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

DB2 MAY CRASH DURING PROCESSING OF THE OPTIMIZER PROFILE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The problem can occur during compilation of a SQL statement in 
the presence of an optimization profile containing at least one 
STMTPROFILE section. 
 
Once this happens the FODC is created with following stack 
(snippet): 
 
... 
sqle_panic 
SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash 
sqlofmblkEx 
sqlno_hint_get_optprofile 
sqlnnProcessProfile 
sqlnp_main 
sqlnn_cmpl 
sqlnn_cmpl 
sqlra_compile_var 
sqlra_find_var 
sqlra_statement_concentrator 
sqlra_get_var 
sqlrr_prepare 
sqljs_ddm_prpsqlstt 
sqljsParseRdbAccessed 
sqljsParse 
sqljsSqlam 
sqljsDriveRequests 
sqljsDrdaAsInnerDriver 
sqljsDrdaAsDriver 
sqeAgent::RunEDU 
sqzEDUObj::EDUDriver 
sqloEDUEntry 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 9                   * 
****************************************************************
Local Fix:
Remove the affected STMTPROFILE section from the optimization 
profile.
Solution
Problem was first fixed in DB2 Version 10.5 and Fix Pack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.02.2017
27.09.2017
27.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)