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

29003 HY000 Statement does not exist
Cause: A validation attempt was made on the getter or exec invocation on a closed statement.
Effect: The getter or exec invocation validation fails.
Recovery: Issue validateGetInvocation() or validateExecDirectInvocation when the statement is open.
[back to the top]
29004 HY024 Invalid transaction isolation value
Cause: An attempt was made to set the transaction isolation level to an invalid value.
Effect: SQLMXConnection.setTransactionIsolation does not set the transaction isolation value.
Recovery: Valid isolation values are: SQL_TXN_READ_COMMITTED, SQL_TXN_READ_UNCOMMITTED,
SQL_TXN_REPEATABLE_READ, and SQL_TXN_SERIALIZABLE.
If no isolation value is specified, the default is SQL_TXN_READ_COMMITTED.
[back to the top]
29005 HY024 Invalid ResultSet type
Cause: An attempt was made to set an invalid ResultSet Type value.
Effect: The SQLMXStatement call with the resultSetType parameter fails.
Recovery: Valid ResultSet types are: TYPE_FORWARD_ONLY, TYPE_SCROLL_INSENSITIVE, and
TYPE_SCROLL_SENSITIVE.
[back to the top]
29006 HY000 Invalid Result Set concurrency
Cause: An attempt was made to set an invalid result-set concurrency value.
Effect: The SQLMXStatement call with resultSetConcurrency fails.
Recovery: Valid resultSetConcurrency values are: CONCUR_READ_ONLY and CONCUR_UPDATABLE.
[back to the top]
29007 07009 Invalid descriptor index
Cause: A ResultSetMetadata column parameter or a ParameterMetaData param parameter is outside of the
descriptor range.
Effect: The ResultSetMetadata or ParameterMetaData method data is not returned as expected.
Recovery: Validate the column or parameter that is supplied to the method.
[back to the top]
29008 24000 Invalid cursor state
Cause: The ResultSet method was called when the connection was closed.
Effect: The method call does not succeed.
Recovery: Make sure the connection is open before making the ResultSet method call.
[back to the top]