My Oracle Support Banner

V$ARCHIVE_DEST_STATUS.RECOVERY_MODE is Changed to IDLE After RMAN Operation on Standby (Doc ID 2419812.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

After RMAN operation on standby database, V$ARCHIVE_DEST_STATUS.RECOVERY_MODE is changed to IDLE from MANAGED REAL TIME APPLY in spite of REDO Apply is in progress.

Result of gv$archive_dest_status before RMAN operation:

INST_ID DEST_ID STATUS RECOVERY_MODE
---------- ---------- -------- ------------------------
1 1 VALID MANAGED REAL TIME APPLY
1 2 VALID IDLE
1 32 VALID IDLE
2 1 VALID MANAGED REAL TIME APPLY
2 2 VALID IDLE
2 32 VALID IDLE

Result of gv$archive_dest_status after RMAN operation:

INST_ID DEST_ID STATUS RECOVERY_MODE
---------- ---------- -------- ------------------------
1 1 VALID IDLE
1 2 VALID IDLE
1 32 VALID IDLE
2 1 VALID IDLE
2 2 VALID IDLE
2 32 VALID IDLE

This problem happens on RAC database. This issue does not happen on single instance.

Changes

RMAN operation is performed on standby database. 

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.