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

DB2.NET OR CLI BASED APPLICATION CAN TRAP AND FAIL WITH
SQLODIAGNOSEFREEBLOCKFAILURE ERROR MESSAGE.

product:
DB2 CONNECT / DB2CONNCT / 950 - DB2
Problem description:
A DB2 .NET or CLI application that calls stored procedures on 
DB2 for z/OS can fail with a memory corruption error. 
 
A typical error that might occur in the db2diag.log is as 
follows: 
 
2011-06-06-12.30.00.253000-300 I642216H311        LEVEL: Severe 
PID     : 4332                 TID  : 2263        PROC : 
w3wp.exe 
INSTANCE: DB2                  NODE : 000 
EDUID   : 2263 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:10 
MESSAGE : Possible memory corruption detected. 
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 
0x820F0002 
DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 4 
bytes 
0x1242e960 
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
0x1242E948 : 0100 2CDB 5800 0000 A1A1 9212 3201 3A00 
..,.X.......2.:. 
0x1242E958 : 2024 B1FA 0800 0000                         $...... 
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
0x1242E960 : 0100 0000 0000 0000 0000 0000 D0E9 4212 
..............B. 
0x1242E970 : 60F7 4112 0000 0000 20EF 4212 0000 0000    `.A..... 
.B..... 
0x1242E980 : 0000 0000 00FE 4612 10FE 4612 0000 0000 
......F...F..... 
 
2011-06-06-12.30.16.450000-300 B391025H903        LEVEL: 
Critical 
PID     : 4332                 TID  : 2263        PROC : 
w3wp.exe 
INSTANCE: DB2                  NODE : 000 
EDUID   : 2263 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:10 
MESSAGE : ADM14001C  An unexpected and critical error has 
occurred: "Panic". 
          The instance may have been shutdown as a result. 
"Automatic" FODC 
          (First Occurrence Data Capture) has been invoked and 
diagnostic 
          information has been recorded in directory 
          "C:\DOCUME~1\ALLUSE~1\APPLIC~1\IBM\DB2\DB2COPY1\DB2\". 
Please look in 
          this directory for detailed evidence about what 
happened and contact 
          IBM support if necessary to diagnose the problem. 
 
2011-06-06-12.30.16.659000-300 B322573H215        LEVEL: Severe 
PID     : 4332                 TID  : 2263        PROC : 
w3wp.exe 
INSTANCE: DB2                  NODE : 000 
EDUID   : 2263 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:999 
MESSAGE : Memory validation failure, diagnostic file dumped. 
DATA #1 : String, 21 bytes 
Corrupt block header. 
DATA #2 : File name, 29 bytes 
4332.2263.mem_diagnostics.txt
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI based applications connecting to DB2 for z/OS            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A DB2 .NET or CLI application that calls stored procedures   * 
* on DB2 for z/OS can fail with a memory corruption error.     * 
*                                                              * 
* A typical error that might occur in the db2diag.log is as    * 
* follows:                                                     * 
*                                                              * 
* 2011-06-06-12.30.00.253000-300 I642216H311        LEVEL:     * 
* Severe                                                       * 
* PID    : 4332                TID  : 2263        PROC :       * 
* w3wp.exe                                                     * 
* INSTANCE: DB2                  NODE : 000                    * 
* EDUID  : 2263                                                * 
* FUNCTION: DB2 UDB, SQO Memory Management,                    * 
* sqloDiagnoseFreeBlockFailure, probe:10                       * 
* MESSAGE : Possible memory corruption detected.               * 
* DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes                          * 
* 0x820F0002                                                   * 
* DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 4  * 
* bytes                                                        * 
* 0x1242e960                                                   * 
* DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes         * 
* 0x1242E948 : 0100 2CDB 5800 0000 A1A1 9212 3201 3A00         * 
* ..,.X.......2.:.                                             * 
* 0x1242E958 : 2024 B1FA 0800 0000                             * 
* $......                                                      * 
* DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes       * 
* 0x1242E960 : 0100 0000 0000 0000 0000 0000 D0E9 4212         * 
* ..............B.                                             * 
* 0x1242E970 : 60F7 4112 0000 0000 20EF 4212 0000 0000         * 
* `.A.....                                                     * 
* .B.....                                                      * 
* 0x1242E980 : 0000 0000 00FE 4612 10FE 4612 0000 0000         * 
* ......F...F.....                                             * 
*                                                              * 
* 2011-06-06-12.30.16.450000-300 B391025H903        LEVEL:     * 
* Critical                                                     * 
* PID    : 4332                TID  : 2263        PROC :       * 
* w3wp.exe                                                     * 
* INSTANCE: DB2                  NODE : 000                    * 
* EDUID  : 2263                                                * 
* FUNCTION: DB2 UDB, SQO Memory Management,                    * 
* sqloDiagnoseFreeBlockFailure, probe:10                       * 
* MESSAGE : ADM14001C  An unexpected and critical error has    * 
* occurred: "Panic".                                           * 
*           The instance may have been shutdown as a result.   * 
* "Automatic" FODC                                             * 
*           (First Occurrence Data Capture) has been invoked   * 
* and                                                          * 
* diagnostic                                                   * 
*           information has been recorded in directory         * 
*                                                              * 
* "C:\DOCUME~1\ALLUSE~1\APPLIC~1\IBM\DB2\DB2COPY1\DB2\".       * 
* Please look in                                               * 
*           this directory for detailed evidence about what    * 
* happened and contact                                         * 
*           IBM support if necessary to diagnose the problem.  * 
*                                                              * 
* 2011-06-06-12.30.16.659000-300 B322573H215        LEVEL:     * 
* Severe                                                       * 
* PID    : 4332                TID  : 2263        PROC :       * 
* w3wp.exe                                                     * 
* INSTANCE: DB2                  NODE : 000                    * 
* EDUID  : 2263                                                * 
* FUNCTION: DB2 UDB, SQO Memory Management,                    * 
* sqloDiagnoseFreeBlockFailure, probe:999                      * 
* MESSAGE : Memory validation failure, diagnostic file dumped. * 
* DATA #1 : String, 21 bytes                                   * 
* Corrupt block header.                                        * 
* DATA #2 : File name, 29 bytes                                * 
* 4332.2263.mem_diagnostics.txt                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5, Fixpak 9                         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
4.2.1 Interim Fix 1 (November 2011) for Tivoli Storage Productivity Center

Solution
First fixed in DB2 Version 9.5, Fixpak 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC76860 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.06.2011
22.03.2012
22.03.2012
Problem solved at the following versions (IBM BugInfos)
9.0.,
9.5.
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList