Oracle 23ai Adapter Limitations

• Supported Types
• Limitations Common to All Operations
• Read Table
• Execute Select SQL
• Write Table
• Execute Update SQL
• Execute Stored Procedure
• Write by Loader
• Major Exceptions

Supported Types

• Yes: Supported.
• Limited: Supported with limitations.
• No: Not supported.

Limitations Common to All Operations

Specification limits

• Displaying table list
  • Tables that belong to the schema of the user specified in [User name] in the global resource are displayed.
  • Synonyms are not displayed, but you can directly enter them in [Table name] or [SQL statement].

Read Table

Specification limits

• When the table name is enclosed with quotation marks, it is case-sensitive.


• Default value of [Fetch size] is 100.

Execute Select SQL

Specification limits

• NUMBER, FLOAT
  • When the Precision of a query result is 0, the data is handled as BigDecimal. For example, even if Precision is set to the column specified in SUM function, 0 will be returned as a result, so the result of SUM function will be handled as BigDecimal.
• SQL statement with functions
  • SQL statement with SQL functions can be executed.
  • Though the SQL statement with user-defined functions can be executed, the value of OUT parameter defined in the functions cannot be received.
• Default value of [Fetch size] is 100.

Write Table

Specification limits

• CHAR
  • When updating, if the column in which you checked [Schema definition/Key] is CHAR type, the key value of the input data has to be padded in the same size.
• When the table name is enclosed with quotation marks, it is case-sensitive.

Execute Update SQL

Specification limits

• CHAR
  • When a CHAR type column is specified in the WHERE clause of an UPDATE statement, and getting the value of the column with SQL parameter, the key value of the input data has to be padded in the same size.
• SQL statement with functions
  • SQL statement with SQL functions can be executed.
  • Though the SQL statement with user-defined functions can be executed, the value of OUT parameter defined in the functions cannot be received.

Execute Stored Procedure

Specification limits

• CHAR
  • Unnecessary spaces might be added to an OUT parameter of CHAR type.
• Procedure description
  • Procedures defined in a package are described as [package name].[procedure name].
  • When a package name includes dot (.), enclose the name with double quotations (").
    Example: In the case of “PROCEDURE” procedure that is defined in “SAMPLE.PACKAGE” package
    • "SAMPLE.PACKAGE".PROCEDURE
  • When a procedure name includes dot (.), enclose the name with double quotations (").
    Example: In the case of “SAMPLE.PROCEDURE” procedure that is defined in “PACKAGE” package.
    • PACKAGE."SAMPLE.PROCEDURE"
• When a stored function is specified in [Procedure], there are cases in which the return value of RETURN statement cannot be retrieved as output parameter, and the operation fails with the following error during script execution.
  • [exec_procedure] failed. Cause: [java.sql.SQLException: ORA-06550: '<procedure name>' is not a procedure or is undefined.]
• PL/SQL types are not supported.


• Synonym is not supported.


• A procedure of a schema that is different from the schema of the user specified in [User name] in the global resource cannot be used.

Write by Loader

Specification limits

• NCHAR, NVARCHAR2
  • Column length is handled as byte length, not string length.
    However, when the character set of Oracle Database Client is UTF-16, it is handled as string length.
• DATE
  • It has to be formatted in the standard format of Oracle as [YYYY-MM-DD] beforehand.
• TIMESTAMP
  • It has to be formatted in the standard format of Oracle as [YYYY-MM-DD Hh24:MI:SS] beforehand.
• When the table name is enclosed with quotation marks, it is case-sensitive.

Major Exceptions