When you stop the DB2® Text
Search instance services, the text search server closes all commands
that are currently active.
About this task
The active commands are closed as follows:
- creating the collection for the text search index is completed,
implying that a CREATE INDEX FOR TEXT operation could fail in a multi-partition
setup, as a text search index is partitioned into multiple collections.
- if drop collection already started to remove files irreversibly,
the drop is completed, otherwise the command is rolled back
- processes the current documents in the queue. Does not accept
other documents. An initial update is marked as attempted and restart,
an incremental update repeats processing all entries in the staging
table.
- if you update the index with the updateautocommit option,
the documents that are already submitted when the text search server
closes are implicitly committed and are processed. The rest of the
documents are not processed. For example, consider that the text server
is shut down unintentionally. As it shuts down, there are 1000 documents
to be indexed and the update index command was issued with the updateautocommit option
set to 100. If you check the number of documents that are indexed
with the adminTool, you will see an arbitrary value
(not multiple of 100) as NumOfDocuments indexed.
In other words, a partial commit occurs during shutdown.
New commands are not accepted while the text search server completes
the stop processing.
Procedure
To stop the DB2 Text
Search server: for the integrated
DB2 Text Search instance
service, enter the following command:
db2ts "STOP FOR TEXT"
for the stand-alone text search server, run the shutdown script
from the
<ECMTS_HOME> directory, where
<ECMTS_HOME> represents
the installation directory of the stand-alone text search server.
DB2 10.5 for Linux, UNIX, and Windows