Oracle DR Setup Problems / ORA - 600 /

Question

Dear All,
Recently we have implemented DR(Disaster Recovery setup Using Oracle data guard in 10g, GUI configurations ) in our Production server. The DR setups are based on the Maximum performance with Realtime apply mode.
The configuration went fine and both servers(DR and ) were syncing fine together as well.
But unfortunately, there was a power failure in the DR site(Which is on the other network) and also the UPS also went down after some time, the real problem started here,
Once the DR server was down, after sometime we are not able to login in to the production system, Interestingly, both DB server and application server are running fine. But we are not able to login into server - SAPGUI hangs. There are no such error written in SAP level and but in oracle alert log, we found out ORA 600 error and also connection timed out for placing the archive log(log_destination_2) in the standby server(This is the DR server - And due to power failure, its not able to reach the server for placing the archive log file )
Temporary solution,
If we restart the production server, we are able to work continuously in the production system without any problem.
So, my query is that, what makes the production system hangs if DR server is unavailable and how it work if we restart the instance? Is this the normal procedure in DR setup? or its a bug in the oracle data guard or in the parameter log_archive_dest2?
Looking forward for your answers with your valuable suggestions
For the reference, I am pasting a part of alert log
Detected ARCH process failure
ARCH: STARTING ARCH PROCESSES
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=92, OS id=4296940
ARC1: Becoming the heartbeat ARCH
Sat Oct 30 02:30:54 2010
WARNING: inbound connection timed out (ORA-3136)
Sat Oct 30 02:31:54 2010
WARNING: inbound connection timed out (ORA-3136)
Sat Oct 30 02:33:33 2010
Incremental checkpoint up to RBA [0x2e2b7.cf96.0], current log tail at RBA [0x2e2b7.cf96.0]
Sat Oct 30 02:37:14 2010
WARNING: inbound connection timed out (ORA-3136)
Sat Oct 30 02:37:52 2010
GES: Potential blocker (pid=2056210) on resource CF-00000000-00000000;
enqueue info in file /oracle/XXX/saptrace/background/xxx_rsm0_2015456.trc
Sat Oct 30 02:38:14 2010
WARNING: inbound connection timed out (ORA-3136)
Sat Oct 30 02:38:22 2010
Errors in file /oracle/XXX/saptrace/background/xxx_rsm0_2015456.trc:
ORA-00600: internal error code, arguments: [2103], [1], [0], [1], [900], [], [], []
Sat Oct 30 02:40:30 2010
GES: Potential blocker (pid=2056210) on resource CF-00000000-00000000;
enqueue info in file /oracle/xxx/saptrace/background/xxx_arc0_4329544.trc
Sat Oct 30 02:41:00 2010
Errors in file /oracle/xxx/saptrace/background/xxx_arc0_4329544.trc:
ORA-00600: internal error code, arguments: [2103], [1], [0], [1], [900], [], [], []
Sat Oct 30 02:41:02 2010
Errors in file /oracle/xxx/saptrace/background/xxx_arc0_4329544.trc:
ORA-00600: internal error code, arguments: [2103], [1], [0], [1], [900], [], [], []
Sat Oct 30 02:41:02 2010
Errors in file /oracle/xxx/saptrace/background/xxx_arc0_4329544.trc:
ORA-00600: internal error code, arguments: [2103], [1], [0], [1], [900], [], [], []
Sat Oct 30 02:41:02 2010
Errors in file /oracle/xxx/saptrace/background/xxx_arc0_4329544.trc:
ORA-00600: internal error code, arguments: [2103], [1], [0], [1], [900], [], [], []
Sat Oct 30 02:41:02 2010
Errors in file /oracle/xxx/saptrace/background/xxx_arc0_4329544.trc:
ORA-00600: internal error code, arguments: [2103], [1], [0], [1], [900], [], [], []
Sat Oct 30 02:41:02 2010
Errors in file /oracle/xxx/saptrace/background/xxx_arc0_4329544.trc:
ORA-00600: internal error code, arguments: [2103], [1], [0], [1], [900], [], [], []
Sat Oct 30 02:41:06 2010
ARCH: Detected ARCH process failure
ARCH: STARTING ARCH PROCESSES
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0 started with pid=91, OS id=1642728
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Sat Oct 30 02:42:20 2010
WARNING: inbound connection timed out (ORA-3136)
Sat Oct 30 02:42:33 2010
GES: Potential blocker (pid=2056210) on resource CF-00000000-00000000;
enqueue info in file /oracle/xxx/saptrace/background/xxx_arc1_4296940.trc
Sat Oct 30 02:43:03 2010
Errors in file
Thanks and Regards
Vijay Kumar G

Answer 1

Hi Vijay,
Get oracle metalink ID from service market place and search for  you will get handy information
ORA-600 [2103] "Timeout on 'Control file' or 'Checkpoint Progress' Enqueue" [ID 28045.1]
Also one very good tool to analyse [Metalink|https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=153788.1]
Regards,