DB2 Text Search Indexing Server failure and recovery
What happens in the event of a text indexing server failure during the initial text index create or incramental text index update operations.
In the event of a text indexing server failure during the initial index update before the first commit point is reached, db2 text search will do a partial commit.
In the event of an text indexing server failure during the initial index update after the first commit point is reached, db2 text search will roll back to the last commit point.
In the event of a text indexing server failure, all preprocessing servers continue to run as usual and automatically attempt to reconnect to the indexing server until it is restored.
Preprocessing servers continue to prepare any documents that were pulled from the indexing server's input queue before the failure occurred. When the indexing server is restored and the preprocessing servers reconnect, any documents that are pushed to the indexing server's output queue are disregarded.
A warning message is generated for each of these documents in the log.
If an indexing server failure occurs while the Java client is being used to submit an array of documents for indexing, these documents must be resubmitted to the indexing server after it is restarted.
If an indexing server failure occurs while the C++ client is being used to submit documents for indexing, all documents that were submitted since the last commit are lost. These documents are not written to the index and must be resubmitted to the indexing server after it is restarted.
More support for:
DB2 for Linux, UNIX and Windows
Extenders - Text Extender
Software version: 9.5, 9.7, 9.8
Operating system(s): AIX, Linux, Solaris, Windows
Software edition: Advanced Enterprise Server, Enterprise Server, Workgroup Server
Reference #: 1631918
Modified date: 2014-06-26