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

INSTANCE CRASH DURING CRASH RECOVERY IF INFLIGHT ONLINE REORG WORKLOAD AND
TABLE SPACE IS INACCESSIBLE.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
At the time of a database crash, if there is an online reorg in 
progress and before the ensuing database crash recovery the 
table space in which the reorg is taking place in becomes 
inaccessible, the crash recovery may crash the DB2 instance 
attempting to compensate the online reorg transaction with the 
follow stack: 
 
sqldOLRTerminate 
<unknown> 
sqldomUndo 
sqldmund 
sqlptudo 
sqlprudm 
sqlprbck 
sqlprDbBackwardPhase 
sqlprecm 
sqlpresr
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* At the time of a database crash, if there is an online reorg * 
* in progress and before the ensuing database crash recovery   * 
* the table space in which the reorg is taking place in        * 
* becomes inaccessible, the crash recovery may crash the DB2   * 
* instance attempting to compensate the online reorg           * 
* transaction with the follow stack:                           * 
*                                                              * 
* sqldOLRTerminate                                             * 
* <unknown>                                                    * 
* sqldomUndo                                                   * 
* sqldmund                                                     * 
* sqlptudo                                                     * 
* sqlprudm                                                     * 
* sqlprbck                                                     * 
* sqlprDbBackwardPhase                                         * 
* sqlprecm                                                     * 
* sqlpresr                                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* To resolve the problem, either try the work around of fixing * 
* the table space issue before the database crash recovery or  * 
* upgrade to Version 10.5 Fix Pack 3.                          * 
****************************************************************
Local Fix:
A work around would be to solve the table space issue first 
before doing database crash recovery.
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 10.5 Fix Pack 3.  At a 
minimum, this fix should be applied on the server.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC97849 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.09.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList