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

INCONSISTENT STATE OF SYSIBMTS SCHEMA OBJECTS CANNOT BE CLEANED

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
DB2 Text Search feature was successfully disabled using force
option:

DB2TS DISABLE DATABASE FOR TEXT FORCE
CIE00001 Operation completed successfully.

but there remain text search catalog objects in schema SYSIBMTS.

Trying to enable DB2 Text Search feature using:
DB2TS ENABLE DATABASE FOR TEXT
fails with error:
SQL20427N  An error occurred during a text search administration
procedure or command.
The error message is "CIE00364 Inconsistent objects in specified
or default database. ". SQLSTATE=38H14

This inconsistent state cannot be cleaned.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Any user that accidentally places their catalog tables in an *
* inconsistent state as described in the APAR body is          *
* affected.                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to db2_v111m1fp2 or greater                          *
****************************************************************
Local Fix:
Drop the inconsistent database and rebuild.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT19284 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.08.2017
10.10.2017
10.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)