Oracle Database Cloud Service Adapter Restrictions
Note the following Oracle Database Cloud Service Adapter restrictions in Oracle Integration.
- The database password length cannot exceed 20 characters.
- Database schema names with hyphens (
-
) are not supported. - All integrations that
include stored procedure, PureSQL, or operation on table
database operations must finish within 240 seconds.
Otherwise, the query times out and a
Limit Exceeded
error occurs. - Overloaded procedures are not supported.
- Wrappers are not generated for releases 18c and later of the database. Any integrations created on prior releases of the database that contain wrappers require a manual migration of the wrapper procedures. A re-edit of the invoke connection is not supported and goes through the non-wrapper route by selecting the original procedure.
- Automatic metadata refresh is not supported. Any modifications to stored procedures or tables used in the invoke or trigger connection require a re-import or redo in the Adapter Endpoint Configuration Wizard for the changes to be reflected.
- The PL/SQL boolean type is not supported as an IN/OUT parameter in a stored procedure if the target database is version 18c or higher. However, you can create a wrapper stored procedure that converts a PL/SQL boolean type to an integer and uses that wrapper stored procedure in Oracle Integration.
- The Oracle Database Cloud Service
Adapter uses JDBC drivers to interact with the database and is restricted by JDBC driver
constraints. Therefore, the nested PL/SQL type (for example, a
RECORD
type inside aTABLE
type) is not supported as an IN/OUT parameter in a stored procedure if the target database is version 18c or higher. However, you can defineOBJECT
types insideTABLE
types.
Note:
There are overall service limits with Oracle Integration. A service limit is the quota or allowance set on a resource. See Service Limits.