DB2 FOR LUW / DB2FORLUW / 910 - DB2

DB2 environments using the Database partitioning feature (DPF) 
may experience an instance crash ,marking database bad while 
upgrading databases. 
The following db2diag.log entries may be found to help identify 
this APAR 
 
 
2009-08-28-10.30.11.459507-300 I385332A472        LEVEL: Severe 
PID     : 3027148              TID  : 9039        PROC : db2sysc 
10 
INSTANCE: <instancename>              NODE : 010         DB   : 
<dbname> 
APPHDL  : 0-13652              APPID: <appid> 
AUTHID  : <authid> 
EDUID   : <eduid>                 EDUNAME: <eduname> 
FUNCTION: DB2 UDB, global services, sqlzeMapZrc, probe:45 
MESSAGE : ZRC=0x87020076=-2029911946=SQLB_INV_POOLID "Invalid 
pool ID" 
 
 
 
2009-08-28-10.30.11.643083-300 I473314A558        LEVEL: Warning 
PID     : 2871430              TID  : 17267       PROC : db2sysc 
INSTANCE: <instancename>           NODE : 000         DB   : 
<dbname> 
EDUID   : <eduid>                EDUNAME: <eduname> 
FUNCTION: DB2 UDB, base sys utilities, 
db2spcat_fixViewColumnNulls, probe:2601 
MESSAGE : ZRC=0xFFFFFBEE=-1042 
DATA #1 : String, 23 bytes 
Failed to recreate view 
DATA #2 : Schema Name, <schema name>, 8 bytes 
SIZEBUY 
DATA #3 : Object Name, <object name>, 24 bytes 
 
 
2009-08-28-10.30.11.643417-300 I473873A421        LEVEL: Error 
PID     : 2871430              TID  : 17267       PROC : db2sysc 
INSTANCE: <instance name>            NODE : 000         DB   : 
<dbname> 
EDUID   : <eduid>                EDUNAME: <eduname> 
FUNCTION: DB2 UDB, base sys utilities, 
db2spcat_fixViewColumnNulls, probe:2613 
MESSAGE : ZRC=0xFFFFFE0B=-501 
DATA #1 : String, 28 bytes 
Error fetching <viewname> 
 
2009-08-28-10.30.11.643785-300 I474295A437        LEVEL: Severe 
PID     : 798916               TID  : 1           PROC : db2bp 
INSTANCE:  <instance name>             NODE : 000 
APPID   : <appid> 
EDUID   : <eduid> 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
MESSAGE : SQLESCDB: sqlcode 
DATA #1 : Hexdump, 14 bytes 
0x0FFFFFFFFFFF70F8 : 7371 6C63 6F64 6520 3D20 2D35 3031 
sqlcode = -501 
 
 
2009-08-28-10.30.11.644148-300 I475813A330        LEVEL: Warning 
PID     : 798916               TID  : 1           PROC : db2bp 
INSTANCE: <instance name>             NODE : 000 
APPID   : <appid> 
EDUID   : 1 
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:40 
MESSAGE : End db2spcat: with rc = -501, sqlcode = -501

**************************************************************** 
* USERS AFFECTED:                                              * 
* Only DB2 Version 8 with DPF environments upgrading to DB2    * 
* Version 9.1 via redirected restore may be affected.          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Upgrade  in Database partitioning feature(DPF) environment   * 
* fails                                                        * 
* due to  view regeneration that triggers the need to go off   * 
* node                                                         * 
* to collect data.                                             * 
*                                                              * 
* This is  because the tables the view is defined on ,belongs  * 
* to                                                           * 
* a database partition group that does not include the catalog * 
*                                                              * 
* node.                                                        * 
*                                                              * 
* Since view regeneration is one of the necessary step in the  * 
*                                                              * 
* process of upgrading databases where some views may need to  * 
* be                                                           * 
* regenerated upgrade  fails.                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See the workaround provided in the "Local fix" or upgrade to * 
* a later release directly from DB2 Version 8.                 * 
****************************************************************

To workaround,  restore the full DPF database in the downlevel 
release, then perform an "inplace" upgrade (ie. don't do the 
upgrade through redirected restore).

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

01.12.2010
02.12.2010
02.12.2010