|
Problem IC65066
|
Status: Closed |
A LOAD OPERATION FROM CURSOR WHICH CONSISTS OF DATA WITH BAD CHARACTERS CAUSES DB2 TO CRASH. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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: *
* All DB2 V9.7 *
****************************************************************
* PROBLEM DESCRIPTION: *
* A LOAD OPERATION FROM CURSOR WHICH CONSISTS OF DATA WITH *
* BADCHARACTERS CAUSES DB2 TO CRASH.A load operation happens *
* between 2 tables with differentdatatypes - CHAR/VARCHAR and *
* GRAPHIC/VARGRAPHICrespectively. The LOAD from CURSOR does *
* implicit codepageconversion due to loading from CHAR columns *
* (codepage 1208)to GRAPHIC columns (codepage 1200). When bad *
* character datais hit during this load operation, the load is *
* unable tohandle this error condition which leads the DB2 *
* server tocrash.This problem can also occur between 2 tables *
* with the samedatatypes, if they are from different databases *
* withdifferent codepages, and the LOAD from CURSOR DATABASE *
* doesimplicit codepage conversion.The stack trace of the *
* trapping process looks similar tothis:...(maybe some trap *
* handling function here)(maybe a _memmove or an unknown *
* function here)_ZN16sqluCCrossParser11zColConvertEbPPj + *
* 0xbb0_ZN16sqluCCrossParser12zParseColumnEbPcmPmPb + *
* 0x1dc0_Z8sqlulxrrP8SQLD_TCBPP10SQLD_VALUEP8sqlulxwa + *
* 0x600_Z23sqluGetAndFormatRecordsP8sqlulacbP13SQLUCACB_TYPEP17S
* 0x13b0_Z8sqluldatPhj + 0xce0... *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7fp2 *
**************************************************************** |
| 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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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 |
Fixed in V9.7fp2 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67134 IC67165 IC67166
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.12.2009
25.05.2010
25.05.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
|
 |
