Oracle Autonomous Data Warehouse Adapter Restrictions
Note the following Oracle Autonomous Data Warehouse Adapter restrictions in Oracle Integration.
- Overloaded procedures are not supported.
- Automatic metadata refresh is not supported. Any modifications to stored procedures or tables used in the invoke or trigger connection must be re-imported or redone in the Adapter Endpoint Configuration Wzard for the changes to be reflected.
- 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. - Access to object storage is a requirement for using the bulk data import operation. Oracle Integration for SaaS consists of a subscription-based account dedicated to Oracle Integration, and does not include services such as object storage. You must obtain a separate trial account to provision object storage for use with the Oracle Autonomous Data Warehouse Adapter.
-
The PL/SQL boolean type is not supported as an IN/OUT parameter in a stored procedure. However, you can create a wrapper stored procedure that converts PL/SQL boolean to an integer and use those wrapper stored procedures in Oracle Integration.
- The Oracle Autonomous Data Warehouse
Adapter uses JDBC drivers to interact with the database and is restricted by JDBC
driver constraints. Therefore, nested PL/SQL types ( for example,
RECORD
types inside aTABLE
type) are not supported as IN/OUT parameters in a stored procedure. However, you can defineOBJECT
types inside theTABLE
type. -
Cross schema stored procedures are not allowed in cases where Oracle Integration must generate the wrappers.
Note:
There are overall service limits with Oracle Integration. A service limit is the quota or allowance set on a resource. See Service Limits.