DB2 FOR LUW / DB2FORLUW / 970 - DB2

During database migration we start to migrate table SYSCOLUMNS 
as indicated by following db2diag.log messages: 
 
' Begin migrating catalog table: SYSCOLUMNS ' 
 
Then we are failing with following messages in the db2diag.log: 
 
2009-11-05-23.35.08.060006-300 I215201A710        LEVEL: Severe 
PID     : 418106               TID  : 1544        PROC : db2sysc 
INSTANCE: db2inst1               NODE : 000         DB   : 
TYPETAB 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.091106043450 
AUTHID  : db2inst1 
EDUID   : 1544                 EDUNAME: db2agent (TYPETAB ) 
FUNCTION: DB2 UDB, catalog migration, sqlrlmGetTargetTypeName, 
probe:690 
MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
CALLED  : DB2 UDB, catalog migration, sqlrlmLogErr 
RETCODE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
DATA #1 : String with size, 26 bytes 
 Migration DMS rc=80040001 
 
2009-11-05-23.35.08.061571-300 I215912A721        LEVEL: Severe 
PID     : 418106               TID  : 1544        PROC : db2sysc 
INSTANCE: db2inst1               NODE : 000         DB   : 
TYPETAB 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.091106043450 
AUTHID  : db2inst1 
EDUID   : 1544                 EDUNAME: db2agent (TYPETAB ) 
FUNCTION: DB2 UDB, catalog migration, sqlrlm_9to95_syscolumns, 
probe:2372 
MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
CALLED  : DB2 UDB, catalog migration, sqlrlmLogErr 
RETCODE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
DATA #1 : String with size, 36 bytes 
SYSCOLUMNS Migration DMS rc=801a006d

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This is caused by issue handled in APAR LI70020. A RENAME    * 
* TABLE leaves an orphan row in SYSCOLPROPERTIES behind. While * 
* upgrading table SYSCOLPROPERTIES in v8 to v9.1, the orphan   * 
* row is cleaned up incorrectly. This causes failure of        * 
* upgrade of table SYSCOLUMNS in v9.1to v9.5, as a lookup of   * 
* the row in SYSCOLPROPERTIES is needed. Additional checks are * 
* added to db2ckupgrade to capture theorphan rows (introduced  * 
* on a db2level without APAR LI70020) and handle this during   * 
* database upgrade.                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 FP2                               * 
****************************************************************

There is no workaround for this issue. Please contact IBM DB2 
Support to verifiy that you are hitting this APAR.

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 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 9a 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 10 for Linux, UNIX, and Windows
 

First fixed in DB2 version 9.7 FP2

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

06.11.2009
31.05.2010
31.05.2010

9.7.FP2