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.
Configure your database server for filteringThis section describes steps you complete before you create an index with the FILTER parameter.
Specify the ETX VPCLASS

Specify the ETX VPCLASS

The filtering routines execute in their own virtual processor called ETX, not in the CPU virtual processor. To start an ETX virtual processor, add the following line to the onconfig file and restart the database server with the oninit utility:

VPCLASS ETX,noyield,num=XXX

where XXX is the maximum number of ETX virtual processors you want to run. You might run more than one ETX virtual processor so that more than one user can use the filtering capability at a time.

You do not need to know how to configure or use the filter server. It is described in this section for your information only.

Each ETX virtual processor starts its own filter server. If you start four ETX virtual processors, you might also have a maximum of four filter servers running. The filter servers run on the same computer as the database server.