|
Problem IC61905
|
Status: Closed |
IN XML MODE, DB2HAICU WILL FAIL WITH ERROR IF THE DATABASENAME ATTRIBUTE VALUE IS NOT IN UPPER CASE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
In XML mode, db2haicu will fail if the user input value for the
database name is not in upper case letters.
In HADR case, db2haicu will fail during the primary instance
setup.
For example:
<HADRDBSet>
<HADRDB databaseName"testdb" localInstance="db2inst1"
remoteInstance="db2inst1" localHost="hostA" remoteHost="hostB"
/>
</HADRDBSet>
To resolve this, simply change the XML clause to:
<HADRDBSet>
<HADRDB databaseName"TESTDB" localInstance="db2inst1"
remoteInstance="db2inst1" localHost="hostA" remoteHost="hostB"
/>
</HADRDBSet>
This defect does not affect interactive mode. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* db2haicu XML mode user only *
****************************************************************
* PROBLEM DESCRIPTION: *
* In XML mode, db2haicu will fail if the user input value for *
* the database name is not in upper case letters. *
* In HADR case, db2haicu will fail during the primary instance *
* setup. *
* *
* For example: *
* *
* <HADRDBSet> *
* <HADRDB databaseName"testdb" localInstance="db2inst1" *
* remoteInstance="db2inst1" localHost="hostA" *
* remoteHost="hostB" /> *
* </HADRDBSet> *
* *
* To resolve this, simply change the XML clause to: *
* *
* <HADRDBSet> *
* <HADRDB databaseName"TESTDB" localInstance="db2inst1" *
* remoteInstance="db2inst1" localHost="hostA" *
* remoteHost="hostB" /> *
* </HADRDBSet> *
* *
* This defect does not affect interactive mode. *
****************************************************************
* RECOMMENDATION: *
* Manually change the databaseName value to upper case *
* letters. *
**************************************************************** |
| Local Fix: |
Change the XML file to use upper case for the databaseName
attribute value. |
| available fix packs: |
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
|
| Solution |
The problem was first fixed in version 9.5 fix pack 5. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC63292
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.07.2009
21.12.2009
21.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.5
|
 |
