Due to reasons outside the scope of this question, we had to flashback our Logical Standby Database (at the VM level) to the previous day.
So, now i'm trying to resolve gaps in missing archivelogs between the primary and the Logical Standby Databases.
SQL> select * from gv$logstdby_process where status_code != 16116; READER ORA-16240: Waiting for log file (thread# 1, sequence# 54888)
Sequence 54888 no longer exists in the Logical Standby (due to the flashback), and since we take a nightly archive log backup, this sequence no longer exists as an archived log on the Primary. However, I verified that this sequence is in the archived log backup on the Primary.
RMAN> list backup of archivelog sequence 54888; List of Archived Logs in backup set 6236 Thrd Seq Low SCN Low Time Next SCN Next Time 1 54888 42289020451 30-MAR-16 42290599951 30-MAR-16
Therefore, I copied the archive log backup to the Logical Standby and issued the following on the Logical Standby database:
RMAN> catalog start with 'L:\oracle\backups'; RMAN> shutdown immediate; RMAN> startup mount; RMAN> recover database; RMAN> alter database open; RMAN> list backup of archivelog scn between 42289020451 and 42289020451; Thrd Seq Low SCN Low Time Next SCN Next Time 1 54888 42289020451 30-MAR-16 42290599951 30-MAR-16 RMAN> list backup of archivelog sequence 54888; specification does not match any backup in the repository SQL> alter database start logical standby apply immediate; SQL> select * from gv$logstdby_process where status_code != 16116; READER ORA-16240: Waiting for log file (thread# 1, sequence# 54888)
So I have 2 questions:
1) Even though I can see the archivelog backup of sequence 54888 on the Logical Standby Database when performing a list backup of archivelog scn, why does the list backup of archivelog sequence 54888 return no records?
2) How can I get the log apply process to pick up sequence 54888 from the archivelog backup?