My Oracle Support Banner

REDO Apply on Standby Database does not Proceed After New Database Incarnation Is Set (Doc ID 2692765.1)

Last updated on AUGUST 03, 2020

Applies to:

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

Symptoms

REDO Apply at Standby Database does not proceed after a new database incarnation is set.

For example, consider the following alert log of the standby database:

2020-07-03T14:48:15.072774+09:00
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
2020-07-03T14:48:15.077454+09:00
Attempt to start background Managed Standby Recovery process (<DB_UNIQUE_NAME>)
Starting background process MRP0
2020-07-03T14:48:15.096816+09:00
MRP0 started with pid=55, OS id=20244
2020-07-03T14:48:15.098011+09:00
Background Managed Standby Recovery process started (<DB_UNIQUE_NAME>)
2020-07-03T14:48:20.103916+09:00
Serial Media Recovery started

IM on ADG: Start of Empty Journal

IM on ADG: End of Empty Journal
MRP0 (PID:20244): Managed Standby Recovery starting Real Time Apply
max_pdb is 3
Media Recovery start incarnation depth : 1, target inc# : 5, irscn : 999999999
stopping change tracking
MRP0 (PID:20244): Media Recovery Waiting for xxxxxxxxx.T-1.S-20
2020-07-03T14:48:21.103414+09:00
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION

 

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
Cause
Solution


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