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

INCOMPATIBLE OPERATIONS OF EXTENT MOVEMENT AND REBALANCE RUN AT THE SAME
TIME CAN CAUSE DATA CORRUPTION

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Data corruption occurs when incompatible operations of Extent
Movement and Rebalance are executed at the same time. This is
normally not possible as the ALTER TABLESPACE command while one
of those operations is running will return SQL0290N. Under a
certain timing window it is possible to start both operations at
the same time. This APAR will be to restrict the execution of
these incompatible operations at the same time.

If Extent Movement and Rebalance are executing at the same time
the tablespace will be in the following state (using db2pd
-tablespace):

0x10080000
State = Move in Progress
      + DMS Rebalance in Progress
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All Users.                                                   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to v11.1 M4 FP4 or newer.                            *
****************************************************************
Local Fix:
Avoid running Tablespace Extent Movement and Rebalance
operations at the same time.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT29257 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.05.2019
23.02.2020
23.02.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)