DataGuard Common Errors

ORA-16664: unable to receive the result from a database Failed. So this will cause issues now throughout the world.
Unable to switchover, primary database is still "wzsdb"

ORA-16664: unable to receive the result from a database Failed. So this will result in clumsy little errors. What crap this is.
Unable to switchover, primary database is still "wzsdb"


ORA-16664: unable to receive the result from a database Failed. So this will result in clumsy little errors. What crap this is.
Unable to switchover, primary database is still "wzsdb"

ref :
http://weidongzhou.wordpress.com/2014/07/17/switchover-failed-in-data-guard-broker/

Dataguard Broker switchover fails with an ORA-16664 and the standby DRC log shows an ORA-604. (Doc ID 1530881.1)
Data Guard Broker reported ORA-16664 (Doc ID 1390892.1)

ORA-12514 during switchover using Data Guard Broker

While adding static entry broker makes an entry for GLOBAL_NAME=<SID_NAME> but in broker configuration staticconnectidentifier it adds as <SID>_DGMGRL.

assumes a static service with “<db_unique_name>_DGMGRL.<db_domain>” is statically registered with the listener of each instance and LOCAL_LISTENER parameter value resolves correctly to point to the local listener on all instances. This applies to RAC, Oracle Restart and Single Instance databases.

ref :
DGMGRL>switchover to <standby> Fails with ORA-12514 (Doc ID 1582927.1)
http://oracle-tech.blogspot.sg/2009/01/ora-12514-during-switchover-using-data.html
http://oracle-tech.blogspot.sg/2013/07/ora-12514-during-switchover-using-data.html

ORA-12521 TNS:listener could not resolve INSTANCE_NAME given in connect

{db_unique_name}_DGB.{db_domain}: This Service is used by the DMON-Processes to communicate between each other

{db_unique_name}_XPT.{db_domain}: This Service is used for Log Transport Services and FAL (corresponding Initialization Parameters are set once a Configuration is enabled) – Oracle 10.x only

From what I can tell the _DGB service is dynamically registered by the broker, it may be worth checking your local and remote listener parameters are correct.

Also if you don’t have a static registration for the _DGMGRL services you will see alerts in you alert log where the broker fails to connect to the _DGB service this can be quite confusing as it doesn’t log the attempts to connect to DGMGRL.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s