LI74662: DB2HAICU, NO RELATIONSHIP IS CREATED FOR FULLY QUALIFIED HOSTNAME IN THE "HOSTNAME" COMMAND. SQL5043N DURING DB2START.

DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as fixed if next.

Error description

• Users Affected:
  Only systems with fully qualified hostname displayed in the
  "hostname" command are affected. The SQL5043N message affects
  HADR instances only.
  
  Problem Description:
  (a) When using db2haicu to set up cluster objects, no
  relationship is created from the network resource (e.g. "lsrel"
  will show that there was no dependency created) for systems that
  displays a fully qualified hostname in the "hostname" output.
  (b) The following problem may be encountered during db2start,
  user may see this message:
  SQL5043N - Support for one or more communications protocols
  failed to start successfully. However, core database manager
  functionality started successfully.
  Here is the error in the db2diag.log:
  2009-06-05-15.05.18.234579+120 I50905E462          LEVEL: Info
  PID     : 23614                TID  : 47341753367856PROC :
  db2star2
  INSTANCE: db2inst1              NODE : 000
  FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure,
  sqlhaQueryObjectUsingAttribute, probe:200
  MESSAGE : DB2 HA Infrastructure query for Resource Name given
  Instance Name:
  DATA #1 : unsigned integer, 4 bytes
  8
  DATA #2 : String, 7 bytes
  db2itar
  DATA #3 : unsigned integer, 4 bytes
  0
  2009-06-05-15.05.18.249279+120 E51368E377          LEVEL: Error
  PID     : 23614                TID  : 47341753367856PROC :
  db2star2
  INSTANCE: db2inst1              NODE : 000
  FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure,
  sqlhaOnlineDB2Partition, probe:70
  RETCODE :
  ECF=0x90000552=-1879046830=ECF_SQLHA_OBJECT_DOES_NOT_EXIST
            Cluster object does not exist
  2009-06-05-15.05.18.273718+120 I51746E268          LEVEL: Info
  PID     : 23614                TID  : 47341753367856PROC :
  db2star2
  INSTANCE: db2inst1              NODE : 000
  FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure,
  sqlhaOnlineDB2Partition, probe:160
  2009-06-05-15.05.18.273846+120 I52015E450          LEVEL: Info
  PID     : 23614                TID  : 47341753367856PROC :
  db2star2
  INSTANCE: db2inst1              NODE : 000
  FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure,
  sqlhaOnlineDB2Partition, probe:9999
  MESSAGE :
  ECF=0x90000552=-1879046830=ECF_SQLHA_OBJECT_DOES_NOT_EXIST
            Cluster object does not exist
  DATA #1 : String, 7 bytes
  db2itar
  DATA #2 : unsigned integer, 4 bytes
  0
  
  The error may lead to the lack of "unlock" of the resource
  group. Also, during db2stop, there may be a similar error
  message regarding sqlhaOfflineDB2Partition that leads to no
  "lock"ing of the resource group.
  (a lock is needed during manual db2stop to disable TSA
  activities on that resource group).
  
  2009-03-12-16.29.15.258093+060 I104748E462         LEVEL: Info
  PID     : 30347                TID  : 46991441861312PROC :
  db2stop2
  INSTANCE: db2itst db2inst1             NODE : 000
  FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure,
  sqlhaQueryObjectUsin
  gAttribute, probe:200
  MESSAGE : DB2 HA Infrastructure query for Resource Name given
  Instance Name:
  DATA #1 : unsigned integer, 4 bytes
  8
  DATA #2 : String, 7 bytes
  db2itst
  DATA #3 : unsigned integer, 4 bytes
  0
  2009-03-12-16.29.15.270804+060 E105211E378         LEVEL: Error
  PID     : 30347                TID  : 46991441861312PROC :
  db2stop2
  INSTANCE: db2itst db2inst1             NODE : 000
  FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure,
  sqlhaOfflineDB2Partition, probe:70
  RETCODE :
  ECF=0x90000552=-1879046830=ECF_SQLHA_OBJECT_DOES_NOT_EXIST
            Cluster object does not exist
  
  
  
  
  First fixed in v95fp5
  

Local fix

• (a) Manually create the relationship (only need to do this once
  during cluster setup)
    chrg -o Offline -s "Name = '<instance_rg_name>'"
    mkrel -p DependsOn -S IBM.Application:<instance_rs_name> -G
  IBM.Equivalency:<network_equ_name>
  <instance_rs_name>_DependsOn_<network_equ_name>-rel
    chrg -o Online -s "Name = '<instance_rg_name>'"
  (b) As root:
  Instead of db2stop, use TSA command: chrg -o offline
  <instance_rg_name>
  Instead of db2start, use TSA command: chrg -o online
  <instance_rg_name>
  

Problem summary

• First fixed in v95fp5
  

Problem conclusion

Temporary fix

Comments

APAR Information

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

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

  IC62233

Fix information

Applicable component levels

• R950 PSY

     UP