JR27576: HADR_REMOTE_HOST COULD NOT BE RESOLVED WHEN USING IP ADRESSES

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  LI72600

Fix information

• Fixed component name

  DB2 UDB HADR

• Fixed component ID

  5724J2000

Applicable component levels

• R820 PSN

     UP