How to delete obsoleted archive logs after point in time recovery

gerhard2001

Hello!

We did a database point in time recovery.

Hardware: ODA X7-S BM

Linux Version: Oracle Linux Server release 6.10

 Database Version: 18c Standard Edition 2 Release 18.7.0.0.0

After that recovery we configured the L0 RMAN, which runs once a week in the following way:

run {

       backup noexclude as compressed backupset incremental level 0 database;

       backup as compressed backupset archivelog all delete input;

}

LIST EXPIRED BACKUPSET;

DELETE NOPROMPT EXPIRED BACKUPSET;

crosscheck backup;

list backup of database;

report unrecoverable;

report schema;

report need backup;

report obsolete;

delete noprompt obsolete;

restore validate database;

restore validate archivelog all;

 

RMAN doesn’t use a catalog. RMAN uses the control file.

Everything works fine except ‘restore validate archivelog all’.

This command writes the following into our Log File:

 Starting restore at 21-NOV-20

using channel ORA_DISK_1

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 11/21/2020 21:21:49

RMAN-06026: some targets not found - aborting restore

RMAN-06025: no backup of archived log for thread 1 with sequence 960 and starting SCN of 759934998 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 959 and starting SCN of 759753414 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 958 and starting SCN of 759309135 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 957 and starting SCN of 758837346 found to restore

……

 

These ‘archive logs’ are obsoleted. After all we don’t have theses files anymore.

I think RMAN gets these information from the control file?!

Has this information any influence to a later recovery?

 How can we get rid of this information?

Is there anything wrong in our configuration?

Thanks for any help!

Gerhard

Sunny kichloo

DO check this:

https://www.parnassusdata.com/en/node/1297