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

29009 HY109 Invalid cursor position
Cause: An attempt was made to perform a deleteRow() method or updateRow() method or cancelRowUpdates
method when the ResultSet row cursor was on the insert row. Or an attempt was made to perform the insertRow()
method when the ResultSet row cursor was not on the insert row.
Effect: The row changes and cursor manipulation do not succeed.
Recovery: To insert a row, move the cursor to the insert row. To delete, cancel, or update a row, move the cursor from
the insert row.
[back to the top]
29010 07009 Invalid column name
Cause: A column search does not contain columnName string.
Effect: The column comparison or searches do not succeed.
Recovery: Supply a valid columnName string to the findColum(), validateGetInvocation(), and
validateUpdInvocation() methods.
[back to the top]
29011 07009 Invalid column index or descriptor index
Cause: A ResultSet method was issued that has a column parameter that is outside of the valid range.
Effect: The ResultSet method data is not returned as expected.
Recovery: Make sure to validate the column that is supplied to the method.
[back to the top]
29012 07006 Restricted data type attribute violation
Cause: An attempt was made to execute a method either while an invalid data type was set or the data type did not
match the SQL column type.
Effect: The interface method is not executed.
Recovery: Make sure the correct method and Java data type is used for the column type.
[back to the top]
29013 HY024 Fetch size is less than 0
Cause: The size set for ResultSet.setFetchSize rows to fetch is less than zero.
Effect: The number of rows that need to be fetched from the database when more rows are needed for a ResultSet
object is not set.
Recovery: Set the setFetchSize() method rows parameter to a value greater than zero.
[back to the top]
29014 HY000 SQL data type not recognized
Cause: An unrecognized SQL data type was detected by JDBC.
Effect: An exception is thrown; data is not updated.
Recovery: Make sure that the SQL data type is supported by JDBC. The error is internal to the JDBC/MX driver.