My Oracle Support Banner

Primary Not Deleting Archivelogs Applied On Standby (Doc ID 2761928.1)

Last updated on APRIL 06, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 to 19.9.0.0.0 [Release 11.2 to 19]
Information in this document applies to any platform.

Symptoms

# Not able to delete archivelogs at PRIMARY although they are applied on Standby.

-- At Primary

RMAN> delete archivelog all ;

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=412 device type=DISK
..
..
RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
archived log file name=/app01/oradata/prmy/arch/prmy_0001_0000192127_1034564654.arc thread=1 sequence=190190
RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
archived log file name=/app01/oradata/prmy/arch/prmy_0001_0000192127_1034564654.arc thread=1 sequence=190191
RMAN-08120: WARNING: archived log not deleted, not yet applied by standby



Changes

There are 2 Standby databases configured, and one of them is not in use.

 

 

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!


In this Document
Symptoms
Changes
Cause
Solution
References


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