| Asset ID: |
1-72-1404964.1 |
| Update Date: | 2012-05-24 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1404964.1
:
Instance Termination by dbwr with ORA-00600: [1433], [60]
| Related Items |
- Exadata Database Machine X2-2 Half Rack
- Oracle Server - Enterprise Edition
- Oracle Exadata Hardware
|
| Related Categories |
- PLA-Support>Database Technology>Engineered Systems>Oracle Exadata>DB: Exadata_EST
- .Old GCS Categories>ST>Server>Engineered Systems>Exadata>Troubleshooting and Debugging
|
Created from <SR 3-5152020811>
Applies to:
Exadata Database Machine X2-2 Half Rack - Version Not Applicable and later
Oracle Server - Enterprise Edition - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]
Oracle Exadata Hardware - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.
Symptoms
Database Alert Log Reports
ALTER DATABASE OPEN /* db agent *//* {1:65326:57315} */
Picked broadcast on commit scheme to generate SCNs
Fri Jan 06 15:39:46 2012
SUCCESS: diskgroup DATA was mounted
Fri Jan 06 15:40:47 2012
Errors in file
/u01/app/oracle/diag/rdbms/bitsdwhp/BITSDWHP2/trace/BITSDWHP2_dbw0_31327.trc
(incident=56154):
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [],
[], [], [], [], []
Incident details in:
/u01/app/oracle/diag/rdbms/bitsdwhp/BITSDWHP2/incident/incdir_56154/BITSDWHP2_
dbw0_31327_i56154.trc
:
:
:
:
Errors in file
/u01/app/oracle/diag/rdbms/bitsdwhp/BITSDWHP2/trace/BITSDWHP2_gen0_31291.trc:
Fri Jan 06 15:40:47 2012
Dumping diagnostic data in directory=[cdmp_20120106154047], requested by
(instance=2, osid=31291 (GEN0)), summary=[abnormal process termination].
Fri Jan 06 15:40:47 2012
Errors in file
/u01/app/oracle/diag/rdbms/bitsdwhp/BITSDWHP2/trace/BITSDWHP2_lmhb_31323.trc
(incident=56138):
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [],
[], [], [], [], []
Incident details in:
/u01/app/oracle/diag/rdbms/bitsdwhp/BITSDWHP2/incident/incdir_56138/BITSDWHP2_
lmhb_31323_i56138.trc
:
:
:
Errors in file
/u01/app/oracle/diag/rdbms/bitsdwhp/BITSDWHP2/trace/BITSDWHP2_gen0_31291.trc:
Errors in file
/u01/app/oracle/diag/rdbms/bitsdwhp/BITSDWHP2/trace/BITSDWHP2_dbw0_31327.trc:
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [],
[], [], [], [], []
DBW0 (ospid: 31327): terminating the instance due to error 471
System state dump requested by (instance=2, osid=31327 (DBW0)),
summary=[abnormal instance termination].
System State dumped to trace file
/u01/app/oracle/diag/rdbms/bitsdwhp/BITSDWHP2/trace/BITSDWHP2_diag_31293.trc
Fri Jan 06 15:40:48 2012
ORA-1092 : opitsk aborting process
Fri Jan 06 15:40:48 2012
License high water mark = 1
Dumping diagnostic data in directory=[cdmp_20120106154048], requested by
(instance=2, osid=31327 (DBW0)), summary=[abnormal instance termination].
Instance terminated by DBW0, pid = 31327
USER (ospid: 560): terminating the instance
Instance terminated by USER, pid = 560
Stack trace will have
ksedsts()<-kjzdssdmp()<-kjzduptcctx()<-kjzdpcrshnfy()<-kstdmp()
<-dbkedDefDump()<-ksedmp()<-ksfdmp()<-dbgexPhaseII()<-dbgexExplicitEndInc()
<-dbgeEndDDEInvocationImpl()<-dbgeEndDDEInvocation()<-ksasnd()<-ksbasend()
<-kfgbDGResAct()<-kfioIdentify()<-ksfd_osmopn()<-ksfdopn1()<-ksfdopn()<-kcfbid()
Trace File will have
Error: ORA-600 [1433] [60] [] [] [] [] [] [] [] [] [] []
[00]: dbgexExplicitEndInc [diag_dde]
[01]: dbgeEndDDEInvocationImpl [diag_dde]
[02]: dbgeEndDDEInvocation [diag_dde]
[03]: ksasnd [VOS]<-- Signaling
[04]: ksbasend [background_proc]
[05]: kfgbDGResAct [KFG]
[06]: kfioIdentify [ASM]
[07]: ksfd_osmopn [VOS]
[08]: ksfdopn1 [VOS]
[09]: ksfdopn [VOS]
[10]: kcfbid []
[11]: kcfbsy []
[12]: kcvvia [CACHE_RCV]
[13]: ksbabs [background_proc]
[14]: ksbrdp [background_proc]
[15]: opirip []
[16]: opidrv []
[17]: sou2o []
[18]: opimai_real []
[19]: ssthrdmain []
[20]: main []
[21]: __libc_start_main []
[22]: _start []
Cause
Cause of the issue is that the
GEN0 process seems to get too many messages during the instance startup by DBW process and GEN0 is not able respond in time.
This has been confirmed in unpublished BUG 12727101
Solution
Following is the current workaround for this issue
Workaround :
------------
1. SQL> ALTER SYSTEM SET "_flashback_prepare_log"=false SCOPE=both SID='*'; (to allow DB nodes to startup)
2. Startup all db instances.
3. Once all the dbs are up :-
SQL> ALTER SYSTEM RESET "_flashback_prepare_log" SCOPE=SPFILE SID='*';
SQL> ALTER SYSTEM SET "_flashback_prepare_log"=TRUE SCOPE=MEMORY SID='*'
OR
Apply Patch for Bug:12727101 when available
Attachments
This solution has no attachment
