My Oracle Support Banner

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

Last updated on FEBRUARY 05, 2024

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Primary Database: BOSTON
Physical Standby Database: CHICAGO,STDBY
Logical Standby Database: LOGSTDBY

**************

To resolve ORA-16664 on Dataguard broker environment.

ORA-16664 (Description : unable to receive the result from a database) is a generic error. Check the primary/standby DRC log for subsequent error.

For example:  

DGMGRL prompt shows,

ORA-16664 and the corresponding logical standby DRC log shows ORA-01031.

For ORA-16664 , ORA-16792 Refer <Note 1228797.1> -ORA-16664 ORA-16792 Data guard Broker.


Sample Error message:

DGMGRL> show configuration;

Configuration - DG

Protection Mode: MaxPerformance
Databases:
BOSTON - Primary database
stdby - Physical standby database
logstdby - Logical standby database
Error: ORA-16664: unable to receive the result from a database

Fast-Start Failover: DISABLED

Configuration Status:
ERROR

-- ---Primary DRC log----

2012-01-02 13:46:06.850 req ID 1.1.973032160, opcode DEL_RES, phase NULL
2012-01-02 13:46:15.798 NSV2: Initialization of connection failed.
2012-01-02 13:46:15.801 NSV2: expected destination db_unique_name is chicago
2012-01-02 13:46:15.802 NSV2: database actually reached LOGSTDBY
2012-01-02 13:46:15.803 NSV2: Failed to send message to site chicago. Error code is ORA-16642.
2012-01-02 13:46:15.804 03000000 973032160 DMON: Database chicago returned ORA-16642
2012-01-02 13:46:15.805 03000000 973032160 for opcode = DEL_RES, phase = NULL, req_id = 1.1.973032160
2012-01-02 13:46:23.670 NSV2: Initialization of connection failed.
2012-01-02 13:46:23.673 NSV2: expected destination db_unique_name is chicago
2012-01-02 13:46:23.675 NSV2: database actually reached LOGSTDBY
2012-01-02 13:46:23.677 NSV2: Failed to send message to site chicago. Error code is ORA-16642.
2012-01-02 13:46:23.678 03000000 973032160 DMON: Database chicago returned ORA-16642

-------Standby DRC log ----------------

2012-01-03 13:51:24.902 Connection to database BOSTON returns ORA-01031.
2012-01-03 13:51:24.903 Please check database BOSTON is using a remote password file,
2012-01-03 13:51:24.904 its remote_login_passwordfile is set to SHARED or EXCLUSIVE,
2012-01-03 13:51:24.905 and the SYS password is the same as this database.
2012-01-03 13:51:24.905 NSV0: Failed to connect to remote database BOSTON. Error is ORA-01031
2012-01-03 13:51:24.906 NSV0: Failed to send message to site BOSTON. Error code is ORA-01031.

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