Warning codes in the ranges +4200 to +4299, and +4450 to +4499, and error codes in the ranges -4200 to -4299, and -4450 to -4499 are reserved for the IBM® Data Server Driver for JDBC and SQLJ.
[jcc][t4][20128][12071][3.50.54] Invalid queryBlockSize specified: 1,048,576,012.
Using default query block size of 32,767. ERRORCODE=0, SQLSTATE=
The IBM Data Server Driver for JDBC and SQLJ issues the following warning codes:
Explanation: Tolerated errors include federated connection, authentication, and authorization errors. This warning applies only to connections to DB2® for Linux, UNIX, and Windows servers. It is issued only when a cursor operation, such as a ResultSet.next or ResultSet.previous call, returns false.
SQLSTATE: 02506
Explanation: A warning condition occurred during connection to the data source.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: A warning condition occurred during initialization.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: A warning condition occurred when data was sent to a server or received from a server.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: A warning condition occurred during customization or bind.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An warning condition occurred that does not fit in another category.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The specified value is not a valid option.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The specified value is invalid or out of range.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: A required value is missing.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because the target resource is closed.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because the target resource is in use.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because the target resource is unavailable.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because the target resource cannot be changed.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
The IBM Data Server Driver for JDBC and SQLJ issues the following error codes:
Explanation: An application that was in a global transaction in an XA environment issued a commit or rollback. A commit or rollback operation in a global transaction is invalid.
SQLSTATE: 2D521
Explanation: An application that was in a global transaction in an XA environment executed the setAutoCommit(true) statement. Issuing setAutoCommit(true) in a global transaction is invalid.
SQLSTATE: 2D521
Explanation: An error occurred on an XA connection during execution of an SQL statement.
For network optimization, the IBM Data Server Driver for JDBC and SQLJ delays some XA flows until the next SQL statement is executed. If an error occurs in a delayed XA flow, that error is reported as part of the SQLException that is thrown by the current SQL statement.
SQLSTATE: 57033
SQLSTATE: 57033
SQLSTATE: 57033
Explanation: Authorization failed.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
SQLSTATE: 28000
Explanation: An error occurred during character conversion.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An error occurred during encryption or decryption.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An error occurred during connection to the data source.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An error occurred during initialization.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An error occurred during resource cleanup.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An error occurred when data was sent to a server or received from a server.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An error occurred during customization or bind.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An error occurred during reset.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An error occurred that does not fit in another category.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: An error occurred during a batch execution.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
SQLSTATE: 0A504
Explanation: The specified value is not a valid option.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The specified value is invalid or out of range.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
SQLSTATE: 42815
Explanation: A required value is missing.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The specified value has a syntax error.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
SQLSTATE: 42601
Explanation: The requested operation cannot be performed because the target resource is closed.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because the target resource is in use.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because the target resource is unavailable.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because the target resource is no longer available.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because the target resource cannot be changed.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because access to the target resource is restricted.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
Explanation: The requested operation cannot be performed because the operation is not allowed on the target resource.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
For client reroute against DB2 for z/OS® servers, special register values that were set after the last commit point are not re-established.
The application is rolled back to the previous commit point. The connection state and global resources such as global temporary tables and open held cursors might not be maintained.
Explanation: A fatal error occurred that resulted in a disconnect from the data source. The existing connection has become unusable.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
SQLSTATE: 08001 or 58009
Explanation: See SQL30108N.
User response: Call SQLException.getMessage to retrieve specific information about the problem.
SQLSTATE: 08506