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.
Binary data typesThe binary18 and binaryvar data types allow you to store binary-encoded strings, which can be indexed for quick retrieval.
Binary data type functions
Support functions for binary data types
The bdttrace() function

The bdttrace() function

The bdttrace() function specifies the location where the trace file is written.

Syntax

bdttrace(filename)

filename: The full path and name of the file to which trace information is appended. The file must be writable by user informix. If no file name is provided, a standard session_id.trc file is placed in the $INFORMIXDIR/tmp directory. If the file already exists, the trace information is appended to the file.

Use the bdttrace() function to troubleshoot events related to binary data types.

To enable tracing, create a trace class by inserting a record into the systemtraceclasses system catalog:

insert into informix.systraceclasses(name) values ('binaryUDT')

For more details regarding tracing, see the HCL OneDB™ Guide to SQL: Reference.

bdttrace(tracefile)