JDBC Type 2 Driver 3.0 Programmer's Reference (SQL/MX 3.x)

[back to the top]
29047 HY000 Batch update failed. See next exception for details
Cause: One of the commands in a batch update failed to execute properly.
Effect: Not all the batch-update commands succeed. See the subsequent exception for more information.
Recovery: View the subsequent exception for possible recovery actions.
[back to the top]
29048 HY009 Invalid use of null
Cause: A parameter that has an expected table name is set to null.
Effect: The DatabaseMetadata method does not report any results.
Recovery: For the DatabaseMetaData method, supply a valid table name that is not null.
[back to the top]
29049 25000 Invalid transaction state
Cause: The begintransaction() method was called when a transaction was in progress.
Effect: A new transaction is not started.
Recovery: Before calling the begintransaction() method, validate whether other transactions are currently started.
[back to the top]
29050 HY107 Row value out of range
Cause: A call to getCurrentRow retrieved is outside the first and last row range.
Effect: The current row is not retrieved.
Recovery: It is an informational message only; no recovery is needed. Report the entire message to your service
provider.
[back to the top]
29051 01S02 ResultSet type changed to TYPE_SCROLL_INSENSITIVE
Cause: The Result Set Type was changed.
Effect: None.
Recovery: This message is reported as an SQL Warning. It is an informational message only; no recovery is needed.
[back to the top]
29052 22003 The Timestamp ({0}) is not in format yyyy-mm-dd hh:mm:ss.fffffffff for
column/parameter number {1,number,integer}
Cause: An attempt was made to enter an invalid timestamp format into a TIMESTAMP column type.
Effect: An exception is thrown; data is not updated.
Recovery: Make sure that a timestamp in the form of yyyy-mm-dd hh:mm:ss.fffffffff is used.
[back to the top]