DB2 - Problembeschreibung
Problem IC76054 | Status: Geschlossen |
THE COLUMN_ID COLUMN OF THE ORACLE DATA DICTIONARY-COMPATIBLE VIEW SYSIBMADM.DBA_TAB_COLUMNS DOES NOT START FROM 1 | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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 | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
First Fixed in DB2 Version V9.7 fix pack 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 28.04.2011 28.12.2011 28.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |