solidDB Help : solidDB reference : Error codes : solidDB SQL API (SSA) errors
  
solidDB SQL API (SSA) errors
The solidDB SQL API (SSA) error codes are described in the following table:
 
Error code
Class
Type
Description
25200
SSA
Error
Invalid application buffer type.
This error is used for the ODBC driver. It is given if signals attempt to use inappropriate buffer type for reading values (such as reading string to integer value). This error is documented into more detail in the ODBC specifications.
25201
SSA
Error
Invalid use of null pointer.
This error is given, if an invalid parameter - NULL is passed as a statement handle, connection handle, or application buffer.
25202
SSA
Error
Function sequence error.
This error is given, if an attempt to violate the ODBC function call sequence is made. This can happen, for example, when trying to execute a statement that has not been prepared.
25203
SSA
Error
Invalid transaction operation code.
This error is given, if an attempt to use an incorrect transaction completion code with the SQLEndTran function (SQL_COMMIT and SQL_ROLLBACK are allowed) is made.
25204
SSA
Error
Invalid string or buffer length.
This error is given, if 0 or any negative buffer size is passed to an ODBC function that requires an application buffer.
25205
SSA
Error
Invalid attribute/option identifier.
This error is given, if an invalid operation code is passed to the SQLSetPos, SQLDriverConnect, SQLFreeStmt and so on.
25206
SSA
Error
Connection timeout expired.
25207
SSA
Error
Invalid cursor state.
This error is given, for example, if an attempt is made to fetch with a closed cursor.
25208
SSA
Error
String data, right truncated.
This error is given if a string buffer was not big enough.
25209
SSA
Error
Datetime field overflow.
This error is given when updating a date or time column with incorrect data.
25210
SSA
Error
COUNT field incorrect.
This error is given, for example, when trying to pass an extra parameter to an insert statement.
25211
SSA
Error
Invalid descriptor index.
This error is given, for example, when using 0 or negative value as SQLBindParameter column index.
25212
SSA
Error
Client unable to establish a connection.
The ODBC client cannot connect to the server.
25213
SSA
Error
Connection name in use.
This error is given, for example, when trying to reconnect an already connected connection.
25214
SSA
Error
Connection does not exist.
This error is given, for example, when trying to use a closed or not connected connection.
25215
SSA
Error
Server rejected the connection.
Transport layer connection to the server has been established, but the server rejects the connection (for example, because it is shutting down).
25216
SSA
Error
Connection switch, some session context might be lost.
This error is specific to HotStandby configurations that use transparent connectivity (TF-1). A TF-1 connection has encountered a connection switch. The application must roll back the transaction to restore the connection.
25217
SSA
Error
Client unable to establish a primary connection.
This error is specific to HotStandby configurations that use transparent connectivity (TF-1). The ODBC driver has not been able to establish connection to the primary server, for example, after an application rolled back a transaction after a failover, or if there is no primary server address in the TF-1 connection string (all the reachable servers are secondary).
25404
SSA
Error
COUNT field incorrect.
25406
SSA
Error
Invalid descriptor index.
25411
SSA
Error
String data.
25416
SSA
Error
Datetime field overflow.
25418
SSA
Error
Invalid cursor state.
25424
SSA
Error
Invalid application buffer type.
25427
SSA
Error
Invalid use of null pointer.
25428
SSA
Error
Function sequence error.
25429
SSA
Error
Invalid transaction operation code.
25432
SSA
Error
Invalid string or buffer length.
25434
SSA
Error
Invalid attribute/option identifier.
25448
SSA
Error
Connection timeout expired.
Go up to
Error codes