JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

29063 HY000 Transaction error {0} - {1} while obtaining start data locator
Cause: A transaction error occurred when the JDBC/MX driver attempted to reserve the data
locators for the given process while inserting or updating a LOB column.
Effect: The application cannot insert or update the LOB columns.
Recovery: Check the file-system error in the message and take recovery action accordingly.
nl
29064 22018 Java data type does not match SQL data type for column
Cause: Attempted to call a PreparedStatement setter method with an invalid column data type.
Effect: An exception is thrown; data is not updated.
Recovery: Make sure that the column data type is valid for the PreparedStatement setter
method.
nl
29065 22018 Java data type cannot be converted to the specified SQL data
type
Cause: A PreparedStatement setter method Java object conversion to the given SQL data type
is invalid.
Effect: An exception is thrown; data is not updated.
Recovery: Make sure that the column data type is valid for the PreparedStatement setter
method.
nl
29066 22018 The String data {0} cannot be converted to a numeric value
Cause: A PreparedStatement setter method could not convert a string to an integer.
Effect: An exception is thrown and the string data is not converted.
Recovery: Make sure that the data to be converted to an integer is valid.
nl
29067 07009 Invalid input value in the method {0}
Cause: One or more input values in the given method is invalid.
Effect: The given input method failed.
Recovery: Check the input values for the given method.
nl
29068 07009 The value for position can be any value between 1 and one
more than the length of the LOB data
Cause: The position input value in Blob.setBinaryStream, Clob.setCharacterStream,
or Clob.setAsciiStream can be between 1 and one more than the length of the LOB data.
Effect: The application cannot write the LOB data at the specified position.
Recovery: Correct the position input value.
nl
29069 HY000 Autocommit is on and LOB objects are involved
Cause: LOB data is involved with autocommit enabled and an external transaction does not exist.
Effect: An exception is reported; the LOB columns are not set.
Recovery: Start an external transaction or disable the autocommit mode when using the
Clob.setASciiStream(),Clob.setCharacterStream(), or Blob.setBinaryStream()
method.
nl
Messages From the Java Side of the JDBC/MX Driver 89