Errors while manually registering archivelogs
edited Apr 1, 2012 8:12PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 1 commentAnswered
I have configured data guard in oracle 11gr2 11.2.0.2.0 physical standby
on RHEL 5. I took backup of primary, copied backup and archive logs created while backup was in process to standby and restored it, during this there was bulk insertion
activity undergone and check point not complete messages were
observed in alert log of primary. However, logs were kept shipping and
applying. I executed following command to check activity of data guard:
SELECT MAX(SEQUENCE#), MAX(COMPLETION_TIME), APPLIED FROM V$ARCHIVED_LOG GROUP BY APPLIED;
MAX(SEQUENCE#) MAX(COMPL APPLIED
-------------- --------- ---------
22485 02-APR-12 IN-MEMORY
19416 31-MAR-12 NO
22484 02-APR-12 YES
Archive log 19416 was present on standby so I executed
SELECT MAX(SEQUENCE#), MAX(COMPLETION_TIME), APPLIED FROM V$ARCHIVED_LOG GROUP BY APPLIED;
MAX(SEQUENCE#) MAX(COMPL APPLIED
-------------- --------- ---------
22485 02-APR-12 IN-MEMORY
19416 31-MAR-12 NO
22484 02-APR-12 YES
Archive log 19416 was present on standby so I executed
0