Home
Extending 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 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™.
extensions and modulesThese topics describe how to use built-in database extensions and separately installed modules.
TimeSeries Data User's GuideThe HCL OneDB™ TimeSeries Data User's Guide contains information to assist you in using the TimeSeries extension with HCL OneDB™.
Pattern matching searchesYou can search time series data for matches to a particular pattern of values. For example, after you identify a pattern of abnormal electricity usage that indicates an outage, you can search for matches to that pattern to find other outages. Pattern matching searches find matches to a pattern that you supply. Pattern matching searches do not discover patterns in time series data.
Pattern matching routinesUse pattern matching routines to run pattern matching searches, to index data for pattern matching searches, and to perform maintenance tasks.
TSPMatchSetTraceFile functionThe TSPMatchSetTraceFile function sets the location and name of the tracing file for pattern matching routines.

TSPMatchSetTraceFile function

The TSPMatchSetTraceFile function sets the location and name of the tracing file for pattern matching routines.

Syntax

TSPMatchSetTraceFile(
                               trace_file   LVARCHAR)
returns INTEGER

trace_file: The path and name of the tracing file.

Usage

Run the TSPMatchSetTraceFile function to give the tracing file for pattern matching routines a different name and location from the default of /tmp/sessionID.trc, where sessionID is the session ID.

Returns

0 = Tracing is enabled.
An error.