|
Problem IC74899
|
Status: Closed |
COLSEQ COLUMN OF SYSCAT.KEYCOLUSE NOT SHOWING CORRECT COLUMN SEQUENCE FOR THE FOREIGN KEY |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
Example:
"SELECT substr(K.TABNAME,1,9) tabname, substr(K.COLNAME,1,20)
colname, substr(K.CONSTNAME,1,10) constname, K.COLSEQ FROM
SYSCAT.KEYCOLUSE K WHERE K.TABSCHEMA = 'XXX' AND K.TABNAME IN
('YYY','ZZZ') "
This returns the correct COLSEQ for primary key as defined, but
the COLSEQ column for foreign key does not match the primary
key. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 users using Referential Integrity tables *
****************************************************************
* PROBLEM DESCRIPTION: *
* "SELECT substr(K.TABNAME,1,9) tabname, *
* substr(K.COLNAME,1,20) *
* colname, substr(K.CONSTNAME,1,10) constname, K.COLSEQ FROM *
* *
* SYSCAT.KEYCOLUSE K WHERE K.TABSCHEMA = 'XXX' AND K.TABNAME *
* IN *
* ('YYY','ZZZ') " RETURNS THE CORRECT COLSEQ FOR PRIMARY KEY *
* AS *
* DEFINED BUT THE COLSEQ COLUMN FOR FOREIGN KEY DOES NOT *
* *
* MATCH THE PRIMARY KEY. *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to the Fix Pack containing the fix *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
Please upgrade to Fix Pack 11 or higher containing the fix |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.03.2011
13.12.2011
13.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.11
|
 |
