Oracle ADG Heartbeat failed to connect to standby故障案例

In this Document

Applies to:

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/boston/trace/boston_tt01_6296.trc:
ORA-16057: 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> 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.

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