1. Using the Oracle Autonomous Transaction Processing Adapter with Oracle Integration Generation 2
  2. Understand the Oracle Autonomous Transaction Processing Adapter
  3. Oracle Autonomous Transaction Processing Adapter Restrictions

Oracle Autonomous Transaction Processing Adapter Restrictions

Note the following Oracle Autonomous Transaction Processing Adapter restrictions in Oracle Integration.

  • Using the bulk data import operation with the connectivity agent is not supported.
  • 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 Transaction Processing Adapter.
  • For direct connections (configured without using the connectivity agent), the Oracle Autonomous Transaction Processing Adapter can only be used for making outbound invocations as an invoke connection. This type of Oracle Autonomous Transaction Processing Adapter-specific connection cannot be configured as a trigger connection in an integration. Use cases related to inbound polling must be implemented using the scheduled orchestration integration pattern.

  • 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 Transaction Processing 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 a TABLE type) are not supported as IN/OUT parameters in a stored procedure. However, you can define OBJECT types inside the TABLE 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.