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.
SQL Packages ExtensionThe SQL packages extension provides SPL routines that you can use in an application that is compatible with database servers other than HCL OneDB™.
DBMS_ALERT packageThe DBMS_ALERT package provides a set of procedures for registering for alerts, sending alerts, and receiving alerts.

DBMS_ALERT package

The DBMS_ALERT package provides a set of procedures for registering for alerts, sending alerts, and receiving alerts.

Alerts are stored in the DBMS_ALERT_EVENTS, DBMS_ALERT_REGISTERED, and DBMS_ALERT_SIGNALED tables which are created in your database when you register the package.

The DBMS_ALERT package includes the following system-defined routines.

Table 1. System-defined routines available in the DBMS_ALERT package
Routine name	Description
REGISTER procedure	Registers the current session to receive a specified alert.
REMOVE procedure	Removes registration for a specified alert.
REMOVEALL procedure	Removes registration for all alerts.
SIGNAL procedure	Signals the occurrence of a specified alert.
SET_DEFAULTS procedure	Sets the polling interval for the WAITONE and WAITANY procedures.
WAITANY procedure	Waits for any registered alert to occur.
WAITONE procedure	Waits for a specified alert to occur.

Usage notes

The procedures in the DBMS_ALERT package are useful when you want to send an alert for a specific event. For example, you might want to send an alert when a trigger is activated as the result of changes to one or more tables.