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

DB2CHKUPGRADE MAY RETURN FALSE POSITIVE ORPHAN ROW ERRORS WITH SYSTABLES
AND SYSTABLESPACES WHEN USERS HAVE NICKNAMES DEFINED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
During upgrade from DB2 V8.2 to DB2 v9.7.GA, db2ckupgrade is 
failing.  The following error may be returned: 
 
Version of DB2CKUPGRADE being run: VERSION 9.7.0.0 
Database: 'SAMPLE' 
 ** ERROR ** 
SQL1344N Orphan rows found in the system catalogs.  Contact 
your technical service representative prior to attempting a 
upgrade. 
                                   . 
The db2ckupgrade utility may be reporting false positives if the 
database has nicknames defined with schema beginning with "SYS". 
 
 
These orphan rows won't have any impact during the actual 
database upgrade, however, db2ckupgrade returns an 
error when orphan rows are detected and can cause the instance 
upgrade to fail.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Customers upgrading from V8.2 to DB2 9.7 GA                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2chkupgrade may return false positive orphan row errors    * 
* with SYSTABLES and SYSTABLESPACES when users have nicknames  * 
* defined with schema beginning with "SYS"                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 V9.7 FP1 or higher                             * 
****************************************************************
Local Fix:
Drop the reported nicknames, proceed with upgrade and recreate 
the dropped nicknames.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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

Solution
Problem Fixed in DB2 Version 9.7 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.09.2009
17.02.2012
17.02.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList