- 最后登录
- 2017-5-4
- 在线时间
- 81 小时
- 威望
- 999
- 金钱
- 2391
- 注册时间
- 2013-9-11
- 阅读权限
- 150
- 帖子
- 1124
- 精华
- 5
- 积分
- 999
- UID
- 1220
|
3#
发表于 2017-4-26 11:25:36
Database Crashed With ORA-1092 error (Doc ID 1448602.1) To BottomTo Bottom
In this Document
Symptoms
Cause
Solution
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
APPLIES TO:
Oracle Database - Enterprise Edition - Version 9.2.0.8 and later
Information in this document applies to any platform.
SYMPTOMS
Database instance crashed with the following error in alert.log:
Wed Nov 02 06:23:51 2011
Non critical error ORA-00001 caught while writing to trace file "/opt/diag/rdbms/prd1/PRD1/trace/PRD1_arc1_2076702.trc"
Error message: IBM AIX RISC System/6000 Error: 5: I/O error
Additional information: 1
Writing to the above trace file iWed Nov 02 06:29:56 2011
USER (ospid: 643220): terminating the instance due to error 1092
Wed Nov 02 06:29:56 2011
ORA-1092 : opitsk aborting process
Instance terminated by USER, pid = 643220
Looking at entries in alert.log prior to crash, following is seen:
a. DBWR process experiencing I/O error:
Wed Nov 02 06:23:38 2011
Non critical error ORA-00001 caught while writing to trace file "/opt/diag/rdbms/prd1/PRD1/trace/PRD1_dbw0_2875438.trc"
Error message: IBM AIX RISC System/6000 Error: 5: I/O error
Additional information: 1
Writing to the above trace file is disabled for now on...
b. Entries in alert.log is incomplete:
Writing to the above trace file iWed Nov 02 06:29:56 2011 -----> as you see here the output is truncated.
2. MMON process trace file shows:
Unix process pid: 1949800, image: oracle@prdserver (MMON)
*** 2011-11-02 06:23:43.879
Taking over instance termination because the instance terminator (ospid: 2875438) is dead
===> 2875438 is the OS PID of DBW0 process which encountered the I/O error and is dead.
3. The instance was then terminated by USER process with the OS PID 643220.
Trace file for this process shows:
Taking over instance termination because the instance terminator (ospid: 2191470) is dead
kjzduptcctx: Notifying DIAG for crash event
----- Abridged Call Stack Trace -----
ksedsts()+644<-kjzdssdmp()+444<-kjzduptcctx()+272<-kjzdicrshnfy()+96<-ksuitm()+1284<-ksuitr()+92<-ksu_dispatch_tac()+372<-kdifxs1()+468<-kdifxs()+28<-qerixtFetch()+940
<-qerilFetch()+276<-opifch2()+7136<-opifch()+60<-opiodr()+3608<-rpidrus()+536<-skgmstack()+208
<-rpidru()+144<-rpiswu2()+1124<-rpidrv()+2892<-rpifch()+80
----- End of Abridged Call Stack Trace -----
*** 2011-11-02 06:29:56.242
USER (ospid: 643220): terminating the instance due to error 1092
5. OS logs (/var/log on AIX) reports I/O errors :
Date/Time: Wed Nov 2 06:29:52 CUT 2011
Description
USER DATA I/O ERROR
Probable Causes
ADAPTER HARDWARE OR MICROCODE
DISK DRIVE HARDWARE OR MICROCODE
SOFTWARE DEVICE DRIVER
STORAGE CABLE LOOSE, DEFECTIVE, OR UNTERMINATED
CAUSE
It could be that either the datafiles are offline/corrupted:
Check the OFFLINE files:
select file#, status, name from v$datafile where status not in ('SYSTEM', 'ONLINE');
OR
There is a problem in the password file (orapw) found in $ORACLE_HOME/dbs which was created after the database creation. Therefore resulted in a sync issue and ultimately causing an additional error message:
ORA-01990: error opening password file $ORACLE_HOME/dbs/orapw.
OR
DBW0 crashed due to I/O errors. This in turn caused the instance to be terminated as termination of background process will cause the instance to crash .
SOLUTION
Datafiles Corrupted/Offline:
Check if you have a good backup from which you can restore any problematic data file.
1) First restore the problematic datafiles
2) Mount the database and ONLINE those datafiles
SQL> startup mount;
SQL> alter database datafile file1#, .. , filen# online;
3) Recover the database
SQL> recover database;
4) Open database
SQL > alter database open ;
I/O errors
Contact your System/Unix administrator and rectify the hardware problem causing I/O error. |
|