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

29261 HY000 No error message in SQL/MX diagnostics area, but sqlcode is non-zero
Cause: An SQL error was detected but no error message was reported by SQL/MX.
Effect: An SQL exception or warning is thrown without a diagnostic message.
Recovery: Unknown.
[back to the top]
29262 HY090 Invalid or null sql string
Cause: A stored-procedure or prepared-statement call contains an invalid SQL string.
Effect: The stored procedure or prepared statement is not executed.
Recovery: Make sure that the stored procedure or prepared statement contains a valid SQL command.
[back to the top]
29263 HY000 Invalid or null statement label or name
Cause: A calling database stored a procedure or a prepared statement that has an invalid statement-label input
parameter.
Effect: The stored procedure or prepared statement is not executed.
Recovery: Make sure that the statement-label parameter is valid.
[back to the top]
29264 HY000 Invalid or null module name
Cause: A calling database stored a procedure or a prepared statement that has an invalid module-name input
parameter.
Effect: The stored procedure or prepared statement is not executed.
Recovery: Make sure that the module-name parameter is valid.
[back to the top]
29265 HY000 Unsupported character set encoding
Cause: The character-set type for a CHAR, VARCHAR, VARCHAR_LONG, or VARCHAR_WITH_LENGTH column is not supported
by the JDBC/MX driver setter or getter methods.
Effect: An SQL exception is thrown.
Recovery: Change the column character-set type to a type supported by the JDBC/MX driver.
[back to the top]
29266 HY000 Data type not supported : [data type]
Cause: An unsupported data type was retrieved from SQL.
Effect: An exception is thrown.
Recovery: None. BIT, BITVAR, BPINT_UNSIGNED, SQLTYPECODE_FLOAT, SQLTYPECODE_REAL, and
SQLTYPECODE_DOUBLE data types are not expected to be returned from SQL/MX. The JDBC/MX driver does not
support these data types.
[back to the top]