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.
TutorialThis section provides a step-by-step procedure for setting up and performing text searches by using the module.
Create a table containing a text search column
Create dbspaces and sbspaces for storageFor optimal performance and to take advantage of the data management facilities of a DBMS, such as transaction rollback, store your text search table and associated indexes in dbspaces and sbspaces that you allocate specifically for this purpose.

Create dbspaces and sbspaces for storage

For optimal performance and to take advantage of the data management facilities of a DBMS, such as transaction rollback, store your text search table and associated indexes in dbspaces and sbspaces that you allocate specifically for this purpose.

If you are using a CLOB, BLOB, or IfxMRData data type, you must store your data in an sbspace. Synonym and stopword lists are also stored in sbspaces. And since etx indexes are also stored in sbspaces, they are always detached, because the table that contains the indexed column is stored in a dbspace.

The following example creates a dbspace named dbsp1 with an initial offset of 0 and a size of 10 MB:

onspaces -c -d dbsp1 -p /Dbspace/dbsp1 -o 0 -s 10000

The following example creates two sbspaces named sbsp1 and sbsp2, each with an initial offset of 0 and a size of 100 MB, and logging turned on:

onspaces -c -S sbsp1 -g 2 -p /SBspace/sbsp1 -o 0 -s 100000 -Df "LOGGING=ON"
onspaces -c -S sbsp2 -g 2 -p /SBspace/sbsp2 -o 0 -s 100000 -Df "LOGGING=ON"