|
Problem IC61706
|
Status: Closed |
DB2 FAILS WITH SQL1224N WHEN REGISTERING XML SCHEMA WITH MAXOCCURS="500000" |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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"). |
| 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 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
|
| Solution |
Problem was first fixed in Version v9.5 Fix Pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.06.2009
17.02.2010
17.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP5,
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
