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

THE COLUMN_ID COLUMN OF THE ORACLE DATA DICTIONARY-COMPATIBLE VIEW
SYSIBMADM.DBA_TAB_COLUMNS DOES NOT START FROM 1

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The Oracle data dictionary-compatible view 
SYSIBMADM.DBA_TAB_COLUMNS has a column named COLUMN_ID, which 
should start count from 1, but it currently start from 0. 
 
 
Example: 
 
$ db2 "CREATE TABLE CT (C1 INT, C2 INT)" 
DB20000I  The SQL command completed successfully. 
$ db2 "SELECT COLUMN_NAME, COLUMN_ID  FROM 
SYSIBMADM.DBA_TAB_COLUMNS WHERE 
TABLE_NAME = 'CT'" 
 
COLUMN_NAME    COLUMN_ID 
 
--------------  --------- 
 
C1            0 
 
C2          1 
 
 
  2 record(s) selected. 
 
The expected should be: 
 
$ db2 "SELECT COLUMN_NAME, COLUMN_ID  FROM 
SYSIBMADM.DBA_TAB_COLUMNS WHERE 
TABLE_NAME = 'CT'" 
 
COLUMN_NAME    COLUMN_ID 
 
--------------  --------- 
 
C1            1 
 
C2          2 
 
  2 record(s) selected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users  using Oracle compatibility mode                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The Oracle data dictionary-compatible view                   * 
* SYSIBMADM.DBA_TAB_COLUMNS has a column named COLUMN_ID,      * 
* which should start count from 1, but it currently start from * 
* 0.  The  APAR fix will make the starting count from 1.       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* To avoid experiencing this issue users can upgrade to DB2    * 
* Version V9.7 fix pack 5 at the minimum.                      * 
****************************************************************
Local Fix:
Manually add 1 to the column value when querying COLUMN_ID from 
the view
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 Version V9.7 fix pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.04.2011
28.12.2011
28.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList