My Oracle Support Banner

DGMGRL Show Database Fails with DGM-17016, ORA-16525, ORA-16625 (Doc ID 2455718.1)

Last updated on APRIL 17, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 18.3.0.0.0 to 18.3.0.0.0 [Release 18]
Information in this document applies to any platform.

Symptoms

DGMGRL show database command fails.

in case of connect to primary database:

DGMGRL> show database <stby>;

Database - <stby>

Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
Average Apply Rate: (unknown)
Real Time Query: OFF
Instance(s):
<stby>_1 (apply instance)
<stby>_2

Database Status:
DGM-17016: failed to retrieve status for database "<stby>"
ORA-16525: The Oracle Data Guard broker is not yet available.
ORA-16625: cannot reach member "<stby>"

in case of connect to standby database:

DGMGRL> show database <stby>
Configuration details cannot be determined by DGMGRL

Broker log (drc<stby>_1.log) on standby database contains :

DMON: Opening configuration file '+DATA/<stby>/DATAGUARDCONFIG/dr1.dat' with blocksize 4096
DMON: Successfully opened configuration file '+DATA/<stby>/DATAGUARDCONFIG/dr1.dat'
DMON: home block of +DATA/<stby>/DATAGUARDCONFIG/dr1.dat: zzz=0x40, Seq.MIV=8.2, fsfo flags=0x2, version=0, vseq=0
DMON: Opening configuration file '+DATA/<stby>/DATAGUARDCONFIG/dr2.dat' with blocksize 4096
DMON: Successfully opened configuration file '+DATA/<stby>/DATAGUARDCONFIG/dr2.dat'
DMON: home block of +DATA/<stby>/DATAGUARDCONFIG/dr2.dat: zzz=0x40, Seq.MIV=2.1, fsfo flags=0x1, version=0, vseq=0
DMON: metadata files' DRC Unique IDs don't match

 

Changes

Restarting 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.