RAC DATABASE HANGS WHEN RMAN IS STARTED
(Doc ID 745198.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - 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.
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 /<path>/<oracle_sid>_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 /<path>/<oracle_sid>_arc1_11671.trc:
ORA-00600: [2103] [1] [0] [1] [900]
alert_INST2.log
===========
Mon Sep 29 23:45:55 2008
Errors in file /<path>/<oracle_sid>_arc1_20541.trc:
ORA-00600 [2103] [1] [0] [1] [900]
Mon Sep 29 23:45:56 2008
Errors in file /<path>/<oracle_sid>_arc1_20541.trc:
ORA-00600: [2103] [1] [0] [1] [900]
....
Tue Sep 30 03:24:33 2008
Errors in file /<path>/<oracle_sid>_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
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 |
| Cause |
| Solution |
| References |