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

V9FP3: XML SCHEMA REGISTRATION DIALOG DOES NOT HANDLE NON-ORDINA RY
IDENTIFIERS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If a non-ordinary identifier such as "SCHEMA-ONE" is used to 
register an XML schema or DTD through the Control Center, the 
command generated by the Control Center will not correctly 
quote the identifier, leading to a syntax error from the DB2 
engine when the command is executed.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Control Center users                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If a non-ordinary identifier such as "SCHEMA-ONE" is used    * 
* toregister an XML schema or DTD through the Control          * 
* Center,thecommand generated by the Control Center will not   * 
* correctlyquote the identifier, leading to a syntax error     * 
* from the DB2engine when the command is executed.             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* apply DB2 v9.7 FixPack 2.                                    * 
****************************************************************
Local Fix:
1.  Use only ordinary identifiers when registering XML schema or 
 DTD through the Control Center, or 
2.  Use the "Show SQL" function to preview the registration comm 
ands,  then copy the commands to the CLP or Command Center and m 
odify them appropriately so that any non-ordinary identifiers ar 
e properly quoted.
available fix packs:
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 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
fixed in DB2 v9.7 FP2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.01.2010
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList