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

AN INVALID CASTING ERROR IN AN XMLTABLE SHOULD FAIL WITH SQL16061,
BUT THE TRANSACTION WAS ROLLED BACK INSTEAD

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A query from an XMLTABLE is supposed to fail with SQL16061 if 
there's an invalid casting.  However, the entire transaction was 
rolled back instead. 
 
Here is an example of such query: 
 
select max(u."mswt") as max1 from 
TABLE(MON_GET_WORKLOAD_DETAILS(CAST(NULL AS BIGINT),-2)) as p, 
XMLTABLE(XMLNAMESPACES(DEFAULT 
'http://www.ibm.com/xmlns/prod/db2/mon'), '$doc/db2_workload' 
PASSING xmlparse (document p.DETAILS) AS "doc" COLUMNS "mswt" 
     BIGINT       PATH 'workload_name') AS U; 
 
Column "mswt" in the above example is of type character, and 
therefore cannot be cast to BIGINT.  The following error should 
have been returned: 
 
SQL16061N  The value "SYSDEFAULTUSERWORKLOAD" cannot be 
constructed as, or 
cast (using an implicit or explicit cast) to the data type 
"xs:long". Error 
QName=err:FORG0001.  SQLSTATE=10608 
 
However, the following  error was returned, and the entire 
transaction was rolled back: 
 
SQL1476N  The current transaction was rolled back because of 
error "-16061". 
SQLSTATE=40506
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See APAR description                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Users should upgrade to V97 Fp2                              * 
****************************************************************
Local Fix:
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 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
This problem is fixed V97 Fp2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.05.2010
22.06.2010
22.06.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