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

INSTANCE CRASH BY ACCESS VIOLATION ON A QUERY WITH OVER 15 RANGE PREDICATES
AND EXPRESSION OPERAND OF SOME RANGE PREDICATES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Instance crash through access violation exception or signal 
can be caused by the following query. 
 
  Query which makes this trap : 
    - Query has greater than 15 RANGE PREDICATEs 
    - Some but not all RANGE PREDICATEs have expression operand, 
e.g. user_defined_function(Table1.column1) >= 1 
 
  And its stacktrace in trap file is as follows. 
 
  Stacktrace : 
    addElem 
    sqlnr_estimate_sel_card 
    ...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Instance crash through access violation exception or signal  * 
*  can be caused by the following query.                       * 
*                                                              * 
*                                                              * 
*                                                              * 
* Query which makes this trap :                                * 
*                                                              * 
*   - Query has greater than 15 RANGE PREDICATEs               * 
*                                                              * 
*   - Some but not all RANGE PREDICATEs have expression        * 
* operand,e.g. user_defined_function(Table1.column1) >= 1      * 
*                                                              * 
*                                                              * 
*                                                              * 
* And its stacktrace in trap file is as follows.               * 
*                                                              * 
*                                                              * 
*                                                              * 
* Stacktrace :                                                 * 
*                                                              * 
*   addElem                                                    * 
*                                                              * 
*   sqlnr_estimate_sel_card                                    * 
*                                                              * 
*   ...                                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 v9.7fp1                                       * 
****************************************************************
Local Fix:
Not available
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 FixPak 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
19.02.2010
19.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList