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

ALTER TABLE MAY FAIL WITH SQL1034C in DPF environment.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
ALTER TABLE may fail with SQL1034C in DPF environment. 
 
SQL1034C  The database is damaged. 
 
 
You will find similar entries in db2diag.log file as shown 
below: 
 
2010-07-09-18.43.19.897506+480 I2102A472  LEVEL: Severe 
PID     : 864406 TID  : 7365 PROC: db2sysc 2 
INSTANCE: bcu02uu1       NODE : 002             DB : BCUU02 
APPHDL  : 0-38845           APPID: *N0.bcu02uu1.100709104312 
AUTHID  : BCU02UU1 
EDUID   : 7365                EDUNAME: db2agntp (BCUU02) 2 
FUNCTION: DB2 UDB, global services, sqlzeMapZrc, probe:45 
MESSAGE : ZRC=0x87120084=-2028863356=SQLR_INV_RPC_REQ "Invalid 
RPC request" 
 
... 
 
2010-07-09-18.43.21.504123+480 E45546A458  LEVEL: Severe 
PID     : 864406   TID  : 7365  PROC  :db2sysc 2 
INSTANCE: bcu02uu1       NODE : 002                DB   : BCUU02 
APPHDL  : 0-38845           APPID: *N0.bcu02uu1.100709104312 
AUTHID  : BCU02UU1 
EDUID   : 7365                EDUNAME: db2agntp (BCUU02) 2 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::MarkDBBad, probe:10 
MESSAGE : ADM7518C  "BCUU02  " marked bad.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users prior to DB2 V97 FP4.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* ALTER TABLE MAY FAIL WITH SQL1034C in DPF environment.       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade DB2 to V97 FP4.                                      * 
****************************************************************
Local Fix:
available fix packs:
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 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem is first fixed in DB2 V97 FP4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.09.2010
09.05.2011
09.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList