My Oracle Support Banner

RMAN-8137 at Physical Standby while trying to Delete Archivelogs Generated By Snapshot DB (Doc ID 1942792.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

Symptoms

While trying to Delete the Archive logs at the Physical Standby, getting Errors

 RMAN-8137: WARNING: archived log not deleted, needed for standby or upstream capture process
 
Getting this RMAN-8137 while trying to delete the Archive logs which was generated  when the Physical Standby DB role was set to Snapshot Standby

 

Steps Done:

- Create physical Standby with DB_RECOVERY_FILE_DEST
- Convert to Snapshot
SQL> alter database convert to snapshot standby;
- Restart and preform log switches
- Convert it back to the Physical Standby
SQL> alter database convert to physical standby;

- Run RMAN> backup archivelog all delete input;
-> This will delete the archives which are applied on the physical but will report an RMAN-8137 on the archives related to the Snapshot

 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.