Usage Restrictions for External Procedures
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 stored procedure object even if the new object name contains
only single‑byte characters. Otherwise, Teradata Database aborts the request and returns
an error to the requestor. Instead, use a multibyte session character set.
You cannot perform a CREATE PROCEDURE (External Form) request from an embedded SQL
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” on page 317) having the following data types.
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
There are also several restrictions for external procedures that are invoked by triggers.
See “Triggers and External Stored Procedures That Make SQL Calls” on page 721 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.
In other words, 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
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.