Oracle Autonomous Transaction Processing Adapter Restrictions

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

  • 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.

  • 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.