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

SPACE IN COLUMN NAME CREATES INRECOGNIZABLE DB2LOOK STATEMENT FOR THE
COLUMN -WHILE RUNNING DB2LOOK OUTPUT.

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
While creating  columns of a table - with creating space in the 
column  name it creates wrong db2look output. 
 
If they create a column with the following options. 
 
Example below : 
 
db2 create table test (\"CO  L1 \" varchar(15), \"COL2\"  - 
integer,\"COL3\" integer)  -- 
 
(here  space in between COL1 name) 
 
if after customer do runstats of the table -it create sample 
runstats in db2look output. 
 
 
But while doing runstats with the statement created in db2look- 
it fails to recognize the column.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.8 FP3 or Subsequent Fix Pack                * 
****************************************************************
Local Fix:
Use  double quotes  between the column name.
available fix packs:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Problem First Fixed in DB2 Version 9.8 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.02.2010
10.12.2012
10.12.2012
Problem solved at the following versions (IBM BugInfos)
9.8.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.3 FixList