Enable tracing

If you specify CONTINUE_ON_ERROR for the FILTER index parameter, you must also set up a trace log to capture any errors encountered while filtering documents when you create an index, insert rows, or update rows in the table. A filtering error typically occurs when the format of a document that is about to be filtered is not in the list of supported formats. See Document formats you can filter, for the full list of formats supported by the module.

Important: The trace log is different from the filter log file described in Logging messages from the filter server. The filter log file contains messages from the filter server; the trace log contains trace messages from the .

To enable tracing, execute the etx_FilterTraceFile() procedure in DB-Access:

EXECUTE PROCEDURE EtxFilterTraceFile ('/tmp/etx_errors');

The trace messages are written to the file /tmp/etx_errors.

If the format of a document that is about to be filtered is not in the list of supported formats, you might get a message similar to the following message in the trace file:

10:29:17  Filter Message: Could not filter document
10:29:17  filter failed for row(row:257 fragid:1048870),ignoring error

In the example, the index parameter FILTER='CONTINUE_ON_ERROR' was specified when the etx index was created. If STOP_ON_ERROR had been specified, the last line would say stopping instead of ignoring error.

See The EtxFilterTraceFile() routine for detailed information about this procedure.

Tip: To enable more detailed tracing, use the TxtSetTrace() procedure:

EXECUTE PROCEDURE TxtSetTrace('EtxExcalIndex 1', '/tmp/etx_level1_msgs');

EtxExcalIndex 1 specifies level-1, or filter, tracing. You can also specify EtxExcalIndex 2 to enable level-2 tracing (messages for main indexing operations, such as inserts and scans) and EtxExcalIndex 3 to enable level-3 tracing (messages regarding tuning parameters evaluated by the search engine).