On a NAT environment with the registry variable
DB2_HADR_NO_IP_CHECK turned on, some 'weak' IP validation is
still being done to confirm that the remote database is
contained in the HADR_TARGET_LIST
The following messages are seen in db2diag.log:
2015-10-29-11.20.54.218756+000 I1555625E487 LEVEL: Info
PID : 15772 TID : 139831032145664 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
DBNAME
HOSTNAME: hostname
EDUID : 82 EDUNAME: db2hadrs.0.0 (DBNAME) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrIsIPValid,
probe:15550
DATA #1 : <preformatted>
HADR local/remote host IP cross check bypassed per registry
variable
DB2_HADR_NO_IP_CHECK
2015-10-29-11.20.54.219281+000 E1556113E765 LEVEL:
Error
PID : 15772 TID : 139831032145664 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
DBNAME
HOSTNAME: hostname
EDUID : 82 EDUNAME: db2hadrs.0.0 (DBNAME) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrIsIPValid,
probe:25940
MESSAGE : ZRC=0x87800140=-2021654208=HDR_ZRC_CONFIGURATION_ERROR
"One or both databases of the HADR pair is configured
incorrectly"
DATA #1 : <preformatted>
HADR_LOCAL_HOST:HADR_LOCAL_SVC (hostnameHADR1:56001
(10.125.62.108:56001)) on remote database is not included in
HADR_TARGET_LIST hostnameHADR1:56001
(9.51.168.99:56001)|hostnameHADR2:56002 (9.51.168.100: 56002) on
local database.
2015-10-29-11.20.54.219897+000 E1556879E546 LEVEL:
Error
PID : 15772 TID : 139831032145664 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
DBNAME
HOSTNAME: hostname
EDUID : 82 EDUNAME: db2hadrs.0.0 (DBNAME) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrIsIPValid,
probe:25940
MESSAGE : ADM12513E Unable to establish HADR primary-standby
connection because the primary and standby databases are
incompatible.
Reason code: "4" |
