|
Problem IC63160
|
Status: Closed |
SPACE IN COLUMN NAME CREATES INRECOGNIZABLE DB2LOOK STATEMENT FOR THE COLUMN -WHILE RUNNING DB2LOOK OUTPUT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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: |
While creating columns of a table and creating space in the
column name -
If they create a column with the following options.
db2 create table t_udf (\"CO L1 \" varchar(15), \"COL2\" -
here space in between COL1 name
integer,\"COL3\" integer) -- (i.e space included in COL1 )-
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. |
| Local Fix: |
Use double quotes between the column name. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
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 |
|
| Workaround |
Use double quotes between the column name |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66502 IC66503
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.09.2009
18.05.2010
18.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
