Security for loading external modules

Use the DB_LIBRARY_PATH configuration parameter to control the location from which shared objects, such as external modules, can be loaded.

Use the DB_LIBRARY_PATH configuration parameter to specify a comma-separated list of valid directory prefix locations from which the database server can load external modules, such as DataBlade® modules. DB_LIBRARY_PATH takes effect when the database server is restarted after the parameter has been set.

Use the DB_LIBRARY_PATH configuration parameter to control the location from which shared objects can be loaded, and enforce policies and standards on the formats of the EXTERNAL NAME clause of the CREATE FUNCTION, CREATE PROCEDURE, and CREATE ROUTINE statements.

If the DB_LIBRARY_PATH configuration parameter is not set or is not present in the onconfig file, security checks for loading external modules are not performed.

You must include in the DB_LIBRARY_PATH settings every file system in which your security policy authorizes DataBlade modules and UDRs to be located. DataBlade modules provided with HCL® OneDB® are stored under the $INFORMIXDIR/extend directory. For extensibility to work properly when security is turned on, the string "$INFORMIXDIR/extend" must be part of DB_LIBRARY_PATH.

For more information about the DB_LIBRARY_PATH configuration parameter, see the HCL OneDB Administrator's Reference.