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™.
Creating extensionsYou can create user-defined data types, routines, access methods, and other database objects to suit your needs. You can use application programming interfaces to write user-defined routines and applications that access data in HCL OneDB™ databases.
DataBlade® Developers KitThe DataBlade® Developers Kit (DBDK) guides contain information about the tools you can use to develop and package DataBlade® modules, which extend the functionality of HCL OneDB™ databases.
DataBlade® Developers Kit User's GuideThe HCL OneDB™ DataBlade® Developers Kit Users Guide describes how to use OneDB® DataBlade® Developers Kit (DBDK) tools to develop and package DataBlade® modules.
Debugging and testing DataBlade® modules on UNIX™This section describes how to debug and perform functional tests for DataBlade® modules written in C for HCL OneDB™ on UNIX™.
The shared object fileA DataBlade® module exists in the HCL OneDB™ database server as a shared object. The shared object file is loaded into the database server the first time one of its routines is executed after the database server is started. The shared object file is unloaded every time the database server is stopped.
Replace a shared object fileWhen a DataBlade® module is loaded onto the HCL OneDB™ database server, the database server stores it in the database server memory map. Therefore, if you overwrite a shared object file while it is loaded in the database server, you must stop and restart the database server to unload the old shared object file and load the new one.

Replace a shared object file

When a DataBlade® module is loaded onto the HCL OneDB™ database server, the database server stores it in the database server memory map. Therefore, if you overwrite a shared object file while it is loaded in the database server, you must stop and restart the database server to unload the old shared object file and load the new one.

If you do not stop and restart the database server after replacing a shared object, the database server might fail when you call a DataBlade module routine.

To unload a module without restarting the HCL OneDB database server, you must drop all objects in the module by using the SQL DROP statement. After all objects in the module have been dropped and all instances of the routines have finished executing, the symbol references to the DataBlade module shared object are invalidated, and a message is recorded in the log file.

After the module is unloaded, replace the shared object file and load it into the database.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.