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

DELETING ALL ROWS FROM TEXT INDEXED TABLE AND THEN RUNNING TEXT INDEX
UPDATE OPERATION THROWS CTE0310 ERROR MESSAGE.

product:
DB2 NET SEARCH / 5765F3800 / 970 - DB2
Problem description:
The problem here is that , since all rows in base table is 
deleted and  then we update index, all index entires are 
removed , so the .ded, .dei files are missing. And when these 
files are not present, the  disk space calculation is going 
wrong.
Problem Summary:
CTE0310 Error is thrwon when the indexed table is deleted of all 
rows. Disk space calculation has been updated to consider empty 
base table.
Local Fix:
Deleting all of the rows and then running update operation is 
the same as dropping the text index. Customer should simply drop 
the text index. 
 
or 
 
Customer could skip the update index operation after the - "db2 
delete , db2 commit" operations , and continue with db2 import. 
After import, Customer can then do a single update index, which 
will take care updating the index of the deleted documents as 
well as the newly imported  rows.
available fix packs:
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 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
Upgrade to V97fp5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.02.2011
21.11.2011
21.11.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList