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

  Data Guard搭建完毕之后,执行开启归档路径2,结果发现不同步,

SQL> alter system set log_archive_dest_state_2=enable;

  查看错误日志,发现有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.

  接着查看v$archive_dest视图,查看是否能找到原因,结果发现如下报错:

SQL> select dest_id,error from v$archive_dest;

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

  很明显,DGID不一样,去备库查看参数db_unique_name参数:

SQL> show parameter db_unique_name

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

  发现db_unique_name参数没有修改,仍然是主库的值,速度改过来,并重启备库:

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.

  然后再在主库开启归档路径2,在备库运行命令,查看同步状态:

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.

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

时间: 2024-10-11 03:47:05

PING[ARC2]: Heartbeat failed to connect to standby 'gqtzdb_dg'. Error is 16047的相关文章

error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory 解决办法

服务器版本:CentOS Linux release 7.4 Linux lb 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux 参考:https://www.cnblogs.com/yogurtwu/p/9988974.html 注:在翻了很多baidu和google相关文章后,逐步排查,根据手动执行libvirtd命令出现的报错信息才查到解决方法.一路坑. 对装有k

主库报 Error 12154 received logging on to the standby PING[ARC2]

主备网络配置存在问题 一系列报错 [[email protected] bin]# ./srvctl  start database -d devdbPRCR-1079 : Failed to start resource ora.devdb.dbCRS-5017: The resource action "ora.devdb.db start" encountered the following error: ORA-00119: invalid specification for

解决openstack “failed to connect to server (code: 1006)”故障一例

openstack版本环境:ocata 安装完成ocata版本后,新建主机实例后,通过管理端进入主机实例的控制台时,报错:"failed to connect to server (code: 1006)" 解决思路: 1.检查日志文件,通过日志寻找原因. tail -f /var/log/nova/nova-novncproxy.log 发现连接5900时出现"Name or service not known" 2017-05-17 17:01:43.994 7

Failed to connect to JobMonApp on port 13491

今天为了解决别的问题,把/etc/hosts文件里的 127.0.0.1 localhost改成了 127.0.0.1 DSETL ,结果运行作业的时候就报这个错:Failed to connect to JobMonApp on port 13491.作业能够运行不会报错,但是无法监控,看得到日志,但是看不到运行情况(数据条数)在官网上找到了如下解释: Problem(Abstract) DataStage job run statistics (i.e. rows per second pr

【LR11】Error -27796: Failed to connect to server"server:port": [10060] Connection timed out错误解决办法

  场景描述:被测系统是发布在远程服务器上的,假设IP是10.10.10.10,端口是8066,那么访问地址是http://10.10.10.10:8066/,在control机器上我设置了IP欺骗. 错误现象:在场景运行时出现大量Action.c(8): Error -27796: Failed to connect to server"server:port": [10060] Connection timed out错误. 官方的troubleshooting: 查看工具的tro

使用phpmailer插件发邮件失败提示:SMTP -> ERROR: Failed to connect to server: Connection timed out (110) smtp connect() failed;

一个邮件发送问题,整整弄了我一周时间,起因是这样的,之前弄的一个网站,需要在邮箱里面认证之后才可以注册成功.网站上线了差不多一年之后,客户突然跟我说,网站不能注册了,然后我就查看了一下代码. 发现报这个错误:SMTP -> ERROR: Failed to connect to server: Connection timed out (110)   smtp connect() failed: 这是我的配置. 然后我就想,之前都是可以用的,那会不会可能是客户在邮箱里面更改客户端密码呢?然后我就

ansible Failed to connect to the host via ssh: no such identity: /root/.ssh/id_rsa.bak

中控机和远端主机配置完密钥后,在中控台上通过ansible检测联通性 ansible -i inventory.cfg all -m ping 10.1.1.1 | UNREACHABLE! => { "changed": false, "msg": "Failed to connect to the host via ssh: no such identity: /root/.ssh/id_rsa.bak: No such file or dire

curl: (7) Failed to connect to 127.**** port 1080: Connection refused on WSL2

在WSL2 Ubuntu18.04上执行指令 curl your_ip 发生了如下错误: curl: (7) Failed to connect to 127.**** port 1080: Connection refused 在网上查了很多不靠谱答案,配置文件位置也不确定. ping了一下地址发现可以ping通, 感觉这个应该是代理导致的, 于是在curl后面加上了不使用代理: curl your_ip --noproxy "*" 成功 或者设置代理: curl your_ip -

Unable to connect to the MKS: Failed to connect to <server IP>:902.控制台黑屏

本人此次遇到此问题的是VSphere 5.1. 在此问题出现之前都正常,没出过任何问题,问之做过什么动作,是客户重配了网络,这其实是我要求改的,但是客户改的和我要求的不一样. 我计划是vswitch0做管理,vswitch1做vmotion,vswitch2做vm network:由于安装ESXI 5.1时自动生成vswitch0:10.23.70.60,客户误搭建了vswitch1:10.23.70.54做管理,vswitch2做vmotion,vswitch3做vm network,且vsw