注册登录
提 问
English中文版
zss0109211
作者zss0109211·2015-01-22 16:41
数据库管理员·null
关注2

HADR HADR_SYNCMODE测试

字数 15172阅读 6644评论 0赞 0
配置HADR 主库与备库同步：sync，模拟备机网络故障 .
主库会被阻塞 HADR_TIMEOUT（120秒） 设置的时间，虽然120秒，事物是提交了，但这样严重的影响主库业务响应时间。
到底是设置sync保证主库一致，故障时HADR能无丢失take over.还是优先保证响应速度,不因备库的网络间歇性故障或者磁盘损坏影响主库？

下面是主库的db2diag.log
2015-01-22-02.48.54.054745-300 I312149E527           LEVEL: Error
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSendRedirectMsgToOneAddress, probe:31070
MESSAGE : ZRC=0xFFFFFFFF=-1
DATA #1 : <preformatted>
The HADR primary was not able to form a TCP connection with the standby: 10.123.18.244:55004.

2015-01-22-02.48.54.057261-300 E312677E499           LEVEL: Error
PID     : 16172                TID : 140736875980544 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 46                   EDUNAME: db2hadrp.0.2 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu::hdrEduP, probe:20389
MESSAGE : ADM12510E  Unable to establish HADR primary-standby connection with 
          host: "hadr_target_list.". Reason code: "10"

2015-01-22-02.50.28.164583-300 I313177E464           LEVEL: Warning
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrHandleRemoteConn, probe:30160
MESSAGE : TCP socket connection accepted.  Remote Host: 10.123.18.244 Port: 
          37606

2015-01-22-02.50.28.265987-300 I313642E452           LEVEL: Info
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSendHsMsgNoDefer, probe:30539
DATA #1 : <preformatted>
A HDR_MSG_REDIRECT message was sent to 10.123.18.244:55004

2015-01-22-02.50.28.266490-300 I314095E479           LEVEL: Info
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrHandleHsAck, probe:43900
DATA #1 : <preformatted>
Handshake HDR_MSG_HDRHS message is received from M4:DB2_db2insta_2nd (10.123.18.244:55004)

2015-01-22-02.50.28.267087-300 I314575E425           LEVEL: Info
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrAfterVerifySystem, probe:30440
DATA #1 : <preformatted>
Connection succeeded, connId=2

2015-01-22-02.50.28.267641-300 I315001E465           LEVEL: Info
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrAfterVerifySystem, probe:30532
DATA #1 : <preformatted>
Info: HADR Socket send buffer size adjusted to, SO_SNDBUF: 16384 bytes

2015-01-22-02.50.28.268031-300 I315467E468           LEVEL: Info
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrAfterVerifySystem, probe:30534
DATA #1 : <preformatted>
Info: HADR Socket receive buffer size adjusted to, SO_RCVBUF: 87380 bytes

2015-01-22-02.50.28.470247-300 E315936E452           LEVEL: Event
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetHdrState, probe:10000
CHANGE  : HADR state set to HDR_P_REM_CATCHUP (was HDR_P_REM_CATCHUP_PENDING), connId=2

2015-01-22-02.50.28.521345-300 I316389E459           LEVEL: Info
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu::hdrEduP, probe:20445
DATA #1 : <preformatted>
Remote catchup starts at lso 60026717.
Using page start lso 60023177.

2015-01-22-02.50.28.563254-300 I316849E424           LEVEL: Warning
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrTransitionPtoNPeer, probe:10645
MESSAGE : near peer catchup starts at LSO 60027311

2015-01-22-02.50.28.664283-300 I317274E449           LEVEL: Info
PID     : 16172                TID : 140736964060928 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 25                   EDUNAME: db2loggw (MYDB) 0
FUNCTION: DB2 UDB, data protection services, sqpLoggwEdu::sqlpLoggwMain, probe:4399
DATA #1 : <preformatted>
Database log writing has been suspended.  Waiting to be resumed.

2015-01-22-02.50.28.664765-300 E317724E438           LEVEL: Event
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetHdrState, probe:10000
CHANGE  : HADR state set to HDR_P_NPEER (was HDR_P_REM_CATCHUP), connId=2

2015-01-22-02.50.28.705431-300 E318163E431           LEVEL: Event
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetHdrState, probe:10000
CHANGE  : HADR state set to HDR_P_PEER (was HDR_P_NPEER), connId=2

2015-01-22-02.50.28.706848-300 I318595E423           LEVEL: Info
PID     : 16172                TID : 140736964060928 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 25                   EDUNAME: db2loggw (MYDB) 0
FUNCTION: DB2 UDB, data protection services, sqpLoggwEdu::sqlpLoggwMain, probe:4427
DATA #1 : <preformatted>
Database log writing has been resumed.

2015-01-22-02.52.59.060923-300 E319019E643           LEVEL: Error
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduAcceptEvent, probe:20200
MESSAGE : Did not receive anything through HADR connection for the duration of 
          HADR_TIMEOUT. Closing connection.
DATA #1 : String, 30 bytes
hdrCurrentTime/hdrLastRecvTime
DATA #2 : unsigned integer, 4 bytes
1421913179
DATA #3 : unsigned integer, 4 bytes
1421913058

2015-01-22-02.52.59.061447-300 I319663E368           LEVEL: Severe
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduAcceptEvent, probe:20200

2015-01-22-02.52.59.061749-300 E320032E445           LEVEL: Event
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetHdrState, probe:10000
CHANGE  : HADR state set to HDR_P_REM_CATCHUP_PENDING (was HDR_P_PEER), connId=2

2015-01-22-02.54.59.226111-300 I320478E584           LEVEL: Error
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSendRedirectMsgToOneAddress, probe:32060
DATA #1 : <preformatted>
HADR handshake with standby host: 10.123.18.244:55004. did not complete  succesfully within timeout time, The network between  the primary and the standby is slow or unreliable. 

2015-01-22-02.54.59.226442-300 E321063E499           LEVEL: Error
PID     : 16172                TID : 140736875980544 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 46                   EDUNAME: db2hadrp.0.2 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu::hdrEduP, probe:20389
MESSAGE : ADM12510E  Unable to establish HADR primary-standby connection with 
          host: "hadr_target_list.". Reason code: "11"

2015-01-22-02.57.20.176177-300 I321563E584           LEVEL: Error
PID     : 16172                TID : 140736880174848 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 45                   EDUNAME: db2hadrp.0.1 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSendRedirectMsgToOneAddress, probe:32060
DATA #1 : <preformatted>
HADR handshake with standby host: 10.123.18.244:55004. did not complete  succesfully within timeout time, The network between  the primary and the standby is slow or unreliable. 

2015-01-22-02.57.20.176818-300 E322148E499           LEVEL: Error
PID     : 16172                TID : 140736875980544 PROC : db2sysc 0
INSTANCE: db2insta             NODE : 000            DB   : MYDB    
HOSTNAME: m3
EDUID   : 46                   EDUNAME: db2hadrp.0.2 (MYDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu::hdrEduP, probe:20389
MESSAGE : ADM12510E  Unable to establish HADR primary-standby connection with 
          host: "hadr_target_list.". Reason code: "11"
数据库HADR
著作权归作者所有

如果觉得我的文章对您有用，请点赞。您的支持将鼓励我继续创作！

赞0

添加新评论0 条评论

Ctrl+Enter 发表

作者其他文章

  • 使用LOAD清空数据遇报错SQL0973N
    评论 1 · 赞 1
  • DB2 V10.5 for Oracle Linux Server release 6.4安装
    评论 0 · 赞 1
  • MYSQL5.5指定表独立路径
    评论 0 · 赞 0
  • DB2 V10.5 1主2从 HADR配置
    评论 0 · 赞 1
  • SNAPSHOT TOP 10 SQL
    评论 0 · 赞 0

    • 相关文章

  • 南大通用对数据库领域国家标准编制与实施的贡献浅析
  • Redis 的优势是如何在保单业务中发挥出来的
  • 企业传统Oracle数据库迁移国产数据库核心难点总结
  • 招聘：建信金科基础技术中心数据库产品团队
  • 数据库运维管理平台面面观

    • 相关问题

  • 超融合能否扛起全闪做支撑交易类数据库最佳平台的大旗？
  • 对于业务系统的历史数据存放、查询，哪种类型的数据库更为合适？
  • 金融行业传统数据库一般如何解决io需求？
  • 引入缺乏第三方服务生态的信创数据库，会不会令甲方被厂商锁定而失去议价能力？
  • 金融行业中，有哪些系统已经应用了容器化数据库？

    • 相关资料

  • oracle日常维护手册
  • Redhat7.6 Oracle 19C RAC部署手册
  • Redhat7.0 Oracle 12C RAC部署手册
  • 海通证券核心数据库系统高可用及存储设备选型经验分享
  • Redhat7.5 Oracle 18C RAC部署手册

    • 关于TWT使用指南社区专家合作厂商入驻社区企业招聘投诉建议版权与免责声明联系我们
    © 2024talkwithtrend — talk with trend,talk with technologist京ICP备09031017号-30

    X社区推广