Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC61734 Status: Closed

SCHEMA REGISTRATION FAILS WITH SQL16157N WHEN XML SCHEMA INVOLVES
ANY COMPARISON BETWEEN 0,0.0 OR -0.0

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When a XML schema contains boundary facets that have different 
representations of the number zero, DB2 schema registration 
fails with SQL16157N.  When an XML instance is validated 
againsta schema which requires comparison between 0, 0.0 or 
-0.0, validation fails with SQL16210N. 
 
Example 1: the following schema will fail to register 
because the facets minInclusive and minExclusive have three 
different representations for the value zero (0, 0.0 and 
-0.0). 
 
--schema 
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> 
 
<xs:simpleType name="baseType"> 
<xs:restriction base="xs:decimal"> 
<xs:minInclusive value="0.0" /> 
</xs:restriction> 
</xs:simpleType> 
 
<xs:simpleType name="restrictedTypeGTZero"> 
<xs:restriction base="baseType"> 
<xs:minExclusive value="0" /> 
</xs:restriction> 
</xs:simpleType> 
 
<xs:simpleType name="restrictedTypeGTNegativeFractionalZero"> 
<xs:restriction base="baseType"> 
<xs:minExclusive value="-0.0" /> 
</xs:restriction> 
</xs:simpleType> 
 
<xs:element name="decimalGreaterThanZero" 
type="restrictedTypeGTZero" /> 
<xs:element name="decimalGreaterThanNegativeFractionalZero" 
type="restrictedTypeGTNegativeFractionalZero" /> 
 
</xs:schema> 
 
Example 2: the following XML instance will fail to validate 
against the following schema because the XML instance 
represents the number zero differently than the schema (0 vs 
0.0). 
 
--xml instance 
<decimalGreaterThanOrEquealFractionalZero>0</decimalGreaterThanO 
rEquealFractionalZero> 
 
 
--schema 
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> 
 
<xs:simpleType name="baseType"> 
<xs:restriction base="xs:decimal"> 
<xs:minInclusive value="0.0" /> 
</xs:restriction> 
</xs:simpleType> 
 
<xs:element name="decimalGreaterThanOrEquealFractionalZero" 
type="baseType" /> 
 
</xs:schema>
Problem Summary:
Local Fix:
To avoid any comparison between 0, 0.0 and -0.0, consistently 
 
use only one representation of the number zero (0, 0.0 or 
-0.0) in the XML schemas and XML instances.
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
Workaround
not known / see Local fix
Comment
SCHEMA REGISTRATION FAILS WITH SQL16157N WHEN XML SCHEMA 
INVOLVES ANY COMPARISON BETWEEN 0,0.0 OR -0.0
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.06.2009
25.02.2010
25.02.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.5 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.