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

DB2 REDISTRIBUTE RECOVERY MAY FAIL WITH -902 ERROR

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
It is possible for Redistribute Recovery after a failed 
redistribute to fail with the following error message: 
 
SQL6064N  SQL error "-902" occurred during data redistribution. 
 
During data redistribution, if the user has not specified 
"INDEXING MODE DEFERRED", Redistribute will recreate the indexes 
on all nodes but will not mark them invalid while they are being 
populated. If redistribute were to be interrupted due to a 
hardware error or other problem it is possible the index on disk 
ends up in an inconsistent state. The subsequent REDISTRIBUTE 
CONTINUE  or ABORT command will attempt to read the index on 
disk since they are not marked invalid but will fail since the 
indexes are inconsistent. The db2diag.log will indicate an error 
about a bad index page. 
 
Redistribute should mark the index invalid prior to populating 
it, and mark it valid again once it is finished. That way in 
case of failure REDISTRIBUTE CONTINUE will not attempt to read 
the index information.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of the REDISTRIBUTE utility                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.5 FP10 or newer to obtain the permanent    * 
* fix.                                                         * 
****************************************************************
Local Fix:
Use DB2DART to manually mark the index invalid and re-issue the 
REDISTRIBUTE CONTINUE or REDISTRIBUTE ABORT command.
Solution
Upgrade to DB2 v9.5 FP10 or newer to obtain the permanent fix.
Workaround
Use DB2DART to manually mark the index invalid and re-issue the 
REDISTRIBUTE CONTINUE or REDISTRIBUTE ABORT command.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC76346 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.05.2011
10.12.2012
10.12.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList