Note the following Oracle Database Adapter restrictions in Oracle Integration.

• Using the Oracle Database Adapter to access the Oracle E-Business Suite Database is not recommended. Instead, use the Oracle E-Business Suite Adapter to access the Oracle E-Business Suite Database.
• The Oracle Database Adapter can only be used with the on-premises connectivity agent.
• 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 such invokes is not supported and goes through a 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 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.
• The Oracle Database 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.
• When using the Oracle Database Adapter with a PureSQL statement operation, carriage returns are not supported in the SQL statement.

• Cross schema stored procedures are not allowed in cases where Oracle Integration must generate the wrappers.

• The Oracle Database Adapter does not support polling when the logical delete column is in lower case.
• No order is maintained while polling records.