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

LIST HISTORY ALL SHOWS MISSING COMMENTS AND TABLESPACE NAMES WHEN DBCS ARE
INVOLVED

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When list history command is executed in CLP either in jp or tw 
locale with 
server in different codepage, the o/p may contain missing 
comments and tablespace names. Also, there could be garbage data 
appended to the o/p when there are DDLs as part of the history 
o/p. 
 
for e.g: 
Client: 
DB2CODEPAGE=954 
DB2COUNTRY=81 
AIXLOCALE=ja_JP 
LC_ALL=ja_JP 
 
Server: 
codepage = 932 
 
 
 
 
Problem #- tablespace name is missing 
 
Expected: 
 
  00001 <tablespace_name> 
 
 --------------------------------------------------------------- 
------------- 
    Comment: CREATE TABLESPACE, ID = 6 
 Start Time: ************** 
   End Time: ************** 
 --------------------------------------------------------------- 
------------- 
  EID: ***** Location: 
 
 
Currnently: 
 
  00001 
---------------------------------------------------------------- 
------------ 
    Comment: CREATE TABLESPACE, ID = 6 
 Start Time: ************** 
   End Time: ************** 
 --------------------------------------------------------------- 
------------- 
  EID: ***** Location: 
 
Problem#-Comments missing 
Instead of: 
              Comment:  <my dbcs comments> 
              Start Time:  ...... 
 
        Current result: (wrong, as its missing the comment 
completely) 
              Comment:   Start Time: ........
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2 clp users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* list history might show corrupted o/p whenever data          * 
* conversion is required between client and server.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v95fp9 or later versions                          * 
****************************************************************
Local Fix:
available fix packs:
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
problem fixed.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.11.2011
08.03.2012
08.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList