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

FAILURE DURING ONLINE TABLE REORGANIZATION MIGHT LEAD TO DATABASE HANG

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Failure during online table reorganization might lead to an 
index page latch being held indefinitely in exclusive mode, 
which in turn might lead to a database hang.  The following 
conditions are required to hit the problem: 
- REORG TABLE is run with the INPLACE ALLOW WRITE ACCESS option 
- REORG TABLE fails during the fill phase 
- Concurrent inserts and/or updates are running against the 
table while the table is being reorganized.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.4.                             * 
****************************************************************
Local Fix:
If the system is hung, execute the db2_kill command and then 
restart the instance using db2start.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

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