DB2 FOR LUW / DB2FORLUW / A10 - DB2

Db2look may trap during execution with following messages in 
db2diag.log file: 
 
2011-11-11-15.22.39.313461+060 E1761544A1215      LEVEL: Severe 
PID     : 1609942              TID  : 1           PROC : db2look 
INSTANCE: db2inst1             NODE : 000 
APPID   : *LOCAL.db2inst1.111111142230 
EDUID   : 1 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:999 
MESSAGE : Memory validation failure, diagnostic file dumped. 
DATA #1 : String, 28 bytes 
Corrupt pool free tree node. 
DATA #2 : File name, 29 bytes 
1609942.1.mem_diagnostics.txt 
 
2011-11-11-15.22.39.323359+060 E1767536A1209      LEVEL: Severe 
PID     : 1609942              TID  : 1           PROC : db2look 
INSTANCE: db2inst1             NODE : 000 
APPID   : *LOCAL.db2inst1.111111142230 
EDUID   : 1 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:999 
MESSAGE : Memory validation failure, diagnostic file dumped. 
DATA #1 : String, 28 bytes 
Corrupt pool free tree node. 
DATA #2 : File name, 29 bytes 
1609942.1.mem_diagnostics.txt 
 
 
Possible stacks: 
 
sqlofmblkEx 
sqlddFreeDD 
sqlddFreeDD 
csmFreeCCB 
csmClose 
csmClose 
 
sqlofmblkEx 
csmBlastCDB 
csmBlastCDB 
csmFreeCCB 
csmClose 
 
Following conditions need to be meet: 
 
- DB2BIDI is set (db2set DB2BIDI=YES) 
- Database codepage differs from client codepage 
e.g. 
db2 create database test using codeset utf-8 territory DE 
export LANG=en_US 
- db2look has to generate a generate a DDL statement larger than 
32k 
e.g. 
DDL for a large SQL procedure

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************

To workaround this issue unset DB2BIDI or use same codepage on 
client and server.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 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
 

First fixed in DB2 Version 10.1 Fix Pack 1

keiner bekannt / siehe Local-Fix

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

14.06.2012
05.11.2012
05.11.2012