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 IC63319 Status: Closed

DB2HAICU INPUT FILE XML SCHEMA DEFINITION IS INCORRECT.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Per the current db2haicu input file XML schema definition, we 
can specify one or more 'HADRDB' elements within a 'HADRDBSet' 
in order to add multiple HADR databases under one single 
instance. This is because the HADRDB element is unbounded. The 
current schema does not accurately describe the model. But when 
using a XML file with this definition, db2haicu will fail with 
the following error during the end of the cluster setup. 
 
There was an error processing the XML file . Refer to 
db2diag.log and the DB2 Information Center for details. 
 
The corresponding db2diag.log entries would look like: 
 
2009-04-22-14.40.40.675268-240 E9889A407          LEVEL: Error 
PID     : 1814532              TID  : 1           PROC : 
db2haicu 
INSTANCE: inst1                NODE : 000 
EDUID   : 1 
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, 
sqlhaErrorHandler::error, probe:10 
DATA #1 : <preformatted> 
Error during XML parsing: Element 'HADRDB' is not valid for 
content model: '(HAD 
RDB,VirtualIPAddress)' 
 
2009-04-22-14.40.40.675976-240 I10297A316         LEVEL: Error 
PID     : 1814532              TID  : 1           PROC : 
db2haicu 
INSTANCE: inst1                NODE : 000 
EDUID   : 1 
FUNCTION: <0>, <0>, <0>, probe:100 
RETCODE : ZRC=0x800002FF=-2147482881=SQLZ_RC_E16196_31 
          "generated for the xml4c errors" 
 
Example: 
 
Let us say you have an XML file with the following content: 
 
<HADRDBSet> 
    <HADRDB databaseName="SAMPLEDB1" localInstance="inst1" 
remoteInstance="inst1" localHost="HAHOST1" remoteHost="HAHOST2" 
/> 
    <HADRDB databaseName="SAMPLEDB2" localInstance="inst1" 
remoteInstance="inst1" localHost="HAHOST1" remoteHost="HAHOST2" 
/> 
</HADRDBSet> 
 
In order to successfully add these databases, which are under 
the same instance 'inst1', we need to specify separate HADRDB 
sets like below. 
 
<HADRDBSet> 
  <HADRDB databaseName="SAMPLEDB1" localInstance="inst1" 
remoteInstance="inst1" localHost="HAHOST1" remoteHost="HAHOST2" 
/> 
</HADRDBSet> 
<HADRDBSet> 
  <HADRDB databaseName="SAMPLEDB2" localInstance="inst1" 
remoteInstance="inst1" localHost="HAHOST1" remoteHost="HAHOST2" 
/> 
</HADRDBSet>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2HAICU INPUT FILE XML SCHEMA DEFINITION IS INCORRECT.      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 9.7 FP1                                           * 
****************************************************************
Local Fix:
Use the db2haicu interactive mode to setup clusters for multiple 
HADR databases that are under one instance.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.09.2009
22.12.2009
22.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList