Messages and limitations of the JDBC connector
Message code list of JDBC category
The following message codes correspond to errors that occur in JDBC 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
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:
|
Corresponding error
-
java.sql.SQLException
This message code is output when the JDBC driver can't be found.
Cause |
Solution |
---|---|
The cause differs according to each error message. |
Check the class name and location of the JDBC driver. |
Corresponding error
-
java.lang.ClassNotFoundException
Exception messages of JDBC 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. |
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.lang.ClassNotFoundException |
JDBC driver isn't found. |
Check the class name and location of the JDBC driver. |
java.sql.SQLException |
This is an exception in database processing. |
Refer to specifications and manuals of the connected database. |
InvalidPropertyConfigurationException The required item of the client information property of the resource isn't specified. |
The required item of the client information property of the resource selected in Destination isn't specified. |
Specify the required item of the client information property of the resource. |
Limitations of JDBC category
Supported types vary by the database to connect and JDBC driver.
This connector reads and writes data in the common method of JDBC. Types that can't be read or written may exist according to the database to connect and JDBC driver.
Please contact the vendor of the database being used about information on supported types.
Specification limits
None.
Notes
-
A JDBC driver must be applied for HULFT Square. In HULFT Square, there are some restrictions regarding JDBC driver allocation, so the destinations that are currently available are restricted. The following JDBC drivers are allocated in the January 2023 release.
-
Snowflake
-
PostgreSQL
-
Amazon Redshift
-
Specification limits
-
Depending on the connected database, some functions might not be able to use.
-
If column names which need to be enclosed in double quotes are selected in Target of Schema definition, error will occur in operation execution.
However, this won't apply if all columns are selected.
Specification limits
-
Depending on the connected database, some functions might not be able to use.
Specification limits
-
Depending on the connected database, some functions might not be able to use.
-
If column names which need to be enclosed in double quotes are selected in Target or Key of Schema definition, error will occur in operation execution.
-
Can't get the key automatically.
To update a row that matches the key value, select true in the key of schema definition.
Specification limits
-
Depending on the connected database, some functions might not be able to use.
Specification limits
-
Depending on the connected database, some functions might not be able to use.
-
Parameters defined for stored procedures may not be retrieved correctly.
Specification Limits
-
Tables which include "." in the schema name or the table name on the database can't be used.
-
Test execution may be failed if the data amount is huge.
-
The maximum record count shown in the Execution result tab is 100.
-
SQL statements can be re-edited only if the tables in the SQL statement exist.
Specification Limits
-
When the connection resource is XAResource, testing can't be executed.
-
Tables which include "." in the schema name or the table name on the database can't be used.
-
SQL statements can be re-edited only if the tables in the SQL statement exist.
-
In connection resources for JDBC connector, when Execute transaction processing is not selected, rollback is not performed in test execution, and the data is updated.