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

FORCED DATABASE SHUTDOWN WHEN RUNNING SELECT WITH XML2CLOB FUNCTION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Running SQL query with XML2CLOB function might cause a forced 
database shutdown. 
 
e.g. 
select * from DB2V1012.XMLTABLE where xml2clob(xml) 
 
 
In the db2diag.log file you will see following error: 
 
2014-03-17-17.17.54.640849+060 I173744A545          LEVEL: Error 
PID     : 33620126             TID : 119741         PROC : 
db2sysc 0 
INSTANCE: db2v1012             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-31375              APPID: 
10.2.173.236.52399.140317161334 
AUTHID  : DB2V1012             HOSTNAME: aix 
EDUID   : 119741               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, runtime interpreter, sqlriXmlClob, probe:110 
MESSAGE : ZRC=0x870F00C0=-2029059904=SQLO_DBCSTRUNC 
          "last unconverted char is truncated" 
 
 
The EDU trap will look like following: 
 
 pthread_kill 
 sqloDumpEDU 
 sqleDoForceDBShutdownFODC 
 ForceDBShutdown 
 sqlrr_rds_common_post 
 sqlrr_fetch 
 sqljs_ddm_cntqry 
 sqljsParseRdbAccessed 
 sqljsParse 
 sqljsSqlam 
 sqljsDriveRequests 
 sqljsDrdaAsInnerDriver 
 sqljsDrdaAsDriver 
 RunEDU 
 EDUDriver 
 sqlzRunEDU 
 sqloEDUEntry
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FixPack 5                               * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 V10.1 FixPack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2014
22.12.2016
22.12.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList