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.
AdministrationThe purpose of this section is to make database administrators aware of configuration and performance issues related to the features of the module.
Refine etx indexesThis section describes ways you can refine your etx index to improve the performance of searches.
Share etx indexesThe etx indexes are to be left open to improve performance of subsequent queries that use the index.

Share etx indexes

The etx indexes are to be left open to improve performance of subsequent queries that use the index.

The first time an etx index is used in a query (opened), resources such as shared memory are allocated in the database server, and these resources continue to be allocated after the query has finished executing. This causes the first query that opens the etx index to run slower than subsequent user sessions that use these already-opened resources.

When opened, an etx index does not automatically free the shared resources until the database server shuts down. An etx index does free shared resources after an update, insertion, or deletion to the table, or during a rollback of a transaction that uses the index. If you must free resources, you can force an etx index to close by executing the etx_CloseIndex() routine. Be aware, however, that the next user who reopens the etx index again incurs the initial cost of storing index information in memory.