Home
Extending HCL OneDB™Beyond standard relational database objects, HCL OneDB™ can be extended to handle specialized data types, access methods, routines, and other objects. HCL OneDB™ includes many built-in extensions that are fully integrated in the database server. HCL OneDB™ also provides DataBlade® modules, which are packages of extended database objects for a particular purpose and that are installed separately from the database server. Alternatively, you can create your own user-defined objects for HCL OneDB™.
HCL OneDB™ extensions and DataBlade® modulesThese topics describe how to use built-in database extensions and separately installed DataBlade® modules.
Excalibur Text Search DataBlade® Module User's GuideThese topics describe the module and how to access and use its components.
RoutinesThis section provides you with reference information about the etx_contains() operator and other routines defined for the DataBlade® module.
The EtxFilterTraceFile() routineThe EtxFilterTraceFile() routine enables tracing for filter operations.

The EtxFilterTraceFile() routine

The EtxFilterTraceFile() routine enables tracing for filter operations.

Syntax

EtxFilterTraceFile ( filename)


Element	Purpose	Data type
filename	The full path name of the trace file, relative to the server computer. The informix user must be able to write to this file.	LVARCHAR

None.

Use the EtxFilterTraceFile() procedure to set a trace log when you build an index on a column and specify FILTER='CONTINUE_ON_ERROR'.

After you have enabled tracing, you can disable tracing only by ending your user session.

See The FILTER parameter for more information about filtering and the FILTER index parameter.

The following example sets up a trace file for filtering operations in a temporary directory:

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