Asynchronous indexing and triggers

You can update the text search index on the OmniFind Text Search Server for DB2® for i manually or schedule it to run automatically.

The text search index maintained on the OmniFind Text Search Server for DB2 for i is not updated synchronously when the DB2 table is updated. Updating a text search index is an extensive operation.

Instead, changes to the DB2 table column are captured by triggers to a local log table. This log table is also called a staging table. These triggers automatically store information about new, changed, and deleted documents in a log table. Each log table is associated with one text search index. Applying the contents of the log table to its corresponding text search index is called an incremental update.

You must periodically update the text search index in order for changes to be reflected in queries.

You can update the text search index manually by calling the SYSPROC.SYSTS_UPDATE stored procedure.

Updates can also be scheduled to occur automatically by using the UPDATE FREQUENCY clause on the SYSPROC.SYSTS_CREATE procedure when the text index is created.