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.
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™.
Virtual tables for time series dataA virtual table provides a relational view of your time series data.
Trace functions
The TSSetTraceFile function

The TSSetTraceFile function

The TSSetTraceFile function specifies a file to which trace information is appended.

Syntax

TSSetTraceFile(traceFileName  lvarchar)
returns integer;

traceFileName: The full path and name of the file to which trace information is appended.

Description

The file you specify using TSSetTraceFile overrides any current trace file. The file is located on the server computer. The default trace file is /tmp/session_number.trc.

TSSetTraceFile calls the mi_set_trace_file() DataBlade® API function. For more information about mi_set_trace_file(), see the HCL OneDB™ DataBlade API Programmer's Guide.

Returns

Returns 0 on success, -1 on failure.

Example

The following example sets the file /tmp/test1.trc to receive trace information:

execute function TSSetTraceFile('/tmp/test1.trc');