DB2 FOR LUW / DB2FORLUW / 970 - 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 9.7 Fix Pack 6.                       * 
****************************************************************

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

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 9.7 Fix Pack 6.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC84442 
follow-up : 

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

19.01.2012
11.06.2012
11.06.2012

9.7.FP6