Messages and limitations of the Amazon RDS for Oracle connector

Message code list of AMAZONRDSORACLE category
Exception messages of AMAZONRDSORACLE category
Limitations of AMAZONRDSORACLE category

Message code list of AMAZONRDSORACLE category

The following message codes correspond to errors that occur in Amazon RDS for Oracle Connector.

This message code is output when an undefined error occurs.

Cause	Solution
An undefined error occurred.	Check the error message or the help of the operation in which the error has occurred.

Corresponding error

None

AMAZONRDSORACLE0001E

This message code corresponds to errors that occur during database processing.

Cause	Solution
The cause differs according to each error message.	Check the error message and perform the following: Check whether the cause/solution of the error is described in "Exception messages" below. Check whether the cause/solution of the error is described in Limitations of the applied connector. Check whether you can find information related to the error in documents of the connected database.

Cause

Solution

The cause differs according to each error message.

Check the error message and perform the following:

Check whether the cause/solution of the error is described in "Exception messages" below.
Check whether the cause/solution of the error is described in Limitations of the applied connector.
Check whether you can find information related to the error in documents of the connected database.

Corresponding error

java.sql.SQLException
java.sql.SQLRecoverableException
java.sql.SQLSyntaxErrorException

Exception messages of AMAZONRDSORACLE category

Exception name		Cause	Solution
InputDataNotFoundException		Input data isn't specified.	Specify Input data or draw data flow.
InvalidPropertyConfigurationException		SQL statement isn't set.	Specify SQL statement.
InvalidPropertyConfigurationException Target column is not selected.		Target for Schema definition isn't selected in the Write Table operation.	Select one or more Target for Schema definition.
InvalidPropertyConfigurationException Target column is not selected.		Target for Schema definition isn't selected in the Read Table operation.	Select one or more Target for Schema definition.
InvalidPropertyConfigurationException		Table name isn't set.	Specify Table name.
InvalidPropertyConfigurationException		Procedure isn't set.	Specify Procedure.
InvalidPropertyConfigurationException Table name is not specified.		A table name isn't selected.	Specify Table name.
java.sql.SQLException		A database access error or some other one has occurred.	Check the SQLException message. SQLException message is based on the specifications of the driver. The cause of the error might be output in SQLException message. For details on messages, contact the database vendor.
ResourceNotFoundException Resource definition could not be found. Name: []		Destination isn't specified.	Specify Destination.
ResourceNotFoundException Resource definition could not be found. Name: [<connection resource name>]		The resource definition selected in Destination isn't found.	Check the connection resource specified in Destination.
java.sql.SQLException	ORA-01017: invalid username/password; logon denied	The user name or the password is incorrect.	Check User name or Password of the connection resource.
java.sql.SQLException	Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor	The SID is invalid.	Check SID or URL of the connection resource.
java.sql.SQLRecoverableException	The Network Adapter could not establish the connection	Can't connect to the database.	Check Host name or Port number of the connection resource.
java.sql.SQLSyntaxErrorException	ORA-00942: table or view does not exist.	Either the table or the view doesn't exist or the table or view name might not be enclosed with quotation marks.	Specify an existing table or view in Table name. Also check whether the table or view name specified in Table name is enclosed with quotation marks.

Supported types

This connector supports the following types.

Type name	Support	Remarks
CHAR	Limited
NCHAR	Limited
VARCHAR2	Yes
NVARCHAR2	Limited
LONG	Yes
NUMBER	Limited
FLOAT	Limited
DATE	Limited
TIMESTAMP	Limited
TIMESTAMP WITH TIME ZONE	Limited	Data is handled as String.
RAW	Yes
LONG RAW	Yes
BLOB	Yes
CLOB	Yes
NCLOB	Yes

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

Common to all operations

Specification limits

Displaying table list
- Tables that belong to the schema of the user specified in User name in the connection resource are displayed.
- Synonyms aren't 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's 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 statements 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 can't be received.
Default value of Fetch size is 100.

Write Table

Specification limits

CHAR
- When updating, if the column in which you selected 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's 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 statements 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 can't 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 a 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 a 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 can't be gotten as output parameter, and the operation fails with the following error during script execution.
- [exec_procedure] failed. Cause: [java.sql.SQLException:ORA-06550: row 1, column 7:
  
  PLS-00221: '<procedure>' is not a procedure or is undefined
  
  ORA-06550: row1, column7:
  
  PL/SQL: Statement ignored
  
  ]
PL/SQL types such as BOOLEAN aren't supported.
Synonyms aren't supported.
A procedure whose schema is different from the schema of the user specified in User name in the connection resource can't be used.