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

DB2CKUPGRADE MIGHT REPORT: "SQL1344N ORPHAN ROWS FOUND" IF THERE
ARE INVALID OBJECTS IN THE DATABASE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
db2ckupgrade utility might report false positive error related 
to orphan rows found in system catalog: 
DBT5529N  The db2ckupgrade utility did not complete 
successfully. The database cannot be upgraded. The output log 
file is named "upgrade.log". 
 
following error will be logged to upgrade.log file: 
Version of DB2CKUPGRADE being run: VERSION "10.5" 
Database: "<DB_NAME>" 
SQL1344N  Orphan rows found in the system catalogs. Contact your 
technical service representative prior to attempting a database 
upgrade. 
 
that will prevent database from being upgraded. This might 
happen if there are invalid objects in the database and object 
on which they depend, do not exist (which could have been the 
reason for invalidation). In order to verify that, you can use 
SYSCAT.INVALIDOBJECTS view: 
$ db2 "SELECT SUBSTR(OBJECTNAME,1,20) OBJECTNAME, 
SUBSTR(ROUTINENAME, 1,20) ROUTINENAME, OBJECTTYPE FROM 
SYSCAT.INVALIDOBJECTS" 
 
and see if such objects are found in the database.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 and Fix Pack 4 or higher.        * 
****************************************************************
Local Fix:
If invalid object exist in the database, fix the problem by 
either dropping them or fixing dependencies and re-validating 
using SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 version 10.5 and Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.04.2014
08.09.2014
08.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList