Shared-Object Filename

Syntax

(1)

1 1  %C Shared-Object File2
1 3  %Java Shared-Object
File4

Usage

If the IFX_EXTEND_ROLE configuration parameter is set to 1 or to ON, only users to whom the DBSA has granted the built-in EXTEND role are authorized to use this segment. (Whether or not IFX_EXTEND_ROLE is enabled, you must hold the Resource privilege or the DBA privilege on the database, and you must also hold the Usage privilege on the external programming language in which the UDR is written, before you can create, drop, or alter an external UDR.)

The Database Server Administrator should include in the DB_LIBRARY_PATH configuration parameter settings every file system where the security policy authorizes DataBlade® modules and UDRs to reside. Unless DB_LIBRARY_PATH is absent or has no setting, the database server cannot access a file that this segment specifies unless its pathname begins with a string that exactly matches one of the values of DB_LIBRARY_PATH.

For example, if "$ONEDB_HOME/extend" is one of the DB_LIBRARY_PATH values on a Linux™ system, then shared-object files can have pathnames within the $ONEDB_HOME/extend file system or its subdirectories. This directory is also the file system where built-in DataBlade modules reside, and the default location where the DataBlade Developers Kit creates user-defined DataBlade modules.This directory is also the file system where built-in DataBlade modules reside.

The syntax by which you specify a shared-object filename depends on whether the external routine is written in the C language or in the Java language. Sections that follow describe each of these external languages.

For more information about the context in which a shared-object filename appears within EXTERNAL NAME clause of the ALTER FUNCTION, ALTER PROCEDURE, ALTER ROUTINE, CREATE FUNCTION, and CREATE PROCEDURE statements, see the related reference, External Routine Reference.