Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 







ORA-16664: unable to receive the result from a database

Oracle Database Tips by Donald BurlesonMay 20, 2016

Question: What do I resolve this data guard error? 

DGM-17016: failed to retrieve status for database "XXX"
ORA-16664: unable to receive the result from a database

Is there any known issues with two Data Guard brokers running on same server on teo homes? This configuration works OK in 12c but fails in 11g.

Answer:  The oerr utility shows this for the ORA-16664 error:

ORA-16664: unable to receive the result from a database

Cause:  During execution of a command, a database in the Data Guard broker configuration failed to return a result.

Action:  Check the Data Guard broker logs for the details of the failure. Ensure network communication is working properly amongst the members of the configuration. Fix any possible network problems and reissue the command.

As we see, you need to check your Data Guard Broker log to see the actual cause for this error.

The real error is likely related to the network, and you should follow these steps to test network connectivity.

One user fixed the issue by registering the 11g and 12c instances on one single listener in the 12c home and removing the 11g listener. Now everything works fine.

Also, this query can give details on the ORA-16667 error:

DGMGRL> show show database verbose 'XXX';

col severity  for a15
col message   for a70
col timestamp for a20
   to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') "timestamp",

Because you indicate that it works OK in 12c, you should open a SR on MOSC and see if you may be hitting a bug.  Other possible causes for the ORA-16667 error include.

- A logon trigger was preventing the connection from the standby database during a switchover. Fix: disable the logon trigger in primary database.  (MOSC id 1530881.1)

- Check the non default port used in connect string of both primary and standby(tnsnames.ora). MOSC id 1228797.

- The protection level does not match: 

select protection_mode, protection_level from v$database;


MOSC - Data Guard Broker reported ORA-16664 (MOSC Doc ID 1390892.1)


Oracle Training from Don Burleson 

The best on site "Oracle training classes" are just a phone call away! You can get personalized Oracle training by Donald Burleson, right at your shop!

Oracle training

  Oracle consulting and training


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.



Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster