Database Crashed With ORA-1092 error
(Doc ID 1448602.1)
Last updated on JULY 05, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.8 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A 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 "<PATH>/<SID>_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
Non critical error ORA-00001 caught while writing to trace file "<PATH>/<SID>_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 "<PATH>/<SID>_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...
Non critical error ORA-00001 caught while writing to trace file "<PATH>/<SID>_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@xxx (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.
*** 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
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
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
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |