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

DB2CKUPGRADE MAY RETURN ORPHAN ROW WARNING MESSAGE WHEN UPGRADIN G A V8.*
DATABASE CONTAINING PSM NATIVE PROCEDURES TO V9.7

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Check database for upgrade command (db2ckupgrade) may return 
orphan row warning message when upgrading a v8.* database 
containing PSM native procedures to v9.7. 
 
The following query can help identify the procedure(s) that may 
be affected: 
 
select r.routineschema, r.specificname from 
sysibm.syscodeproperties cp, sysibm.sysroutines r where 
cp.lib_id = r.lib_id and r.implementation = 'db2pvm!pvm_entry' 
and cp.object_id = 0;
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* n/a                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Check database for upgrade command (db2ckupgrade) may        * 
* returnorphan row warning message when upgrading a v8.*       * 
* databasecontaining PSM native procedures to v9.7.The         * 
* following query can help identify the procedure(s) thatmaybe * 
* affected:select r.routineschema, r.specificname              * 
* fromsysibm.syscodeproperties cp, sysibm.sysroutines r        * 
* wherecp.lib_id = r.lib_id and r.implementation               * 
* ='db2pvm!pvm_entry'and cp.object_id = 0;                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fixpack 1                         * 
****************************************************************
Local Fix:
As a workaround, customer should do the following: 
 
- Request help from IBM support 
- Collect the outputs for db2cleancat <dbname> 0 
- Collect the output of the query "select object_type, 
object_id, cp.lib_id, libversion from sysibm.syscodeproperties 
cp, sysibm.sysroutines r where cp.lib_id = r.lib_id"
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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
First fixed in DB2 Version 9.7 Fixpack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.09.2009
24.02.2010
24.02.2010
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