High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Data Guard issue. ORA-16700 - Replication from primary to secondary broken.

in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered

Standby database has diverged from the primary database. Redo Apply has stopped.

How do I fix this? How do we get the Standby sync with Primary and replication working again? Below are some details:

DGMGRL > show configuration verbose

SecondaryDB - Physical Standby database
Error: ORA-16810: multiple errors or warnings detected for the member

Configuration Status:
ERROR

DGMGRL > show database SecondaryDB

Role: Physical Standby
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: 6 days 11 minutes
Average Apply Rate: (unknown)
Real Time Query : OFF
Instance(s):
PrimaryDB

Database Error(s):
ora-16700: The standby database has diverged from the primary database.
Ora-16766: Redo Apply is stopped

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center