Load an executable code into memory

To execute a UDR written in an external language, the executable code must reside in database server memory. On the first invocation of a UDR, the routine manager loads into memory the file that contains the UDR. The database server locates that file from the externalname column in the sysprocedures system catalog table.

Use the onstat command-line utility with the -g dll option to view the dynamically loaded libraries in which your UDRs reside. For information about the onstat command, refer to the HCL OneDB™ Administrator's Reference.

You must install shared libraries and .jar files on all database servers that need to run the UDRs, including database servers involved in Enterprise Replication (ER) and High-Availability Data Replication (HDR). The shared object files and .jar files need to be installed under the same absolute path name.

After the routine manager has loaded an external-language routine into memory, this file remains in memory until it is explicitly unloaded or the database server is shut down. For more information, see Drop a user-defined routine.