DB2 - Problem description
| Problem IC87471 | Status: Closed |
USING FQDN FOR NODE NAMES DURING DB2HAICU SETUP IS BROKEN | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
Using Fully Qualified Domain Names(FQDN) for node names during
db2haicu setup is broken.
Attempted to run both the db2haicu interactive interface and the
db2haicu XML
input file methods using FQDN and it fails.
db2haicu -f db2ha_HADR.xml
Welcome to the DB2 High Availability Instance Configuration
Utility (db2haicu).
You can find detailed diagnostic information in the DB2 server
diagnostic log file called db2diag.log. Also, you can use the
utility called db2pd to query the status of the cluster domains
you create.
For more information about configuring your clustered
environment using db2haicu, see the topic called 'DB2 High
Availability Instance Configuration Utility (db2haicu)' in the
DB2 Information Center.
db2haicu determined the current DB2 database manager instance is
'db2inst1'. The cluster configuration that follows will apply to
this instance.
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 ...
The local hostname 'hostA' is not part of the host list passed
in. Re-run the command and provide the local hostname in
the host list.
There was an internal db2cluster error. Refer to the diagnostic
logs (db2diag.log or /tmp/ibm.db2.cluster.*) and the DB2
Information Center for details.
[db2inst1@xxx]$ db2level
DB21085I Instance "db2inst1" uses "64" bits and DB2 code
release "SQL10010"
with level identifier "0201010E".
Informational tokens are "DB2 v10.1.0.0", "s120403",
"LINUXAMD64101", and Fix
Pack "0".
Product is installed at "/opt/ibm/db2/V10.1".
db2diag.log snippet:
2012-04-27-17.37.51.670826-240 E1018418E449 LEVEL:
Error
PID : 6471 TID : 139994365077280 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME: hostA.torolab.ibm.com
FUNCTION: DB2 UDB, high avail services, sqlhaUICreateDomain,
probe:3329
RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
Invalid parameter
DATA #1 : String, 11 bytes
db2HAdomain
DATA #2 : signed integer, 4 bytes
2
2012-04-27-17.37.51.670940-240 E1018868E361 LEVEL: Info
PID : 6471 TID : 139994365077280 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME: hostA.torolab.ibm.com
FUNCTION: DB2 UDB, high avail services, sqlhaUICreateDomain,
probe:3329
DATA #1 : String, 11 bytes
db2HAdomain
DATA #2 : signed integer, 4 bytes
2
2012-04-27-17.37.51.671024-240 E1019230E590 LEVEL:
Severe
PID : 6471 TID : 139994365077280 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME: hostA.torolab.ibm.com
FUNCTION: DB2 UDB, high avail services, handleEndElement,
probe:1200
MESSAGE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
Invalid parameter
DATA #1 : String, 58 bytes
Error during Domain creation from HA XML input processing.
DATA #2 : String, 11 bytes
db2HAdomain
DATA #3 : unsigned integer, 4 bytes
2
DATA #4 : String, 27 bytes
hostA.torolab.ibm.com | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 10.1 Fixpack 4 * **************************************************************** | |
| Local Fix: | |
Use short hostname values. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.10.2012 01.01.2013 01.01.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.2 |
|
| 10.5.0.2 |
|