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.
Database Extensions User's GuideThe HCL OneDB™ Database Extensions User's Guide explains how to use the database extensions that come with HCL OneDB™: Large Object Locator, MQ messaging, binary data types, basic text search, node data type, HCL OneDB™ web feature service for Geospatial Data, and SQL packages.
Basic Text SearchYou can perform basic text searching for words and phrases in a document repository stored in a column of a table.
Preparing for basic text searchingBefore you can perform basic text searching, you must prepare the server environment and create the bts index. Review the requirements and restrictions.
Creating a bts indexYou create a bts index by using the bts access method and specifying index parameters and other options.
bts access method syntaxThe bts access method is a secondary access method to create indexes that support basic text search queries.
xact_ramdirectory index parameterBy default, you build a bts index in a temporary sbspace. You can build a bts index faster in RAM than in a temporary sbspace.

xact_ramdirectory index parameter

By default, you build a bts index in a temporary sbspace. You can build a bts index faster in RAM than in a temporary sbspace.

Include the xact_ramdirectory="yes" in the bts index to build the index in memory. However, when building the index in memory uses too much memory, the build is switched to the temporary sbspace. The maximum amount of memory that is allowed for an index build is approximately one third of the value of that is specified by the xact_memory index parameter or the SHMTOTAL configuration parameter, whichever is more restrictive.