PING[ARC2]: Heartbeat failed to connect to standby ‘gqtzdb_dg’. Error is 16047

PING[ARC2]: Heartbeat failed to connect to standby ‘gqtzdb_ dg’. Error is 16047

Posted on July 3, 2017 18:42 flying board reading (94) comments (0) editing collection

After the data guard is set up, open the archive path 2, and the result is out of sync

SQL> alter system set log_archive_dest_state_2=enable;

Check the error log:PING[ARC2]: Heartbeat failed to connect to standby ‘gqtzdb_dg’. Error is 16047.

[[email protected] trace]$ tail -100f alert_gqtzdb.log 
Mon Jul 03 18:19:10 2017
Using STANDBY_ARCHIVE_DEST parameter default value as /oradata/gqtzdb/archivelog
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Mon Jul 03 18:19:10 2017
PING[ARC2]: Heartbeat failed to connect to standby 'gqtzdb_dg'. Error is 16047.

Next, look at the V $archive_ In the dest view, check whether the cause can be found, and the following error is reported:

SQL> select dest_id,error from v$archive_dest;

   DEST_ID ERROR
---------- -----------------------------------------------------------------
         1
         2 ORA-16047: DGID mismatch between destination setting and target
           database

Obviously, dgid is different. Go to the standby database to check the parameter dB_ unique_ Name parameter:

SQL> show parameter db_unique_name

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_unique_name                       string      gqtzdb

It is found that the db_unique_name parameter has not been changed and is still the value of the primary library, so change it quickly and restart the backup library as follows.

1

2

3

4

5

6

7

8

9

10

SQL> alter system set db_unique_name='gqtzdb_dg' scope=both;

alter system set db_unique_name='gqtzdb_dg' scope=both

*

ERROR at line 1:

ORA-02095: specified initialization parameter cannot be modified

SQL> alter system set db_unique_name='gqtzdb_dg' scope=spfile;

System altered.

Then turn on archive path 2 on the master and run the command on the standby to check the synchronization status.

SQL> alter database recover managed standby database using current logfile disconnect from session;

Database altered.

SQL> select process,client_process,sequence#,status from v$managed_standby;

PROCESS   CLIENT_P  SEQUENCE# STATUS
--------- -------- ---------- ------------
ARCH      ARCH              0 CONNECTED
ARCH      ARCH              0 CONNECTED
ARCH      ARCH              0 CONNECTED
ARCH      ARCH              0 CONNECTED
RFS       UNKNOWN           0 IDLE
RFS       LGWR             24 IDLE
RFS       UNKNOWN           0 IDLE
RFS       UNKNOWN           0 IDLE
MRP0      N/A              11 APPLYING_LOG

9 rows selected.

Similar Posts: