Last updated on APRIL 25, 2012
Applies to:
Oracle Server - Enterprise Edition - Version 10.2.0.1 to 11.1.0.7 [Release 10.2 to 11.1]Information in this document applies to any platform.
***Checked for relevance on 25-Apr-2012***
Symptoms
When RMAN is started against the database after a while it hangs, moreover no more connections to the database are allowed, it's not even possible to shutdown database.
Looking at alert.log of both nodes:
alert_INST1.log
===============
GES: Potential blocker (pid=27801) on resource CF-00000000-00000000;
enqueue info in file /u01/app/oracle/admin/INST/bdump/inst1_lmd0_10739.trc and DIAG trace file
Mon Sep 29 23:30:48 2008
Killing enqueue blocker (pid=27801) on resource CF-00000000-00000000
by killing session 123.1305
..
Errors in file /u01/app/oracle/admin/INFRP/bdump/inst1_arc1_11671.trc:
ORA-00600: [2103] [1] [0] [1] [900]
alert_INST2.log
===========
Mon Sep 29 23:45:55 2008
Errors in file /u01/app/oracle/admin/INST/bdump/inst2_arc1_20541.trc:
ORA-00600: [2103] [1] [0] [1] [900]
Mon Sep 29 23:45:56 2008
Errors in file /u01/app/oracle/admin/INFRP/bdump/inst2_arc1_20541.trc:
ORA-00600: [2103] [1] [0] [1] [900]
....
Tue Sep 30 03:24:33 2008
Errors in file /u01/app/oracle/admin/INFRP/bdump/inst2_m000_7490.trc:
ORA-00470: LGWR process terminated with error
ORA-00600: internal error code, arguments: [2103], [1], [0], [1], [900], [], [], []
The only way to exit from this situation is a reboot.
In this case the database was a two nodes RAC, but it can also affect to single instance databases
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms