home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT06667 Status: Geschlossen

DB2CKUPGRADE UTILITY FAILS WITH "SQL1344N ORPHAN ROWS FOUND IN THE
SYSTEM CATALOGS".

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Similar to APAR IT01225, which fixes the issue with procedures 
this APAR addresses views. 
 
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 Fixpack 6 or Later.                 * 
****************************************************************
Local-Fix:
If invalid objects exist in the database, fix the problem by 
either dropping them or fixing dependencies and re-validating 
using SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS.
Lösung
First Fixed in DB2 LUW v10.5 Fixpack 6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.01.2015
01.09.2015
01.09.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.6 FixList
10.5.0.7 FixList