Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC81238 Status: Closed

DB2LOOK COMMAND MIGHT LEAD TO A CRASH.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
DB2 instance might crash if you issue db2look command on catalog 
node. 
 
In db2diag.log you would see error messages similar to the 
following: 
==================================== 
2012-01-01-01.01.01.123456+480 I12345678901234    LEVEL: Severe 
PID     : 1234567              TID  : 12345       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-12345              APPID: 
10.251.4.70.37060.120131150501 
AUTHID  : DB2INST1 
EDUID   : 12345                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SQO Memory Management, sqlofmblkEx, probe:40 
MESSAGE : Attempted to free NULL pointer. 
CALLSTCK: 
  [0] 0x0900000003B9354C pdLog + 0x88 
  [1] 0x0900000003B93DD8 pdLog@glue33D + 0xA8 
  [2] 0x0900000003A0D31C sqlofmblkEx + 0x3C 
  [3] 0x09000000048F2908 sqlrr_recreate_ddl__FP14db2UCinterface 
+ 0x408 
  [4] 0x09000000037944A8 sqlesrvr__FP14db2UCinterface + 0x400 
  [5] 0x0900000003C4911C sqleMappingFnServer__FP5sqldaP5sqlca + 
0x434 
  [6] 0x0900000003C48AF8 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0x228 
  [7] 0x0900000003C8BFD8 
sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x454 
  [8] 0x0900000003C8C984 
sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x98 
  [9] 0x0900000003B4E0AC 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x78 
==================================== 
 
In trap file you would see the same call stack as you see in 
db2diag.log, i.e.: 
==================================== 
sqlofmblkEx 
sqlrr_recreate_ddl 
...... 
====================================
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.5 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 instance might crash if you issue db2look command on     * 
* catalog node.                                                * 
*                                                              * 
* In db2diag.log you would see error messages similar to the   * 
* following:                                                   * 
* ====================================                         * 
* 2012-01-01-01.01.01.123456+480 I12345678901234    LEVEL:     * 
* Severe                                                       * 
* PID     : 1234567              TID  : 12345       PROC :     * 
* db2sysc 0                                                    * 
* INSTANCE: db2inst1             NODE : 000         DB   :     * 
* SAMPLE                                                       * 
* APPHDL  : 0-12345              APPID:                        * 
* 10.251.4.70.37060.120131150501                               * 
* AUTHID  : DB2INST1                                           * 
* EDUID   : 12345                EDUNAME: db2agent (SAMPLE) 0  * 
* FUNCTION: DB2 UDB, SQO Memory Management, sqlofmblkEx,       * 
* probe:40                                                     * 
* MESSAGE : Attempted to free NULL pointer.                    * 
* CALLSTCK:                                                    * 
*   [0] 0x0900000003B9354C pdLog + 0x88                        * 
*   [1] 0x0900000003B93DD8 pdLog@glue33D + 0xA8                * 
*   [2] 0x0900000003A0D31C sqlofmblkEx + 0x3C                  * 
*   [3] 0x09000000048F2908                                     * 
* sqlrr_recreate_ddl__FP14db2UCinterface + 0x408               * 
*   [4] 0x09000000037944A8 sqlesrvr__FP14db2UCinterface +      * 
* 0x400                                                        * 
*   [5] 0x0900000003C4911C                                     * 
* sqleMappingFnServer__FP5sqldaP5sqlca + 0x434                 * 
*   [6] 0x0900000003C48AF8                                     * 
* sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAge * 
* ntP5sqlca + 0x228                                            * 
*   [7] 0x0900000003C8BFD8                                     * 
* sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x454           * 
*   [8] 0x0900000003C8C984                                     * 
* sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject +    * 
* 0x98                                                         * 
*   [9] 0x0900000003B4E0AC                                     * 
* sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14d * 
* b2UCinterface + 0x78                                         * 
* ====================================                         * 
*                                                              * 
* In trap file you would see the same call stack as you see in * 
* db2diag.log, i.e.:                                           * 
* ====================================                         * 
* sqlofmblkEx                                                  * 
* sqlrr_recreate_ddl                                           * 
* ......                                                       * 
* ====================================                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.5 Fix Pack 10 or higher levels. * 
****************************************************************
Local Fix:
For DPF environment, issuing db2look command on non-catalog node 
can avoid the problem. 
For non-DPF environment, there is no workaround.
Solution
First fixed in DB2 LUW Version 9.5 Fix Pack 10.
Workaround
For DPF environment, issuing db2look command on non-catalog node 
can avoid the problem. 
For non-DPF environment, there is no workaround.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.02.2012
22.08.2012
22.08.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.