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

SQLCOLUMNS CLI FUNCTION MAY NOT WORK ON A TABLE NAME THAT INCLUDES MBCS
CHARACTERS

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
The CLI function, SYSIBM.SQLCOLUMNS may return no data for a
table whose table name includes MBCS characters.

This problem originally happened for the following environment.
However, this problem may happen in different environments.

The database codepage was UTF-8.
The client codepage was IBM-943.
The table name had U+8868 + U+005F.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of DBCS, non-Unicode databases                         *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 version 11.5.7.0 and run db2updv115 on        *
* existing DBCS, non-Unicode databases                         *
****************************************************************
Local Fix:
Set the client codepage same as the databses codepage.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of DBCS, non-Unicode databases                         *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 version 11.5.7.0 and run db2updv115 on        *
* existing DBCS, non-Unicode databases                         *
****************************************************************
Comment
First fixed in Db2 version 11.5.7.0
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.06.2021
21.11.2021
21.11.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)