A fix is available
APAR status
Closed as program error.
Error description
Starting with FP15 the following problem is exposed: It can happen that HADR cannot be started when using IP addreses for HADR local host name (HADR_LOCAL_HOST) HADR remote host name (HADR_REMOTE_HOST) and the maschines have more than one network cards. db2diag.log: 2007-09-28-10.12.46.616052+120 I5906369E450 LEVEL: Error PID : 404 TID : 47490870195824PROC : db2hadrs (DGBS) INSTANCE: db2root1 NODE : 000 DB : DGBS FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrResolveHosts, probe:20158 MESSAGE : The hadr_remote_host: xxx.xx.x.x could not be resolved DATA #1 : Hexdump, 4 bytes 0x00007FFF5AAA822C : 1200 0F81 .... 2007-09-28-10.12.46.616241+120 I5906820E362 LEVEL: Error PID : 404 TID : 47490870195824PROC : db2hadrs (DGBS) INSTANCE: db2root1 NODE : 000 DB : DGBS FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrResolveHosts, probe:20158 RETCODE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error"
Local fix
n/a
Problem summary
USERS AFFECTED ALL using HADR PROBLEM DESCRIPTION Starting with FP15 the following problem is exposed: It can happen that HADR cannot be started when using IP addreses for HADR local host name (HADR_LOCAL_HOST) HADR remote host name (HADR_REMOTE_HOST) and the maschines have more than one network cards. db2diag.log: 2007-09-28-10.12.46.616052+120 I5906369E450 LEVEL: Error PID : 404 TID : 47490870195824PROC : db2hadrs (DGBS) INSTANCE: db2root1 NODE : 000 DB : DGBS FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrResolveHosts, probe:20158 MESSAGE : The hadr_remote_host: xxx.xx.x.x could not be resolved DATA #1 : Hexdump, 4 bytes 0x00007FFF5AAA822C : 1200 0F81 .... 2007-09-28-10.12.46.616241+120 I5906820E362 LEVEL: Error PID : 404 TID : 47490870195824PROC : db2hadrs (DGBS) INSTANCE: db2root1 NODE : 000 DB : DGBS FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrResolveHosts, probe:20158 RETCODE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error" PROBLEM SUMMARY Starting with FP15 the following problem is exposed: It can happen that HADR cannot be started when using IP addreses for HADR local host name (HADR_LOCAL_HOST) HADR remote host name (HADR_REMOTE_HOST) and the maschines have more than one network cards. db2diag.log: 2007-09-28-10.12.46.616052+120 I5906369E450 LEVEL: Error PID : 404 TID : 47490870195824PROC : db2hadrs (DGBS) INSTANCE: db2root1 NODE : 000 DB : DGBS FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrResolveHosts, probe:20158 MESSAGE : The hadr_remote_host: xxx.xx.x.x could not be resolved DATA #1 : Hexdump, 4 bytes 0x00007FFF5AAA822C : 1200 0F81 .... 2007-09-28-10.12.46.616241+120 I5906820E362 LEVEL: Error PID : 404 TID : 47490870195824PROC : db2hadrs (DGBS) INSTANCE: db2root1 NODE : 000 DB : DGBS FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrResolveHosts, probe:20158 RETCODE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error"
Problem conclusion
The complete fix for this problem first appears in DB2 UDB Version 8.1 FixPak 16.
Temporary fix
n/a
Comments
APAR Information
APAR number
JR27576
Reported component name
DB2 UDB HADR
Reported component ID
5724J2000
Reported release
820
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-10-08
Closed date
2008-02-06
Last modified date
2008-02-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB HADR
Fixed component ID
5724J2000
Applicable component levels
R820 PSN
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820"}]
Document Information
Modified date:
07 October 2021