ORA-16501: the Data Guard broker operation failed

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

You may see the redo shipping is working fine from Primary to standby DB. But you can notice this error when you try to enable the DG broker.

Test the following:

1. connection to standby from Primary server - should be good if the redo shipping is fine

2. connection from standby to Primary server

This could be the cause - As during normal redo shipping we don't need the vice versa connection from standby to Primary but when you enable the DG Broker it needs that for the auto switchover, fail over.

From standby server, try to connect to the Primary DB. If it throws the any error look into it accordingly.

Primary:

----------

Alertlog Details:

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

Thu Jun 18 17:19:55 2015

LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)

LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned

Error 3135 for archive log file 3 to 'ebox'

Errors in file /u01/app/oracle/diag/rdbms/eb/eb/trace/eb_nsa2_0022.trc:

ORA-03135: connection lost contact

DGBroker Log(DRC log) Details:

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

06/18/2015 18:00:25

Failed to send message to site p1ebox. Error code is ORA-16501.

Data Guard Broker Status Summary:

  Type                        Name                             Severity  Status

  Configuration               DG-eb                           Warning  ORA-16607

  Primary Database            eb                              Success  ORA-00000

  Physical Standby Database   ebox                              Error  ORA-16501

DGMGRL> show configuration

Configuration - DG-eb

  Protection Mode: MaxPerformance

  Databases:

  eb   - Primary database

  ebox - Physical standby database

  Error: ORA-16501: the Data Guard broker operation failed

Fast-Start Failover: DISABLED

Configuration Status:

ERROR

                               

Standby:

----------

Alertlog Details:

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

Thu Jun 18 17:19:55 2015

RFS[4]: Possible network disconnect with primary database

Thu Jun 18 17:25:29 2015

Primary database is in MAXIMUM PERFORMANCE mode

DGBroker Log(DRC log) Details:

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

05/28/2015 19:23:30

Site eb returned ORA-16664.

05/28/2015 19:25:45

Site eb returned ORA-16664.

05/28/2015 19:26:02

Redo Apply is running without USING CURRENT LOGFILE option while DelayMins=0

05/28/2015 20:12:38

Command ENABLE DATABASE ebox completed

06/08/2015 11:35:01

Site eb returned ORA-16664.

06/17/2015 12:30:39

Command ENABLE CONFIGURATION completed

Creating Data Guard Broker Monitor Process (DMON)

06/18/2015 07:53:12

06/18/2015 17:53:40

Site eb returned ORA-16664.

 DGMGRL> show configuration

Configuration - DG-eb

  Protection Mode: MaxPerformance

  Databases:

    eb   - Primary database

    ebox - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:

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

DGM-17017: unable to determine configuration status

We have done the below steps.

DGMGRL> show configuration

Configuration - DG-eb

  Protection Mode: MaxPerformance

  Databases:

    eb   - Primary database

    ebox - Physical standby database

    Error: ORA-16501: the Data Guard broker operation failed

Fast-Start Failover: DISABLED

Configuration Status:

ERROR

DGMGRL> enable configuration

Enabled.

DGMGRL> show configuration

Configuration - DG-eb

  Protection Mode: MaxPerformance

  Databases:

    eb   - Primary database

    ebox - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:

SUCCESS

Primary DRC log:

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

06/18/2015 18:22:10

ENABLE CONFIGURATION

06/18/2015 18:22:11

Command ENABLE CONFIGURATION completed

Standby DRC log:

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

06/18/2015 18:22:11

Command ENABLE CONFIGURATION completed

Happy Learning :)