DGMGRL Show Database Fails with DGM-17016, ORA-16525, ORA-16625
(Doc ID 2455718.1)
Last updated on OCTOBER 10, 2018
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 18]
Information in this document applies to any platform.
DGMGRL show database command fails.
in case of connect to primary database:
DGMGRL> show database db01;
Database - db01
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
Average Apply Rate: (unknown)
Real Time Query: OFF
db01_1 (apply instance)
DGM-17016: failed to retrieve status for database "db01"
ORA-16525: The Oracle Data Guard broker is not yet available.
ORA-16625: cannot reach member "db01"
in case of connect to standby database:
Configuration details cannot be determined by DGMGRL
Broker log (drcdb01_1.log) on standby database contains :
DMON: Successfully opened configuration file '+DATA/DB01/DATAGUARDCONFIG/dr1.dat'
DMON: home block of +DATA/DB01/DATAGUARDCONFIG/dr1.dat: zzz=0x40, Seq.MIV=8.2, fsfo flags=0x2, version=0, vseq=0
DMON: Opening configuration file '+DATA/DB01/DATAGUARDCONFIG/dr2.dat' with blocksize 4096
DMON: Successfully opened configuration file '+DATA/DB01/DATAGUARDCONFIG/dr2.dat'
DMON: home block of +DATA/DB01/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
Restarting standby database.
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