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

DB2TS INDEX WITH THE CONTAINS FUNCTION DOESN'T BRING SOME WORDS WITH
ACCENT MARKS WITH DATABASE IN CODEPAGE 819

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When working with DB2 text search index with XML in database 
with codepage 819, characters with accent marks are not returned 
properly. 
 
select pkey, xmlserialize(text as varchar(160)) from xmltest 
where contains(text,'Acentua&#231;&#227;o')<>0 
 
PKEY        2 
----------- 
---------------------------------------------------------------- 
---------------------------------------------------------------- 
-------------------------------- 
          2 <row><text1>Acentuacao 
removida</text1><text2>Palavrascom acentuacao so que escritas 
sem</text2></row> 
 
  1 registro(s) selecionado(s). 
 
The XML text is always stored in the database in unicode, but 
for plain text and XML, TS always does a conversion from the 
database codepage to unicode during the indexing stage. When the 
database codepage is 819, the TS does an extra conversion from 
codepage 819 to codepage 1208 conversion for XML which is 
already in codepage 1208 when fetched from the database. This 
caused corrupted indexes and problems during queries
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 8                               * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 10.5 Fix Pack 8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.07.2016
13.03.2017
13.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)