home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC61905 Status: Geschlossen

IN XML MODE, DB2HAICU WILL FAIL WITH ERROR IF THE DATABASENAME ATTRIBUTE
VALUE IS NOT IN UPPER CASE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
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

Lösung
The problem was first fixed in version 9.5 fix pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC63292 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.07.2009
21.12.2009
21.12.2009
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP5
Problem behoben lt. FixList in der Version
9.5.0.5 FixList