The following restrictions apply to external procedures.
- If the UDF library for your database contains any objects with multibyte characters in their name, you cannot use a single-byte session character set to create a new UDF, UDT, method, or Java external procedure object even if the new object name contains only single-byte characters. Instead, use a multibyte session character set.
- You cannot perform a CREATE PROCEDURE (External Form) request from an embedded SQL application.
- You can only execute SQL function calls using the CLIv2 or JDBC APIs.
- You cannot include CLIv2 or JDBC SQL function calls that execute the administration of row-level security constraints in any way in an external procedure definition.
- You cannot write Java strings into columns of a global temporary trace table (see CREATE GLOBAL TEMPORARY TRACE TABLE) having the following data types.
- LONG GRAPHIC
Though you can define global temporary trace table columns with these types, the Java language does not support them, so you cannot write Java strings into them from a Java procedure.
- There are also several restrictions for external procedures that are invoked by triggers. See Triggers and External Stored Procedures That Make SQL Calls for details.
The following additional restrictions apply to Java external procedures only.
- You cannot access LOBs using inline processing with dynamic result sets.
- You cannot process result sets from other sessions or databases.
- Java procedures do not support pass back from call to call for dynamic result sets.
The results cannot be passed up a level at a time.
- You cannot mix non-result set and dynamic result set requests in a multistatement request.
- You cannot copy result sets.
Making a copy of a result set object does not return it twice.
- An SQL procedure cannot consume the dynamic results from a call to a Java procedure.