DB2 - Problem description
Problem IC61603 | Status: Closed |
XS:DOUBLE(<INPUT STRING>) RETUNS SQL0901N WHEN THE <INPUT STRING> TERMINATES WITH "+" OR "-", FOR EXAMPLE XS:DOUBLE("8E+") | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
xs:double is returning a -901 system error for a malformed input to xs:double() which is incorrect and very misleading to the user. Because 8E+ is not in a valid lexical representation for xs:double (From the spec 3.2.5.1 Lexical representation http://www.w3.org/TR/xmlschema-2/#double) we should be returning the SQL16061N error below. SQL16061N The value "" cannot be constructed as, or cast (using an implicit or explicit cast) to the data type "xs:double". Error QName=err:FORG0001. SQLSTATE=10608 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 LUW All Platforms * **************************************************************** * PROBLEM DESCRIPTION: * * xs:double is returning a -901 system error for a malformed * * input * * to xs:double() which is incorrect and very misleading to the * * user. * * * * Because 8E+ is not in a valid lexical representation for * * xs:double (From the spec 3.2.5.1 Lexical representation * * http://www.w3.org/TR/xmlschema-2/#double) we should be * * returning * * the SQL16061N error below. * * * * SQL16061N The value "" cannot be constructed as, or cast * * (using * * an implicit * * or explicit cast) to the data type "xs:double". Error * * QName=err:FORG0001. * * SQLSTATE=10608 * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v95 Fixpack 5. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
The fix catches the malformed input and raises the correct error. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.06.2009 19.02.2010 19.02.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.5 |