达梦守护集群主库处于mount状态问题处理

本文记录了在虚拟机上搭建的DW环境中,主库被挂起后次日发现处于mount状态的问题。通过启动dmwatcher、检查端口和日志,作者逐步解决主库连接问题并成功将其打开,备库也同步更新为standby状态。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

主库处于mount状态问题

在虚拟机新搭建的dw环境,测试正常后,挂起虚拟机,关闭crt工具下班,第二天回来后发现守护失败:主库处于mount状态,dmwatcher守护进程不能将主库open。
查询主库状态
SQL> select instance_name,host_name,status,mode,mode,mode,oguid from v$instance;

行号 INSTANCE_NAME HOST_NAME STATUS$ MODE$ OGUID


1 DMDW1 dw1 MOUNT PRIMARY 453331

已用时间: 4.625(毫秒). 执行号:1.

于是想到需要启动dmwatcher守护进程,在主库上启动守护进程
[dmdba@dw1 ~]$ dmwatcher /opt/dmdbms/data/lzdm/dmwatcher.ini
DMWATCHER[4.0] V8
DMWATCHER[4.0] IS READY

再次查看主库的状态,主库仍然处于mount状态,
查看主库的dmwatcher日志
[dmdba@dw1 log]$ tail -0f dm_dmwatcher_DMDW1_202110.log
2021-10-13 20:36:48.940 [INFO] dmwatcher P0000020612 T0000139923596203840 dw2_conn_mgr_thread create, connect ip:10.228.10.16, port:5536, from_flag:0
2021-10-13 20:36:48.941 [INFO] dmwatcher P0000020612 T0000139923596203840 DMWATCHER[4.0] group(GRP1) initialized succeed.
GUID(7EF96A5E7EF96A5E26F9D02F7841ABD7)
2021-10-13 20:36:48.977 [INFO] dmwatcher P0000020612 T0000139923596203840 DMWATCHER[4.0] IS READY
2021-10-13 20:36:49.947 [INFO] dmwatcher P0000020612 T0000139923485456128 dw2_send_port_set to dmserver vio(3) set, mid(-1), to name:DMDW1, ip:127.0.0.1
2021-10-13 20:36:49.950 [ERROR] dmwatcher P0000020612 T0000000000000020617 Can’t connect to DM server on ‘10.228.10.16’ port(5536) errno(111)
2021-10-13 20:36:49.950 [INFO] dmwatcher P0000020612 T0000139923477034752 dw2_group_process_svr_info_low, receive ep(seqno:0, master:0, n_ok:0) message, change ep(DMDW1) status from ERROR to OK.
2021-10-13 20:36:49.952 [INFO] dmwatcher P0000020612 T0000139923477034752 Local db apply info changed, old info[p_db_magic:0, n_apply_ep:0], new info to set[p_db_magic:330004170, n_apply_ep:0]!
2021-10-13 20:36:49.952 [INFO] dmwatcher P0000020612 T0000139923477034752 dw2_process_ohis_info, n_ohis changed from 0 to 7, from_ep:DMDW1, ep_seqno:0, hpc_master:0
2021-10-13 20:36:49.953 [INFO] dmwatcher P0000020612 T0000139923477034752 dw2_process_ohis_info local apply info, p_db_magic:330004170, n_apply_ep:0, n_fill_ep:1 pkg_seq_arr:[4742, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], apply_lsn_arr:[37833, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]!
2021-10-13 20:36:49.953 [INFO] dmwatcher P0000020612 T0000139923477034752 服务器端(DMDW1)公钥发生变化,广播新值给监视器

从日志可以看到一条错误信息,主库链接不到备库的5536端口
测试端口的情况:
从主库链接备库的5536端口:
[dmdba@dw1 log]$ telnet 192.168.3.16 5536
Trying 192.168.3.16…
telnet: connect to address 192.168.3.16: Connection refused

链接端口失败
检查备库上端口是否开启:
[dmdba@dw2 lzdm]$ lsof -i:5536
备库上5536为开启,同样检查主库上的5536是否开启,由那个进程开启
[dmdba@dw1 log]$ lsof -i:5536
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dmwatcher 21412 dmdba 4u IPv6 422116 0t0 TCP *:5536 (LISTEN)
从查询结果看出,5536是由dmwatcher进程开启,于是想到备库的dmwatcher进程未启动,在备库上启动dmwatcher进程
在备库上启守护进程
[dmdba@dw2 ~]$ dmwatcher /opt/dmdbms/data/lzdm/dmwatcher.ini

再次查看主库状态

主库:
SQL> select instance_name,host_name,status,mode,mode,mode,oguid from v$instance;

行号 INSTANCE_NAME HOST_NAME STATUS$ MODE$ OGUID


1 DMDW1 dw1 OPEN PRIMARY 453331

备库:
SQL> select instance_name,host_name,status,mode,mode,mode,oguid from v$instance;

行号 INSTANCE_NAME HOST_NAME STATUS$ MODE$ OGUID


1 DMDW2 dw2 OPEN STANDBY 453331

已用时间: 6.374(毫秒). 执行号:400.

更多资讯请上达梦技术社区了解:https://eco.dameng.com

评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值