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 IC61706 Status: Geschlossen

DB2 FAILS WITH SQL1224N WHEN REGISTERING XML SCHEMA WITH
MAXOCCURS="500000"

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When there is not enough storage to complete registration of an 
XML schema due to a large value specified for the facet 
maxOccurs, DB2 fails with SQL1224N and message ADM0502C is 
logged in the db2diag.log.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If an XML schema that is registered in the DB2 XSR uses the  * 
* maxOccurs attribute where the value is greater than 5000,    * 
* the maxOccurs attribute value is treated as if you specified * 
* "unbounded". Because document elements that have a maxOccurs * 
* attribute value that is greater than 5000 are processed as   * 
* if you specified "unbounded", an XML document might pass     * 
* validation when you use the XMLVALIDATE function even if the * 
* number of occurrences of an element exceeds the maximum      * 
* according to the XML schema that you used to validate the    * 
* document.                                                    * 
*                                                              * 
* If you use an XML schema that defines an element that has a  * 
* maxOccurs attribute value that is greater than 5000 and you  * 
* want to reject XML documents that have a maxOccurs attribute * 
* value greater than 5000, you can define a trigger or         * 
* procedure to check for that condition. In the trigger or     * 
* procedure, use an XPath expression to count the number of    * 
* occurrences of the element and return an error if the number * 
* of elements exceeds the maxOccurs attribute value.           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version v9.7 Fix Pack 1                           * 
****************************************************************
Local-Fix:
To register the XML schema, change the facet maxOccurs to 
"unbounded" (maxOccurs="unbounded").
verfügbare FixPacks:
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 6 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 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

Lösung
Problem was first fixed in Version v9.5 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.06.2009
17.02.2010
17.02.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP5,
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList