DB2 FOR LUW / DB2FORLUW / A10 - DB2

During rollforward of an online index reorganization operation, 
if an error is encountered (such as an out of memory error or a 
disk error), then the error handling code may fail to complete 
successfully.  As a result, the roll forward will fail with 
SQL3785N and the following message may be present in the 
db2diag.log: 
 
2013-05-07-15.41.16.415650-240 I627145E2707          LEVEL: 
Warning 
PID     : 26756                TID : 46913193765184  KTID : 1551 
PROC    : db2sysc 
INSTANCE: leechu               NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-59                 APPID: *LOCAL.leechu.130507194028 
AUTHID  : LEECHU               HOSTNAME: hotel62 
EDUID   : 510                  EDUNAME: db2redom (SAMPLE) 
FUNCTION: DB2 UDB, SQO Memory Management, sqlogmblkEx, 
probe:1000 
MESSAGE : ZRC=0x820F0004=-2112946172=SQLO_MEM_SIZE "Mem Mgt 
invalid size" 
          DIA8563C An invalid memory size was requested. 
DATA #1 : String, 43 bytes 
Memory management block allocation failure. 
DATA #2 : Codepath, 8 bytes 
2 
DATA #3 : Memory pool handle pointer, 
PD_TYPE_MEM_POOL_HANDLE_PTR, 8 bytes 
0x0000000000000000 
DATA #4 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes 
0 
DATA #5 : Adjusted block size, PD_TYPE_MEM_ADJUSTED_SIZE, 8 
bytes 
0 
DATA #6 : Options for requested block, PD_TYPE_GET_MEM_OPTIONS, 
4 bytes 
0x00000200 
DATA #7 : Pointer to address that will be set by new allocation, 
PD_TYPE_PTR_TO_ADDRESS_OUT, 8 bytes 
0x00002aaad43f74d0 
DATA #8 : File name, PD_TYPE_OSS_MEM_FILE_NAME, 10 bytes 
sqluvppo.C 
DATA #9 : Line of code, PD_TYPE_OSS_MEM_LINE_NUM, 8 bytes 
1305 
DATA #10: Resource binding pointer, 
PD_TYPE_RESOURCE_BINDING_PTR, 8 bytes 
0x0000000000000000 
 
In the handling of the original error, DB2 failed to check for a 
boundary condition and handling of the original rollforward 
error is incomplete.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All configurations.                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.2.                             * 
****************************************************************

Examine the db2diag.log to determine the cause of the original 
failure.  If possible, correct the problem and then retry the 
restore and rollforward commands. 
 
Updating to DB2 version 10.1.0.2 will correct the improperly 
handled boundary condition in the error handling, but the 
original error that led to all of this still needs to be 
resolved by the user.

DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

The problem is first fixed in DB2 version 10.1.0.2.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

09.10.2012
08.05.2013
08.05.2013