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

DB2 SERVER TERMINATES ABNORMALLY WHEN SPATIAL FUNCTION USED IN PREDICATE

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Compiling a SQL query may cause the DB2 server to terminate 
abnormally when a spatial function is used in a predicate.  The 
stack looks similar to the following: 
 
sqlnq_iext_modify_filter_ptree 
sqlnq_iext_create_filter_ptree 
sqlnq_iext_create_filter_prd 
sqlnr_iext_create_twin_udp 
sqlnr_iext_prep 
sqlnr_optprep 
sqlnr_optprep_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc 
sqlnr_exe
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Compiling a SQL query may cause the DB2 server to terminate  * 
* abnormally when a spatial function is used in a predicate.   * 
* The stack looks similar to the following:                    * 
*                                                              * 
* 0x00002B13DD538BB9                                           * 
* _Z30sqlnq_iext_create_filter_ptreeP9sqlnq_pidP3locRS0_ +     * 
* 0x012f                                                       * 
* 0x00002B13DD538CBD                                           * 
* _Z28sqlnq_iext_create_filter_prdP9sqlnq_oprP9sqlnq_pidP3locR * 
* P9sqlnq_prd + 0x0095                                         * 
* 0x00002B13DD8F11EE                                           * 
* _Z26sqlnr_iext_create_twin_udpP9sqlnq_prdP9sqlnq_pidP3lociii * 
* + 0x076a                                                     * 
* 0x00002B13DD8EF8A5 _Z15sqlnr_iext_prepP9sqlnq_oprP3loc +     * 
* 0x03b1                                                       * 
* 0x00002B13DD9C9021 _Z13sqlnr_optprepP9sqlnq_qur + 0x8c1f     * 
* 0x00002B13DD8E0BBC                                           * 
* _Z20sqlnr_optprep_actionP10sqlnr_qrwaPiP14sqlnr_progress +   * 
* 0x002a                                                       * 
* 0x00002B13DDB346BD                                           * 
* _Z10sqlnr_compPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_pr * 
* ogress + 0x045d                                              * 
* 0x00002B13DDB34ED9                                           * 
* _Z9sqlnr_seqPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass  * 
* + 0x0129                                                     * 
* 0x00002B13DDB351CA                                           * 
* _Z9sqlnr_rcciP10sqlnr_qrwaPiP14sqlnr_progress + 0x00f2       * 
* 0x00002B13DD8E2CA2 _Z9sqlnr_exeP9sqlnq_qur + 0x1bbc          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.5 Fix Pack 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

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