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

FUZZY SEARCH USING SOME ENVIRONMENT SPECIFIC KEYWORD MAY RESULT IN CTE0103

product:
DB2 NET SEARCH / 5765F3800 / 970 - DB2
Problem description:
The following fuzzy search query using some specific keyword for 
fuzzy option may have an internal error CTE0103. The keyword 
depends on the environment. 
 
(Fuzzy Search Example) 
SELECT COUNT(*) FROM TABLE1 WHERE CONTAINS(COMMENT,'FUZZY FORM 
OF 90 \"indin\" ')=1 
 
SQL0443N  Routine "*ARCH_8K64" (specific name "") has returned 
an error 
SQLSTATE with diagnostic text "CTE0103 An internal error 
occurred. 
Location: 
"361", "10". SQLSTATE=38703 
 
db2diag.log may generate the following message from NSE and GTR. 
 
2011-12-05-14.15.10.039901+540 I193655A440        LEVEL: Error 
PID     : 811136               TID  : 36462       PROC : db2sysc 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
EDUID   : 36462                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary 
logging fu, probe:0 
MESSAGE : Message 
DATA #1 : String, 58 bytes 
CTE0103 An internal error occurred. Location: "361", "10". 
 
2011-12-05-14.15.10.040244+540 I194096A451        LEVEL: Error 
PID     : 811136               TID  : 36462       PROC : db2sysc 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
EDUID   : 36462                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
MESSAGE : GTR data 
DATA #1 : Hexdump, 4 bytes 
0x0000000118875AD0 : 0000 0005 
.... 
 
2011-12-05-14.15.10.040554+540 I194548A451        LEVEL: Error 
PID     : 811136               TID  : 36462       PROC : db2sysc 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
EDUID   : 36462                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
MESSAGE : GTR data 
DATA #1 : Hexdump, 4 bytes 
0x0000000118875AD4 : 0000 0D1A 
....
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using fuzzy search in NSE                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to NSE V9.7 FP7 or later                             * 
****************************************************************
Local Fix:
Recreate the index.
available fix packs:
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The fix is first included in V9.7 FP7
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC86240 IC86241 IC86242 IC86544 IC87109 IC87170 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.07.2012
25.10.2012
25.10.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList