home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC66309 Status: Closed

DB2LOOK FAILS TO INSERT A COMMA INCASE THERE IS NO CONSECUTIVE ELEMENT
CREATED FOR COMPONENTS LISTED.

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
db2look fails to insert a comma incase there is no consecutive 
element created for COMPONENTS listed. 
 
EX: 
 
 
CREATE SECURITY LABEL COMPONENT "COMPONENT_01" 
   SET {'001', '002', '003'}; 
 
 
CREATE SECURITY LABEL COMPONENT "COMPONENT_02" 
   SET {'004', '005', '006'}; 
 
CREATE SECURITY LABEL COMPONENT "COMPONENT_03" 
   SET {'007', '008', '009'}; 
 
 
If you specify the elements for components COMPONENT_01 and 
COMPONENT_03 as follows: 
 
CREATE SECURITY LABEL "SEC_LABEL"."LABEL_NAME" 
   COMPONENT "COMPONENT_01" '001', 
   COMPONENT "COMPONENT_03" '008'; 
 
 
then db2look will fail to insert a comma for components listed 
causing error SQL0104N be printed in db2look output and 
bad syntax like as following: 
 
 
CREATE SECURITY LABEL "SEC_LABEL"."LABEL_NAME" 
   COMPONENT "COMPONENT_01" '001' 
 
   COMPONENT "COMPONENT_03" '008'; 
 
 
However, if you specify all consecutive component elements, 
db2look will generate the correct DDL: 
 
CREATE SECURITY LABEL "SEC_LABEL"."LABEL_NAME" 
   COMPONENT "COMPONENT_01" '001', 
   COMPONENY "COMPONENT_02" '004', 
   COMPONENT "COMPONENT_03" '008';
Problem Summary:
DB2LOOK FAILS TO INSERT A COMMA INCASE THERE IS NO CONSECUTIVE 
ELEMENT CREATED FOR COMPONENTS LISTED.
Local Fix:
No local Fix
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
Fixed in DB2 V98 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.02.2010
23.12.2010
23.12.2010
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