Duplicate archivelog sequence on standby database
edited Dec 13, 2012 6:56PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 5 commentsAnswered
Hi,
In our standby database when i check archivelog (below command), i see 2 duplicate sequence number. One is applied and another is not applied. Is there any problem with dataguard and how to solve it
TQ
In our standby database when i check archivelog (below command), i see 2 duplicate sequence number. One is applied and another is not applied. Is there any problem with dataguard and how to solve it
TQ
SQL> sELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG where SEQUENCE# like '369%' order by SEQUENCE#;
THREAD# SEQUENCE# APP
1 36900 YES
1 36901 YES
1 36902 YES
1 36902 NO
1 36903 YES
1 36903 YES
1 36904 YES
1 36904 YES
1 36905 YES
1 36905 NO
1 36906 YES
1 36907 YES
1 36908 YES
1 36909 YES
1 36910 YES
1 36911 YES
1 36911 NO
1 36912 YES
1 36912 NO
1 36913 YES
1 36913 YES
1 36914 YES
1 36914 NO
1 36915 YES
1 36915 NO
1 36916 YES
1 36917 YES
0