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

A TEXT SEARCH STRING THAT HAS DASH AND A WILDCARD CHARACTER
'"T-S*"' FAILS WITH IQQS0032E ERROR MESSAGE ON V10.5

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
1.  Problem description 
Here are the commands that recreate the error in V10.5 , it 
works on V9.5 , V9.7 , V10.1. 
 
db2 create database gtest 
db2 connect to DATABASE_NAME 
 
db2ts "enable database for text connect to gtest " 
 
db2ts "create index gtest.mytabix for text on gtest.mytab(data) 
connect to gtest user USERID using xxxxxxx" 
 
db2ts "update index gtest.mytabix for text connect to gtest user 
USERID using xxxxxxxx" 
 
db2 "select * from gtest.mytab where contains(data,'\"t-s*\"') = 
1"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V105 fp5 to get fix.                              * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Fix provided in V105fp5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.10.2013
16.09.2014
16.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList