The DB2 Net Search Extender (NSE) text index update operations are not running as scheduled

Technote (troubleshooting)


Problem(Abstract)

When multiple text indexes are all set up to run the update operation at the same time , the update operation does not seem to start on time and the update operations seem to be drifting.

Symptom

NSE text index update operations are not starting on time.


Cause

When NSE text indexes are on a single file system the updates schedules for indexes are serialized in such a way that no two updates occur at the same time.

Diagnosing the problem

The time stamp on the "CTE0003 Index update started" message in the db2ext.event tables for the indexes is later than the update frequency.

Resolving the problem

To avoid serialization , every NSE text indexes must reside on its own
filesystem . Use the db2text alter index command to move the text indexes to their own file system

Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows
Extenders - Net Search Extender

Software version:

9.1, 9.5, 9.7, 9.8

Operating system(s):

AIX, HP-UX, Linux, Linux iSeries, Linux pSeries, Windows

Software edition:

Advanced Enterprise Server, Enterprise Server, Express, Express-C, Personal, Workgroup Server

Reference #:

1644226

Modified date:

2013-07-18

Translate my page

Machine Translation

Content navigation