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

TEXT SEARCH QUERY RETURNS SQL20425N WHEN ORACLE COMPATIBILITY MODE IS
ENABLED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Text search query returns SQL20425N when Oracle compatibility 
mode is enabled and query is run by user with login less than 8 
 
character even though the text index exists. 
 
 
This problem can be reproduced through following steps 
 
db2set DB2_COMPATIBILITY_VECTOR=ORA 
 
db2stop 
 
db2start 
 
 
 
db2ts "stop for text" 
 
db2 "create database tstest using codeset utf-8 territory kr" 
 
db2ts "start for text" 
 
 
 
set DB2DBDFT=tstest 
 
db2 connect to tstest 
 
db2 "GRANT  DBADM ON DATABASE  TO USER <instance owner>" 
 
db2ts "enable database for text" 
 
db2 "create table book (id int not null primary key,title 
varchar(400))" 
 
 
db2 "insert into book values (1,'IBM Text Search 
---------------')" 
db2ts "create index titleidx for text on book (title)" 
 
db2ts "update index titleidx for text" 
 
 
another user with less than 8 character login name run the 
following select statement 
 
db2 "select * from book where contains(title,'Text')=1" 
 
 
 
This select command returns SQL20425N. 
 
 
 
SQL20425N 
 
Column 'TITLE' in table 'BOOK' was specified as an argument to a 
text 
search function, but a text search index does not exist for the 
column. 
 
same select command will run fine is if we do not set 
"DB2_COMPATIBILITY_VECTOR=ORA".
Problem Summary:
TEXT SEARCH QUERY RETURNS SQL20425N WHEN ORACLE COMPATIBILIT 
MODE IS ENABLED
Local Fix:
available fix packs:
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 6 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 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
This APAR is first fixed in V9.7 FP2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.02.2010
14.05.2010
14.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList