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.
NSE text index update operations are not starting on time.
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