Oracle ADG Heartbeat failed to connect to standby fault case

Oracle ADG Heartbeat failed to connect to standby fault case

The customer's primary Database is a standalone Database of Oracle Database 11gR2 for AIX. The ibm hacmp software is deployed at the system level, the database is made into a master-slave mode that can be switched between two physical machines, and the ADG is implemented for the database. After the customer switches the master database to the backup server, the master database and the backup database are no longer synchronized. The following alarm is reported in the alarm log of the database:

Fri Mar 13 02:28:00 2015
PING [ARC2]: Heartbeat failed to connect to standby 'd012dg '. Error is 16057. <Note the Error number.
Fri Mar 13 02:29:01 2015
PING [ARC2]: Heartbeat failed to connect to standby 'd012dg '. Error is 16057.
Fri Mar 13 02:30:01 2015
PING [ARC2]: Heartbeat failed to connect to standby 'd012dg '. Error is 16057.
Fri Mar 13 02:31:02 2015
PING [ARC2]: Heartbeat failed to connect to standby 'd012dg '. Error is 16057.
Fri Mar 13 02:32:02 2015
PING [ARC2]: Heartbeat failed to connect to standby 'd012dg '. Error is 16057.
Fri Mar 13 02:33:02 2015
PING [ARC2]: Heartbeat failed to connect to standby 'd012dg '. Error is 16057.
Fri Mar 13 02:34:03 2015
PING [ARC2]: Heartbeat failed to connect to standby 'd012dg '. Error is 16057.
Fri Mar 13 02:35:03 2015
PING [ARC2]: Heartbeat failed to connect to standby 'd012dg '. Error is 16057.
Fri Mar 13 02:36:04 2015
PING [ARC2]: Heartbeat failed to connect to standby 'd012dg '. Error is 16057.

The above alarms have been encountered multiple times in the ADG environment. Please note the error ID similar to the error message. The ID here is 16057. Oracle explains this error as follows:
ORA-16057: DGID from server not in Data Guard configuration
Cause: The Data Guard name of the primary database or the FAL server is not in the Data Guard configuration of the standby.

Action: In order for the primary database or the FAL server to archive logs to the standby database, the Data Guard name of the primary or FAL server must be in the Data Guard configuration of the standby.

Find the following article in MOS:

Primary Remote log shipping failing with ORA-16057-Server not in Data Guard configuration (Doc ID 1570928.1)

 
In this Document

Symptoms

Cause

Solution

 

 

Applies:
Oracle Database-Enterprise Edition-Version 12.1.0.1 and later
Information in this document applies to any platform.

Symptoms

------------ Primary Alert log -----------------
Thu Jul 11 16:28:16 2013
Alter system set log_archive_dest_2 = 'service = chicago async valid_for = (all_logfiles, primary_role) db_unique_name = chicago'

SCOPE = BOTH;
Thu Jul 11 16:28:17 2013
PING [ARC1]: Heartbeat failed to connect to standby 'Chicago '. Error is 16057 ..'
..
.
Error 16057 for archive log file 1 to 'Chicago'
Thu Jul 11 16:28:19 2013
Errors in file/u01/app/oracle/diag/rdbms/boston/trace/boston_tt01_6296.trc:
ORA-16057: the server not in Data Guard configuration

@ Primary,

SQL> col error for a30
SQL> select dest_id, error, status, log_sequence, applied_scn from v $ archive_dest where dest_id = 2;

DEST_ID error status LOG_SEQUENCE APPLIED_SCN
------------------------------------------------------------------------
2 ORA-16057: server not in Data ERROR 61 0
Guard configuration

Cause

Log_archive_config not set.

Solution

@ Primary,

SQL> col error for a30
SQL> select dest_id, error, status, log_sequence, applied_scn from v $ archive_dest where dest_id = 2;

DEST_ID error status LOG_SEQUENCE APPLIED_SCN
------------------------------------------------------------------------
2 ORA-16057: server not in Data ERROR 61 0
Guard configuration

SQL> sho parameter log_archive_config

NAME TYPE VALUE
-----------------------------------------------------------------------------
Log_archive_config string

SQL> ALTER SYSTEM SET log_archive_config = 'dg _ config = (boston, ChicagO) 'SCOPE = BOTH;

System altered.

SQL> alter system set log_archive_dest_state_2 = defer;

System altered.

SQL> alter system set log_archive_dest_state_2 = enable

System altered.

SQL> alter system switch logfile;

System altered.

SQL> select dest_id, error, status, log_sequence, applied_scn from v $ archive_dest where dest_id = 2;

DEST_ID error status LOG_SEQUENCE APPLIED_SCN
------------------------------------------------------------------------
2 VALID 63 2133221

@ Standby,

SQL> sho parameter log_archive_config

NAME TYPE VALUE
-----------------------------------------------------------------------------
Log_archive_config string

NOTE:

1. It is not mandatary to set the config parameter at standby side. But we need this to be set on standby side as well for any role

Transition purpose and for DG broker configuration.

2. Once remote shipping established then log_archive_config to null will not affect the remote destination until DB is restarted.

Restart will verify log_archive_config.

Ti. run "type =" text/javascript ">

This error is caused by the absence of log_archive_config. You can reconfigure this parameter and re-enable the log_archive_dest_state_x parameter to restore the synchronization of the master and slave databases. This error occurs because the customer has not synchronized the initialization parameter files on the master and slave servers of the master database.

When a Heartbeat failed to connect to standby error occurs, pay attention to the error number and locate the error according to the number, for the newly configured ADG environment, you can also try to restart the slave database or the master database to see if synchronization works.

-- End --