JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.1 (H06.23+, J06.12+)

29071 HY000 Internal programming error - {0}
Cause: The JNI layer (get Object method) always returns a byte array and, therefore, any other instance is considered
a programming error.
Effect: An exception is reported.
Recovery: None. The error is internal to the JDBC/MX driver.
[back to the top]
29072 HY000 Attempting to exceed the maximum connection pool size ({0,number,integer})
Cause: An attempt was made to obtain a connection outside the set connection pool size limit.
Effect: An exception is thrown.
Recovery: Increase the connection pool size by using the maxPoolSize command-line property.
[back to the top]
29073 22003 The Time ({0}) is not in format hh:mm:ss for column/parameter number
{1,number,integer}
Cause: An attempt was made to enter an invalid time format into a TIME column type.
Effect: An exception is thrown; data is not updated.
Recovery: Make sure that a time in the form of hh:mm:ss is used.
[back to the top]
29074 42821 The getter method, {0}, cannot be used to retrieve data for column/parameter
number
{1,number,integer}
Cause: Attempted to use an unsupported column type in the ResultSet.getString method.
Effect: An exception is reported; no data is obtained.
Recovery: Use a supported column data type other than BLOB, ARRAY, REF, STRUCT, DATALINK, or JAVA_OBJECT with the
ResultSet.getString method.
[back to the top]
29075 HY000 'transactionMode' property is set to a null value or set to an invalid value
Cause: Called SQLMXDataSource.setTransactionMode() or
SQLMXConnectionPoolDataSource.setTransactionMode() using an invalid transaction mode.
Effect: The application cannot set the transaction mode.
Recovery: Use a valid transaction mode: external, internal, or mixed.
[back to the top]
29076 HY000 Exceeded 'maxStatements' ({0,number,integer}) -- performance may be
compromised
Cause: The cached statement count has reached the limit set by the maxStatements property and all statements are in
use.