|
Problem IC88304
|
Status: Closed |
INSERTING DATA INTO VARCHAR COLUMN, FAILS IN CLI DRIVER WITH CLI0109E ON THE UNICODE CODESET CLIENT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If a multi-byte code string is inserted into VARCHAR data type
column through a parameter marker like below on the unicode
codeset client, it fails in CLI layer with "CLI0109E String data
right truncation" error when the database codeset is different
from the client.
Currently this fix requires "Patch2=82" in db2cli.ini and it
can be made by a "UPDATE CLI CFG" command like below.
UPDATE CLI CFG FOR SECTION COMMON USING Patch2 82
Sample SQL :
INSERT INTO T1(COL_VARCHAR) VALUES(?);
CLI error message :
(-99999): [IBM][CLI Driver] CLI0109E String data right
truncation.
And db2trc shows the following SQLZ_RC_STRING_TRUNCATED error
return code in CLI_callbDrdaInput.
476690 ... | sqljrGenSqlDta data [probe 10]
476691 ... | | CLI_callbDrdaInput entry
476692 ... | | | sqljrDrdaArGetWriteBufferPtr entry
476693 ... | | | sqljrDrdaArGetWriteBufferPtr data [probe 10]
476694 ... | | | sqljrDrdaArGetWriteBufferPtr exit
476695 ... | | CLI_callbDrdaInput data [probe 100]
476696 ... | | | CLI_errStoreError entry
476697 ... | | | CLI_errStoreError data [probe 999]
476698 ... | | | CLI_errStoreError exit
476699 ... | | | unknown error [probe 164] [ ZRC = 0x8800000A =
-2013265910 = SQLZ_RC_STRING_TRUNCATED] |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* CLI user on connecting to the different codepage database *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 Version 10.1 FixPack 2 *
**************************************************************** |
| Local Fix: |
Use the same codeset on the client as the database codeset.
ex, export DB2CODEPAGE=< database codepage > and recycle the
application |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 10.1 FixPack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.11.2012
19.12.2012
19.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
