JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2.1

Effect: The designated setter or updater method does not modify the ASCII or Binary or Character
stream.
Recovery: Informational message only; no corrective action is needed.
nl
29036 HY000 Unsupported encoding {0}
Cause: The character encoding is not supported.
Effect: An exception is thrown when the requested character encoding is not supported.
Recovery: ASCII (ISO88591), KANJI, KSC5601, and UCS2 are the only supported character
encodings. SQL/MP tables do not support UCS2 character encoding.
nl
29037 HY106 ResultSet type is TYPE_FORWARD_ONLY
Cause: An attempt was made to point a ResultSet cursor to a previous row when the object
type is set as TYPE_FORWARD_ONLY.
Effect: The ResultSet object cursor manipulation does not occur.
Recovery: TYPE_FORWARD_ONLY ResultSet object type cursors can move forward only.
TYPE_SCROLL_SENSITIVE and TYPE_SCROLL_INSENSITIVE types are scrollable.
nl
29038 HY107 Row number is not valid
Cause: A ResultSet absolute() method was called when the row number was set to 0.
Effect: The cursor is not moved to the specified row number.
Recovery: Supply a positive row number (specifying the row number counting from the beginning
of the result set), or supply a negative row number (specifying the row number counting from the
end of the result set).
nl
29039 HY092 Concurrency mode of the ResultSet is CONCUR_READ_ONLY
Cause: An action was attempted on a ResultSet object that cannot be updated because the
concurrency is set to CONCUR_READ_ONLY.
Effect: The ResultSet object is not modified.
Recovery: For updates, you must set the ResultSet object concurrency to CONCUR_UPDATABLE.
nl
29040 HY000 Operation invalid. Current row is the insert row
Cause: An attempt was made to retrieve update, delete, or insert information on the current insert
row.
Effect: The ResultSet row information retrieval does not succeed.
Recovery: To retrieve row information, move the ResultSet object cursor away from the insert
row.
nl
29041 HY000 Operation invalid. No primary key for the table
Cause: The getKeyColumns() method failed on a table that was created without a primary-key
column defined.
Effect: No primary-key data is returned for the table.
Recovery: Change the table to include a primary-key column.
nl
29042 HY000 Fetch size value is not valid
Cause: An attempt was made to set the fetch-row size to a value that is less than 0.
90 Messages