|
Problem IT02319
|
Status: Closed |
DB2CKUPGRADE MIGHT REPORT: "SQL1344N ORPHAN ROWS FOUND" IF THERE ARE INVALID OBJECTS IN THE DATABASE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Starting from DB2 version 10.1 Fix Pack 4, 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.1"
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.1 and Fix Pack 5 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 |
| Solution |
Problem was first fixed in DB2 version 10.1 and Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.06.2014
27.07.2015
27.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
