Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC64387 Status: Geschlossen

Upgrading a v8.X database may fail with -902 while upgrading SYSCOLUMNS

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This is caused by issue handled in APAR LI70020. A           * 
* RENAMETABLE leaves an orphan row in SYSCOLPROPERTIES         * 
* behind.While upgrading table SYSCOLPROPERTIES in v8 to v9.1, * 
* theorphan 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 isneeded.Additional checks    * 
* are added to db2ckmig to capture theorphan rows (introduced  * 
* on a db2level without APAR LI70020)and handle this during    * 
* database upgrade.                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.5 FP6                               * 
****************************************************************
Local-Fix:
There is no workaround for this issue. Please contact IBM DB2 
Support to verifiy that you are hitting this APAR.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 version 9.5 FP6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC64393 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.11.2009
10.06.2010
10.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version