5. Error Messages#
This chapter lists the SQL States of errors which can occur while using the Altibase JDBC driver.
SQL States#
The string value returned to SQLSTATE is composed of the first 2 characters which indicate the class and the following 3 characters which indicate the subclass. The class indicates the state and the subclass indicates the detailed state.
The following table lists the types of SQLSTATE which can occur in the Altibase JDBC driver and its meanings briefly.
| Condition | Class | Subcondition | Subclass |
|---|---|---|---|
| connection exception | 08 | ||
| Communication link failure | S01 | ||
| Invalid packet header version | P01 | ||
| Fail-Over completed | F01 | ||
| Invalid format for alternate servers | F02 | ||
| Invalid packet next header type | P02 | ||
| Invalid packet sequence number | P03 | ||
| Invalid packet serial number | P04 | ||
| Invalid packet module ID | P05 | ||
| Invalid packet module version | P06 | ||
| Invalid operation protocol | P07 | ||
| Invalid property id: %s | P08 | ||
| Invalid connection URL | U01 | ||
| Unknown host | H01 | ||
| There are no available data source configurations | D01 | ||
| connection failure | 006 | ||
| SQL-client unable to establish SQL-connection | 001 | ||
| Unsupported Algorithm | K01 | ||
| Could not create keystore instance | K02 | ||
| Could not load keystore | K03 | ||
| Invalid kestore url | K04 | ||
| Could not open keystore file | K05 | ||
| Key management exception occurred | K06 | ||
| Could not retreive key from keystore | K07 | ||
| Default algorithm definition invalid | K08 | ||
| Mandatory properties that are supported for the client version are not supported for the server version. | M01 | ||
| dynamic SQL error | 07 | This statement returns result set(s) | R01 |
| Invalid query string | Q01 | ||
| Statement has not been executed yet | S01 | ||
| no data | 02 | ||
| The sql statement does not produce a result set | 001 | ||
| warning | 01 | ||
| cursor operation conflict | 001 | ||
| Invalid connection string attribute | S00 | ||
| Batch update exception occurred: %s | B00 | ||
| There are no batch jobs | B01 | ||
| There are existing some batch jobs | B02 | ||
| The query cannot be executed while batch jobs are executing | B03 | ||
| Binding cannot be permitted during executing batch jobs | B04 | ||
| Fetch operation cannot be executed during batch update | B05 | ||
| There are too many added batch jobs | B31 | ||
| Statement has already been closed | C01 | ||
| The result set has already been closed | C02 | ||
| The stream has already been closed | C03 | ||
| additional result sets returned | 00D | ||
| This result set doesn't retain data | R01 | ||
| Attempt to return too many rows in only one fetch operation | R02 | ||
| Option value changed | S02 | ||
| Invalid value for bitset | V01 | ||
| feature not supported | 0A | 000 | |
| Cannot change the name of the database | C01 | ||
| The read only mode in transaction cannot be supported | C02 | ||
| Not supported operation on forward only mode | T01 | ||
| Not supported operation on read only mode | T02 | ||
| violate the JDBC specification | V01 | ||
| syntax error or access rule violation | 42 | Invalid type conversion | 001 |
| Column not found | S22 | ||
| JDBC internal error | JI | 000 | |
| Overflow occured on dynamic array which is defined by JDBC | D01 | ||
| Underflow occured on dynamic array which is defined by JDBC | D02 | ||
| This result set was created by JDBC driver's internal statement | D03 | ||
| Connection thread is interrupted | D04 | ||
| Remaining data exceeds the max size of the primitive type | D05 | ||
| Packet Operation has been twisted | P01 | ||
| Invalid method invocation | I01 | ||
| cardinality violation | 21 | Insert value list does not match column list | S01 |
| data exception | 22 | 000 | |
| null value not allowed | 004 | ||
| invalid parameter value | 023 | ||
| Insufficient number of parameters | P01 | ||
| IN type parameter needed | P02 | ||
| OUT type parameter needed | P03 | ||
| There is no column which needs to bind parameter. | P04 | ||
| Statement ID mismatch | V01 | ||
| Error occurred from InputStream | S01 | ||
| The length between actual lob data and written lob data into the communication buffer is different. | L01 | ||
| invalid transaction state | 25 | ||
| branch transaction already active | 002 | ||
| savepoint exception | 3B | ||
| Cannot set savepoint at auto-commit mode | S01 | ||
| Invalid savepoint name | V01 | ||
| Invalid savepoint | V02 | ||
| Not supported operation on named savepoint | N01 | ||
| Not supported operation on un-named savepoint | N02 | ||
| invalid schema name | 3F | 000 | |
| Explain Plan Error | EP | ||
| EXPLAIN PLAN is set to OFF | S01 | ||
| General Error | HY | ||
| There are too many allocated statements | 000 | ||
| Associated statement is not prepared | 007 | ||
| Attribute cannot be set now | 011 | ||
| Invalid string or buffer length | 090 | ||
| Invalid cursor position | 109 | ||
| Empty ResultSet | R01 | ||
| Timeout expired | T00 | ||
| XA error | XA | ||
| XA open failed | F01 | ||
| XA close failed | F02 | ||
| XA recover failed | F03 |