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

DB2 CRASH ON INVALID OBJECT

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
DB2 can crash with the following stack 
 
      sqlnq_qtb::box_drop 
      sqlnn_regen_view 
      sqlrl_regen_view 
      sqlnq_check_referenced_qtb 
      sqlnq_handle_from_table_ref 
      sqlnq_sem 
      sqlnp_smactn 
      sqlnp_parser 
      sqlnp_main 
      sqlnq_handle_new_view 
      sqlnq_check_referenced_qtb 
      sqlnq_handle_from_table_ref 
      sqlnn_regen_view 
      sqlrl_regen_view 
      sqlnq_check_referenced_qtb 
     sqlnq_handle_from_table_ref 
     sqlnq_sem 
 
The db2diag log will show something like: 
 
2015-10-22-10.18.44.330786-300 I24482E643          LEVEL: Severe 
PID     : 24036                TID  : 140309237327616PROC : 
db2sysc 0 
INSTANCE: db2inst2             NODE : 000          DB   : FOO 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst2.151022151454 
AUTHID  : DB2INST2 
EDUID   : 23                   EDUNAME: db2agent (FOO) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
MESSAGE : RDS UCINTFC: pStatementText = 
DATA #1 : Hexdump, 19 bytes 
0x00007F9C2F9771A0 : 7365 6C65 6374 202A 2066 726F 6D20 6368 
select * from ch 
0x00007F9C2F9771B0 : 6169 6E 
ain
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 11.1.0.1                              * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in DB2 version 11.1.0.1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.09.2016
20.12.2016
20.12.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
11.1.1.1 FixList