Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

What to do when archive logs go missing ?

francois42Mar 20 2023 — edited Mar 20 2023

RDBMS version : 19c
OS: Oracle Linux 8.4

I have a critical production DB and yesterday I noticed that an RMAN backup job had failed with the following error. I don't remember if it was an L1 or Archivelog backup that failed.

RMAN-03002: failure of backup command at 19/03/2023 09:11:48
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file +FRA_DG/CDB_02P/ARCHIVELOG/2023_03_19/thread_1_seq_23644.1471.1129991671
ORA-17503: ksfdopn:2 Failed to open file +FRA_DG/CDB_02P/ARCHIVELOG/2023_03_19/thread_1_seq_23644.1471.1129991671
ORA-15012: ASM file '+FRA_DG/CDB_02P/ARCHIVELOG/2023_03_19/thread_1_seq_23644.1471.1129991671' does not exist

Recovery Manager complete.

To fix it, I connected to DB and catalog and ran a CROSSCHECK command like below.

After that, I ran an RMAN archivelog backup job manually and it ran fine without any errors.

RMAN> crosscheck copy of archivelog all;

But, is the above “fix”, the best course of action in such a scenario ? I have 2 questions on this.

1. If there was a need for DB restore + recovery, could those missing archive logs caused issues ?

2. In the above scenario, after running a crosscheck, should I have run an L1 backup ? But, will this L1 backup contain the changes from the missing Arch log ?

Comments

Post Details

Added on Mar 20 2023
4 comments
146 views