Our primary is 3 node RAC of 11.2.0.1 on Redhat 5.2. Same for physical standby except it is a single instance. The redo applying was found stopped from Dec 15. I checked and see that all archivedlogs are transported to the standby and they are up to date by comapare the result of query v$archive_log from primary and standby, and by comparing the physical files. I then tried to register the archived log on standby. I started to the ealiese non-applied archivelog
SQL> ALTER DATABASE REGISTER OGFILE '/u01/flash/flashback_recovery_area/CCHDR/archivelog/2010_12_15/o1_mf_2_10620_6jlk3g25_.arc';
ALTER DATABASE REGISTER LOGFILE '/u01/flash/flashback_recovery_area/CCHDR/archivelog/2010_12_15/o1_mf_2_10620_6jlk3g25_.arc'
*
ERROR at line 1:
ORA-16089: archive log has already been registered
Check the standby alert_log file and see the connection to the primary was broken at the time when redo apply stopped:
.....
Recovery of Online Redo Log: Thread 2 Group 10 Seq 10615 Reading mem 0
Mem# 0: +REDO/cchdr/onlinelog/group_10.303.736441613
Wed Dec 15 16:33:14 2010
RFS[22]: Possible network disconnect with primary database
....
While primary alert_log indicates that at the time the database was reboot. Afyer the prmary was started, data guard broker was initialized
....
ALTER DATABASE OPEN
Data Guard Broker initializing...
Data Guard Broker initialization complete
Data Guard: verifying database primary role...
Starting Data Guard Broker (DMON)
Wed Dec 15 16:46:15 2010
This instance was first to open
Block change tracking file is current.
Beginning crash recovery of 2 threads
parallel recovery started with 3 processes
....
Now how can I let Redo Apply service to continue?