Messages and limitations of the Amazon Aurora for MySQL connector

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

Message code list of AMAZONAURORAMYSQL category

The following message codes correspond to errors that occur in Amazon AURORA for MySQL 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

AMAZONAURORAMYSQL0001E

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

AMAZONAURORAMYSQL0002E

This message code is output when a database connection failed.

Cause	Solution
Can't connect to the database.	Check the cluster endpoint and the port number.

Corresponding error

java.sql.SQLNonTransientConnectionException

Exception messages of AMAZONAURORAMYSQL 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.
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 is not found. Name: []		Destination isn't specified.	Specify Destination.
ResourceNotFoundException Resource definition is not found. Name: [<connection resource name>]		The resource definition selected in Destination isn't found.	Check the connection resource specified in Destination.
java.sql.SQLNonTransientConnectionException		Can't connect to the database.	Check Cluster Endpoint or Port number of the connection resource.
java.sql.SQLException	Communications link failure with primary. No active connection found for master. Caused by: java.sql.SQLException: Access denied for user '<user name>'@'%' to database '<database name>'	The database doesn't exist.	Specify an existing database in Database name of the connection resource.
java.sql.SQLException	Communications link failure with primary. No active connection found for master. java.sql.SQLException: Access denied for user '<user name>'@'<IP address>' (using password: YES)	The user name, the password, or the SSL connection is incorrect.	Check User name, Password, or SSL connection of the connection resource.
java.sql.SQLSyntaxErrorException	Table '<table name>' doesn't exist	The table doesn't exist.	Specify an existing table in Table name.

Limitations of AMAZONAURORAMYSQL category

Supported types
Read Table
Execute Select SQL
Write Table
Execute Update SQL
Execute Stored Procedure

Supported types

This connector supports the following types.

Type name	Support	Remarks
BOOL (BOOLEAN)	Yes	Alias of tinyint(1)
BIT	Limited
TINYINT	Yes
TINYINT UNSIGNED	Limited
MEDIUMINT	Yes
MEDIUMINT UNSIGNED	Limited
SMALLINT	Yes
SMALLINT UNSIGNED	Limited
INT (INTEGER)	Yes
INT UNSIGNED (INTEGER UNSIGNED)	Limited
BIGINT	Yes
BIGINT UNSIGNED	Limited
FLOAT	Limited
FLOAT UNSIGNED	Limited
DOUBLE	Limited
DOUBLE UNSIGNED	Limited
REAL	Limited
REAL UNSIGNED	Limited
DECIMAL (NUMERIC)	Yes
DECIMAL UNSIGNED (NUMERIC UNSIGNED)	Limited
DATE	Limited
DATETIME	Limited
TIMESTAMP	Limited
TIME	Limited
YEAR	Limited
CHAR	Limited
VARCHAR	Limited
BINARY	Yes
VARBINARY	Yes
TINYBLOB	Yes
TINYTEXT	Limited
BLOB	Yes
TEXT	Limited
MEDIUMBLOB	Yes
MEDIUMTEXT	Limited
LONGBLOB	Yes
LONGTEXT	Limited
ENUM	Limited
SET	Limited
JSON	No

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

Read Table

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type isn't supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
- If the number of digits is large, the correct value might not be retrieved.
  
  Example: if the number is "2.14748365E9", "2.14748006E9" will be retrieved.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
DATE, DATETIME, TIMESTAMP
- When data is 0000-00-00 00:00:00, it will be retrieved as null.
TIME
- If data is out of range from 00:00:00 to 23:59:59, only the hour will be converted among 00 and 23 and retrieved.
  
  Example: if the data is "27:15:00", it will be "03:15:00".
  
  Example: if the data is "-04:20:00", it will be "20:20:00". It won't be "19:40:00".
YEAR
- Data is handled as String.
TINYINT UNSIGNED, FLOAT UNSIGNED, DOUBLE UNSIGNED, REAL UNSIGNED, DECIMAL UNSIGNED
- It's displayed without UNSIGNED in Schema definition/Type.
Even when an optional extended attribute ZEROFILL is specified, the result is returned excluding 0.
The default value for Fetch size is 500.

Execute Select SQL

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type isn't supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
- If the number of digits is large, the correct value might not be retrieved.
  
  Example: if the number is "2.14748365E9", "2.14748006E9" will be retrieved.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
DATE, DATETIME, TIMESTAMP
- When data is 0000-00-00 00:00:00, it will be retrieved as null.
TIME
- If data is out of range from 00:00:00 to 23:59:59, only the hour will be converted among 00 and 23 and retrieved.
  
  Example: if the data is "27:15:00", it will be "03:15:00".
  
  Example: if the data is "-04:20:00", it will be "20:20:00". It won't be "19:40:00".
YEAR
- Data is handled as String.
TINYINT UNSIGNED, FLOAT UNSIGNED, DOUBLE UNSIGNED, REAL UNSIGNED, DECIMAL UNSIGNED
- It's displayed without UNSIGNED in Output schema definition/Type.
Even when an optional extended attribute ZEROFILL is specified, the result is returned excluding 0.
The default value for Fetch size is 500.

Write Table

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type isn't supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
- Values nearby the maximum value or the minimum value can't be written.
  
  Example: if the data is "3.402823466E+38", an error occurs.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
DATE, DATETIME, TIMESTAMP
- In the case of non-existent date, it's not written correctly.
  
  Example: When the date is "0000/00/00", it will be "0002/11/30".
TIME
- If the epoch second of time is negative value, it won't be written correctly.
  
  Example: if the data is "January 01, 1950 08:59:59", it will be "-08:59:59".
YEAR
- Data is handled as String.
TINYINT UNSIGNED, FLOAT UNSIGNED, DOUBLE UNSIGNED, REAL UNSIGNED, DECIMAL UNSIGNED
- It's displayed without UNSIGNED in Schema definition/Type.

Execute Update SQL

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type isn't supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
- Values nearby the maximum value or the minimum value can't be written.
  
  Example: if the data is "3.402823466E+38", an error occurs.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
DATE, DATETIME, TIMESTAMP
- In the case of non-existent date, it's not written correctly.
  
  Example: When the date is "0000/00/00", it will be "0002/11/30".
TIME
- If the epoch second of time is negative value, it won't be written correctly.
  
  Example: if the data is "January 01, 1950 08:59:59", it will be "-08:59:59".
YEAR
- Data is handled as String.

Execute Stored Procedure

Specification limits

BIT
- BIT type data whose size is 1 is handled as boolean. Other sized BIT type isn't supported.
FLOAT, FLOAT UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
- If the number of digits is large, the correct value might not be retrieved.
  
  Example: if the number is "2.14748365E9", "2.14748006E9" will be retrieved.
- Values nearby the maximum value or the minimum value can't be written.
  
  Example: if the data is "3.402823466E+38", an error occurs.
DOUBLE, DOUBLE UNSIGNED
- There are precautions for the precision with MySQL floating points.
  
  = Remarks =
  For details, refer to "MySQL Reference Manual" (https://dev.mysql.com/doc/).
CHAR, VARCHAR, TEXT, TINYTEXT, MEDIUMTEXT, LONGTEXT
- An error occurs when an argument with multi-byte characters is used.
TIME
- If data is out of range from 00:00:00 to 23:59:59, only the hour will be converted among 00 and 23 and retrieved.
  
  Example: if the data is "27:15:00", it will be "03:15:00".
  
  Example: if the data is "-04:20:00", it will be "20:20:00". It won't be "19:40:00".
- If the epoch second of time is negative value, it won't be written correctly.
  
  Example: if the data is "January 01, 1950 08:59:59", it will be "-08:59:59".
YEAR
- Data is handled as String.
ENUM, SET
- An error occurs when an argument with multi-byte characters is used.
TINYINT UNSIGNED, MEDIUMINT UNSIGNED, SMALLINT UNSIGNED, INT UNSIGNED, BIGINT UNSIGNED, FLOAT UNSIGNED, DOUBLE UNSIGNED, REAL UNSIGNED, DECIMAL UNSIGNED
- It's displayed without UNSIGNED in Input/Type and Output/Type.