Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC92391 Status: Closed

IN A DB2 HA ENVIRONMENT, IF DB2HAICU IS SETUP WITH FQHN, DB2START CAN FAIL
WITH SQL6048N

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In a DB2 HA environment, with db2haicu setup with FQHN, db2start 
can fail with SQL6048N. 
 
db2diag.log shows: 
-- 
2013-05-16-13.57.48.492925+000 E463019E411           LEVEL: 
Error 
PID     : 41303                TID : 47183451397632  PROC : 
db2start 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: xxxyyyzzz.lenexa.ibm.com 
FUNCTION: DB2 UDB, high avail services, 
sqlhaGetInfoForClusterObject, probe:4651 
RETCODE : 
ECF=0x90000552=-1879046830=ECF_SQLHA_OBJECT_DOES_NOT_EXIST 
          Cluster object does not exist 
 
2013-05-16-13.57.48.517166+000 E463431E348           LEVEL: Info 
PID     : 41303                TID : 47183451397632  PROC : 
db2start 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: xxxyyyzzz.lenexa.ibm.com 
FUNCTION: DB2 UDB, high avail services, 
sqlhaTearDownHAInfrastructure, probe:50 
MESSAGE : db2havend process has been terminated 
 
2013-05-16-13.57.48.517307+000 I463780E948           LEVEL: 
Severe 
PID     : 41303                TID : 47183451397632  PROC : 
db2start 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: xxxyyyzzz.lenexa.ibm.com 
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, 
probe:1103 
MESSAGE : 
ZRC=0x827300CF=-2106392369=HA_ZRC_OBJECT_DOES_NOT_EXIST 
          "Cluster object does not exist" 
DATA #1 : String, 31 bytes 
failed to obtain the host state 
DATA #2 : String, 64 bytes 
/home/db2inst1/sqllib/adm/db2rstar db2profile db2star2 SN 0 0 CM 
DATA #3 : String, 14 bytes 
xxxyyyzzz 
DATA #4 : Hexdump, 4 bytes 
0x00007FFFDFF09A50 : 1000 0000 
.... 
DATA #5 : Hexdump, 36 bytes 
0x00007FFFDFEE75F8 : C8F4 E9C6 E92A 0000 7336 3038 3433 326E 
.....*..xxxyyyzz 
0x00007FFFDFEE7608 : 6A33 736C 3330 0000 0000 0000 0000 0000 
z............... 
0x00007FFFDFEE7618 : 0000 0000 
.... 
 
2013-05-16-13.57.48.517447+000 I464729E331           LEVEL: 
Event 
PID     : 41303                TID : 47183451397632  PROC : 
db2start 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: xxxyyyzzz.lenexa.ibm.com 
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, 
probe:7183 
DATA #1 : signed integer, 4 bytes 
-6048 
 
== 
 
This is because DB2 is querying the RSCT IBM.PeerNode resource 
using the short hostname format which does not match the FQHN, 
since db2haicu was defined with FQHN. 
 
# lsrsrc IBM.PeerNode 
Resource Persistent Attributes for IBM.PeerNode 
resource 1: 
        Name               = "xxxyyyzzz.lenexa.ibm.com" 
        NodeList           = {2} 
        RSCTVersion        = "3.1.2.7" 
        ClassVersions      = {} 
        CritRsrcProtMethod = 0 
        IsQuorumNode       = 1 
        IsPreferredGSGL    = 1 
        NodeUUID           = "" 
        ActivePeerDomain   = "db2HAdomain" 
        NodeNameList       = {"xxxyyyzzz.lenexa.ibm.com"}
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 FixPack 3 or higher                     * 
****************************************************************
Local Fix:
Change the hostname; /etc/hosts; uname and 
/etc/sysconfig/network to use short name. Delete and recreate 
the cluster using shortname
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 v10.1 FixPack 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC96562 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.05.2013
08.10.2013
08.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList