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

A LOAD OPERATION FROM CURSOR WHICH CONSISTS OF DATA WITH BAD CHARACTERS
CAUSES DB2 TO CRASH.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
A load operation happens between 2 tables with different 
datatypes - CHAR/VARCHAR and GRAPHIC/VARGRAPHIC respectively. 
The LOAD from CURSOR does implicit codepage conversion due to 
loading from CHAR columns (codepage 1208) to GRAPHIC columns 
(codepage 1200). When bad character data is hit during this load 
operation , the load is unable to handle this error condition 
which leads the DB2 server to crash. 
 
This problem can also occur between 2 tables with the same 
datatypes, if they are from different databases with different 
codepages, and the LOAD from CURSOR DATABASE does implicit 
codepage conversion. 
 
The stack trace of the trapping process looks similar to this: 
... 
(maybe some trap handling function here) 
(maybe a _memmove or an unknown function here) 
_ZN16sqluCCrossParser11zColConvertEbPPj + 0xbb0 
_ZN16sqluCCrossParser12zParseColumnEbPcmPmPb + 0x1dc0 
_Z8sqlulxrrP8SQLD_TCBPP10SQLD_VALUEP8sqlulxwa + 0x600 
_Z23sqluGetAndFormatRecordsP8sqlulacbP13SQLUCACB_TYPEP17SQLU_FOR 
MATTER_CBjPPhiP10sqlz_valueS5_PP10SQLD_VALUESB_Pi 
+ 0x13b0 
_Z8sqluldatPhj + 0xce0 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V9.5                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A  LOAD OPERATION FROM CURSOR WHICH CONSISTS OF DATA WITH    * 
* BAD CHARACTERS CAUSES DB2 TO CRASH.                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.5fp6                                       * 
****************************************************************
Local Fix:
available fix packs:
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
Fixed in DB2 V9.5fp6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.03.2010
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)
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.