home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC87247 Status: Closed

DB2HAICU FAILS "ECF_SQLHA_HADR_VALIDATION_FAILED" ERROR WHEN FQDN
ARE USED FOR HOST NAMES.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When FQDN names are being used for host names, db2haicu fails to 
recognize the hosts and fails with 
ECF_SQLHA_HADR_VALIDATION_FAILED error. 
 
 
db2haicu output from Primary server: 
 
db2haicu is collecting information on your current setup. This 
step may take some time as db2haicu will need to activate all 
databases for the instance to discover all paths ... 
Configuring quorum device for domain 'DB2HADR_PRD' ... 
Configuring quorum device for domain 'DB2HADR_PRD' was 
successful. 
Adding network interface card 'en0' on cluster node 
'sample.domainname.net' to the network 'db2_public_network_0' 
... 
NIC 'en0' cannot be added to network 'db2_public_network_0' 
because it does not belong to the same physical network as the 
other NICs in the network. 
Adding network interface card 'en0' on cluster node 
'sample1.domainname.net' to the network 'db2_private_network_1' 
... 
NIC 'en0' cannot be added to network 'db2_private_network_1' 
because it does not belong to the same physical network as the 
other NICs in the network. 
Adding DB2 database partition '0' to the cluster ... 
Adding DB2 database partition '0' to the cluster was successful. 
Adding HADR database 'SAMPLE' to the domain ... 
HADR database 'SAMPLE' cannot be added to the cluster because 
the standby instance is not configured in the domain. Run 
db2haicu on the standby instance to configure it into the shared 
file system cluster. 
 
db2diag entries from Primary db look like: 
 
2012-09-25-20.46.03.649839-240 I134793A498          LEVEL: Info 
PID     : 9633866              TID : 1              PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: sample.domainname.net 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, 
sqlhaGetObjectAttribute2, probe:200 
MESSAGE : Getting object attribute for HA function 
DATA #1 : unsigned integer, 4 bytes 
8 
DATA #2 : unsigned integer, 4 bytes 
4 
DATA #3 : String, 3 bytes 
en0 
DATA #4 : unsigned integer, 4 bytes 
4 
 
2012-09-25-20.46.03.685905-240 E135292A355          LEVEL: Info 
PID     : 9633866              TID : 1              PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: sample.domainname.net 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, 
sqlhaTearDownHAInfrastructure, probe:50 
MESSAGE : db2havend process has been terminated 
 
2012-09-25-20.46.03.686496-240 I135648A447          LEVEL: Info 
PID     : 9633866              TID : 1              PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: sample.domainname.net 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, sqlhaListClusterObject, 
probe:4011 
DATA #1 : unsigned integer, 4 bytes 
10 
DATA #2 : String, 0 bytes 
Object not dumped: Address: 0x0FFFFFFFFFF98AD0 Size: 0 Reason: 
Zero-length data 
 
 
2012-09-25-20.46.20.878265-240 E239966A408          LEVEL: Info 
PID     : 9633866              TID : 1              PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: sample.domainname.net 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, 
sqlhaUIListAllPartitionsOnlineAtNode, probe:100 
DATA #1 : String, 30 bytes 
sample1.domainname.net 
DATA #2 : String, 8 bytes 
sample 
 
2012-09-25-20.46.20.878858-240 E240375A711          LEVEL: Error 
PID     : 9633866              TID : 1              PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: sample.domainname.net 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, sqlhaUICreateHADR, 
probe:900 
RETCODE : 
ECF=0x9000056F=-1879046801=ECF_SQLHA_HADR_VALIDATION_FAILED 
          The HADR DB failed validation before being added to 
the cluster 
MESSAGE : Please verify that HADR_REMOTE_INST and 
HADR_REMOTE_HOST are correct 
          and in the exact format and case as the Standby 
instance name and 
          hostname. 
DATA #1 : String, 8 bytes 
db2inst1 
DATA #2 : String, 30 bytes 
sample.domainname.net 
 
2012-09-25-20.46.20.879366-240 E241087A659          LEVEL: Error 
PID     : 9633866              TID : 1              PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: sample.domainname.net 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, sqlhaUICreateHADR, 
probe:900 
RETCODE : 
ECF=0x9000056F=-1879046801=ECF_SQLHA_HADR_VALIDATION_FAILED 
          The HADR DB failed validation before being added to 
the cluster 
DATA #1 : String, 8 bytes 
db2inst1 
DATA #2 : String, 8 bytes 
db2inst1 
DATA #3 : String, 30 bytes 
sample.domainname.net 
DATA #4 : String, 30 bytes 
sample1.domainname.net 
DATA #5 : String, 5 bytes 
SAMPLE 
 
2012-09-25-20.46.20.879994-240 E241747A544          LEVEL: Info 
PID     : 9633866              TID : 1              PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: sample.domainname.net 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, sqlhaUICreateHADR, 
probe:900 
MESSAGE :  Create HADR end... 
DATA #1 : String, 8 bytes 
db2inst1 
DATA #2 : String, 8 bytes 
db2inst1 
DATA #3 : String, 30 bytes 
sample.domainname.net 
DATA #4 : String, 30 bytes 
sample1.domainname.net 
DATA #5 : String, 5 bytes 
SAMPLE 
 
2012-09-25-20.46.20.880548-240 E242292A767          LEVEL: Error 
PID     : 9633866              TID : 1              PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME:sample.domainname.net 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, handleStartElement, 
probe:8000 
MESSAGE : 
ECF=0x9000056F=-1879046801=ECF_SQLHA_HADR_VALIDATION_FAILED 
          The HADR DB failed validation before being added to 
the cluster 
DATA #1 : String, 40 bytes 
Error during HADR Cluster configuration. 
DATA #2 : String, 8 bytes 
db2inst1 
DATA #3 : String, 8 bytes 
db2inst1 
DATA #4 : String, 30 bytes 
sample.domainname.net 
DATA #5 : String, 30 bytes 
sample1.domainname.net 
DATA #6 : String, 5 bytes 
SAMPLE 
DATA #7 : unsigned integer, 8 bytes 
1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on DB2 V10 FP1 or earlier                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10 FP2                                       * 
****************************************************************
Local Fix:
As a temporary workaround, use short names for host names 
instead of fully qualified domain names.
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 FP2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.10.2012
31.10.2012
31.10.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList