DB2 FOR LUW / DB2FORLUW / A10 - DB2

In a pureScale environment, if the database crashed while 
executing a heuristic abort request from LIST INDOUBT 
TRANSACTION WITH PROMPTING command, the subsequent crash 
recovery might not have performed all the compensation 
action needed to back out the changes made by this 
transaction.  Further more, the heurstically aborted 
transaction is no longer tracked and reported by subsequent 
LIST INDOUBT TRANSACTION command. 
 
Depending on the crash point, if the transaction was in the 
midst of being compensated then the ensuing recovery would not 
complete the compensation nor abort the transaction.  This can 
leave the data inconsistent, where any future access can result 
in undefined behavior.  One possibility could be getting: 
 
SQL1034C  The database was damaged, so all applications 
processing the database were stopped. 
 
and marking the database damaged and/or creating a FODC_BadPage 
directory in the 
db2dump directory.

**************************************************************** 
* USERS AFFECTED:                                              * 
* pureScale                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In a pureScale environment, if the database crashed while    * 
* executing a heuristic abort request from LIST INDOUBT        * 
* TRANSACTION WITH PROMPTING command, the subsequent crash     * 
* recovery might not have performed all the compensation       * 
* action needed to back out the changes made by this           * 
* transaction.  Further more, the heurstically aborted         * 
* transaction is no longer tracked and reported by subsequent  * 
* LIST INDOUBT TRANSACTION command.                            * 
*                                                              * 
* Depending on the crash point, if the transaction was in the  * 
* midst of being compensated then the ensuing recovery would   * 
* not                                                          * 
* complete the compensation nor abort the transaction.  This   * 
* can                                                          * 
* leave the data inconsistent, where any future access can     * 
* result                                                       * 
* in undefined behavior.  One possibility could be getting:    * 
*                                                              * 
* SQL1034C  The database was damaged, so all applications      * 
* processing the database were stopped.                        * 
*                                                              * 
* and marking the database damaged and/or creating a           * 
* FODC_BadPage                                                 * 
* directory in the db2dump directory.                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 for LUW version 10.1.4.                       * 
****************************************************************

Problem was first fixed in Version 10.1 Fix Pack 4.  At a 
minimum, this fix should be applied on the server.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC98726 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

14.01.2014
13.07.2015
13.07.2015