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

DB2 MIGHT TRAP WHILE COMPILING SQL QUERY WITH CONTAINS() FUNCTION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
While compiling SQL query with Net Search Extender ( NSE ) 
function called 'contains()', the DB2 database manager instance 
might trap ( return code SQL1224N ) with the following stack 
trace: 
 
<StackTrace> 
 
CteTextCost 
 
CteTextCost 
 
sqlno_post_pass 
... 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DN2 Net Search Extender                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Please see the Error Description section.                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 1.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The problem was fixed in DB2 version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
06.11.2012
15.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList