Messages and limitations of the DB2 connector
Message code list of DB2 category
The following message codes correspond to errors that occur in DB2 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
-
com.ibm.db2.jcc.b.SqlException, etc.
Exception messages of DB2 category
|
Exception name |
Cause |
Solution |
|
|---|---|---|---|
|
InputDataNotFoundException |
Input data isn't specified. |
Specify Input data or draw data flow. |
|
|
InvalidPropertyConfigurationException <Property name> is not specified. |
<Property name> isn't specified. |
Specify <property name>. |
|
|
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. |
|
|
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. |
|
|
com.ibm.db2.jcc.am.SqlNonTransientConnectionException |
Required property "<Host name>" is unclear. ERRORCODE=-4222, SQLSTATE=08001 |
Can't connect to the database. |
Check Host name of the connection resource. |
|
com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException |
Exception java.net.ConnectException: Error occurred upon opening sockets to Server /<Host name>. Port: <Port number> Message: Connection refused: connect ERRORCODE=-4499, SQLSTATE=08001 |
Check Port number of the connection resource. |
|
|
com.ibm.db2.jcc.am.DisconnectNonTransientException |
For the disperse protocol error causing release of allocating conversation, the execution failed. DRDA Data stream syntactic error was detected. Reason: 0x3. ERRORCODE=-4499, SQLSTATE=58009 |
Check the environment of the destination. |
|
|
com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException |
The application server rejected establishment of the connection. An attempt was made to access a database, <Database name>, which was either not found or does not support transactions. ERRORCODE=-4499, SQLSTATE=08004 |
You may be specifying database that doesn't exist. |
Specify an existing database in Database name of the connection resource. |
|
While operating on the socket, socket input stream, or socket output stream that become the base of connection, communication error occurred. Location of error: Reply.fill() - socketInputStream.read (-1). Message: Software caused connection abort: recv failed. ERRORCODE=-4499, SQLSTATE=08001 |
|||
|
com.ibm.db2.jcc.am.SqlInvalidAuthorizationSpecException |
Connection authorization failure occurred. Reason: user ID or password is invalid. ERRORCODE=-4214, SQLSTATE=28000 |
The user name or the password is incorrect. |
Check User name or Password of the connection resource. |
|
com.ibm.db2.jcc.am.SqlSyntaxErrorException |
DB2 SQL Error: SQLCODE=-104, SQLSTATE=42601, SQLERRMC=<Table name>, DRIVER=4.21.29 |
Spaces may have been inserted into the specified table name. |
When spaces are inserted into the table name specified in Table name, enclose it with quotation marks. |
|
DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=<Table name>, DRIVER=4.21.29 |
The table doesn't exist. |
Specify an existing table in Table name. |
|
Limitations of DB2 category
This connector supports the following types.
|
Type name |
Support |
Remarks |
|---|---|---|
|
SMALLINT |
Yes |
|
|
BIGINT |
Yes |
|
|
REAL |
Yes |
|
|
DOUBLE |
Yes |
|
|
DECIMAL |
Yes |
|
|
DATE |
Yes |
|
|
TIME |
Yes |
|
|
TIMESTAMP |
Yes |
|
|
CHAR |
Yes |
|
|
CHAR FOR BIT DATA |
Limited |
|
|
VARCHAR |
Yes |
|
|
VARCHAR FOR BIT DATA |
Limited |
|
|
LONG VARCHAR FOR BIT DATA |
Limited |
|
|
CLOB |
Yes |
|
|
BLOB |
Limited |
|
|
GRAPHIC |
Yes |
|
|
VARGRAPHIC |
Yes |
|
|
LONGVARGRAPHIC |
Limited |
|
|
DBCLOB |
Limited |
|
|
XML |
Limited |
Data is handled as String. |
-
Yes: Supported.
-
Limited: Supported with limitations.
-
No: Not supported.
Specification limits
-
When the table name is enclosed with quotation marks, it's case-sensitive.
Specification limits
-
None.
Specification limits
-
CHAR
-
The default code page when creating a database is "UTF-8". Therefore, depending on the character, string length may be longer, and the result may change from former operation.
-
-
When the table name is enclosed with quotation marks, it's case-sensitive.
Specification limits
-
CHAR
-
The default code page when creating a database is "UTF-8". Therefore, depending on the character, string length may be longer, and the result may change from former operation.
-
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.