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

MOSC Banner

Standby database not connecting..giving error like DGM-17016 ORA-16603 ORA-16625

edited Dec 8, 2019 11:31AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 6 commentsAnswered ✓
I am trying to connect stand by using data guard broker. giving error as follows

DGMGRL> show database db11gsby

Database - db11gsby

  Role:            PHYSICAL STANDBY
  Intended State:  APPLY-ON
  Transport Lag:   (unknown)
  Apply Lag:       (unknown)
  Real Time Query: OFF
  Instance(s):
    DB11GSBY

Database Status:
DGM-17016: failed to retrieve status for database "db11gsby"
ORA-16603: Data Guard broker detected a mismatch in configuration ID
ORA-16625: cannot reach database "db11gsby"



==========================
Broker steps
--------------


DGMGRL> remove configuration
Removed configuration
DGMGRL> create configuration db11g as primary database is 'db11g' connect identifier is 'db11g';
Configuration "db11g" created with primary database "db11g"

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