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

IMPLEMENTING DB2TOP WITH OPTION -NO_MAP_CHAR WHICH WAS INTRODUCED TO
DB2EXFMT

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When using db2exfmt for explain plan with languages other than 
English, the 
statement was not formatted correctly. 
There are gaps inserted into the plan because of unprintable 
characters used . 
 
Option to format the plan correctly was to use "-no_map_char" 
with db2exfmt. 
 
When we run db2top in the following steps: 
 
db2top -d <databasename> 
* Use l option to list the application 
* Choose an agent of SQL application using option 'a' 
* Use option 'x' to generate explain plan 
 
db2top ends up calling db2exfmt for an explain plan. However we 
 
can not enter the option of "-no_map_char", 
Therefore the output is not formatted correctly.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 Fixpack 9                             * 
****************************************************************
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
First fixed in Version 9.5 Fixpack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.08.2011
13.03.2012
13.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