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.
Hierarchical data typeThe node data type helps to resolve a difficult relational database problem–transitive closure.
The node data type for querying hierarchical dataThe node data type is an opaque type of variable length up to 256 characters.
Troubleshooting the node data typeError message specific to the node data type have the prefix UND. You can enable tracing on the node data type to diagnose problems.

Troubleshooting the node data type

Error message specific to the node data type have the prefix UND. You can enable tracing on the node data type to diagnose problems.

You might receive the following errors:


Error	Description
UNDE1: Invalid input string.	A node is invalid. Nodes cannot end in 0.
UNDE2: Illegal character found in input string.	An argument contains an illegal character. Nodes can contain only numeric characters.
UNDE3: Third input parameter is not descendant of first input parameter.	The third argument of a Graft function is not a descendant of the first argument.
UNDE4: Index to node element should be greater than or equal to 1.	A problem exists with the node indexing.

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

INSERT INTO informix.systraceclasses(name) VALUES ('Node');

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