Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 04W08 | Error | 2214 | -605L | "The server attempted to access a page beyond the end of the maximum allowable dbspace file size" | The database attempted to access a page whose page number is beyond the maximum possible number of disk pages. This is a fatal internal error. Click here for a list of possible parameters and odbc states. |
| 07001 | Error | 2119 | -188L | "Not enough values for host variables" | You have not provided enough host variables for either the number of bind variables, or the statement, or the number of SELECT list items. Click here for a list of possible parameters and odbc states. |
| 07002 | Error | 2114 | -182L | "Not enough fields allocated in SQLDA" | There are not enough fields in the SQLDA to retrieve all of the values requested. Click here for a list of possible parameters and odbc states. |
| 07003 | Error | 2110 | -171L | "Error opening cursor" | You attempted to open a cursor on a statement that is not SELECT, CALL or EXEC. Click here for a list of possible parameters and odbc states. |
| 07005 | Error | 2107 | -160L | "Can only describe a SELECT statement" | In the C language interface, you attempted to describe the SELECT list of a statement other than a SELECT statement. In UltraLite this error can result from trying to retrieve the schema of any statement other than a SELECT. Click here for a list of possible parameters and odbc states. |
| 07009 | Error | 2246 | -640L | "Invalid descriptor index" | The index number used with respect to a descriptor area is out of range. Click here for a list of possible parameters and odbc states. |
| 07W01 | Error | 2108 | -161L | "Invalid type on DESCRIBE statement" | A Java type specified on a DESCRIBE statement has no corresponding SQL type. Click here for a list of possible parameters and odbc states. |
| 07W02 | Error | 2070 | -130L | "Invalid statement" | The prepared statement is invalid. In embedded SQL, an OPEN or EXECUTE failed. Click here for a list of possible parameters and odbc states. |
| 07W03 | Error | 2074 | -133L | "Invalid prepared statement type" | This is an internal error. If it can be reproduced, it should be reported to iAnywhere. Click here for a list of possible parameters and odbc states. |
| 07W04 | Error | 2328 | -700L | "SQLDA fields inconsistent for a multi-row SQLDA" | Not all of the rows in a multi-row SQLDA have been defined identically for an array operation (insert, fetch, or execute). A given column must be defined the same (type and length) in each row. Click here for a list of possible parameters and odbc states. |
| 07W05 | Error | 2406 | -759L | "SQLDA data type invalid" | The data type specified for a SQLDA variable is invalid. Click here for a list of possible parameters and odbc states. |
| 07W06 | Error | 2407 | -760L | "Invalid SQL identifier" | An invalid identifier was supplied through the C language interface. For example, you may have supplied a NULL string for a cursor name. Click here for a list of possible parameters and odbc states. |
| 07W07 | Error | 2454 | -807L | "Host variables must not be used within a batch" | You have attempted to execute a batch that contains host variable references. Host variables are not supported within a batch. Click here for a list of possible parameters and odbc states. |
| 07W08 | Error | 2504 | -856L | "Invalid sqllen field in SQLDA" | An invalid length was specified in a SQLDA sqllen field. All variable length types must have a non-negative length. The DT_BINARY and DT_VARCHAR types must have length greater than one. Click here for a list of possible parameters and odbc states. |
| 08001 | Error | 2042 | -105L | "Database cannot be started -- %1" | The specified database cannot be started. Either it does not exist, it is not a database, it is corrupt, or it is an older, unsupported format. Click here for a list of possible parameters and odbc states. |
| 08003 | Error | 2037 | -101L | "Not connected to a database" | You are not connected to a database, or you executed the DISCONNECT statement and have not connected to a database again. Click here for a list of possible parameters and odbc states. |
| 08004 | Error | 2080 | -140L | "User ID '%1' does not exist" | You used a user ID that does not exist. Click here for a list of possible parameters and odbc states. |
| 08005 | Error | 2627 | -963L | "Password contains an illegal character" | The specified password contains an illegal character. Click here for a list of possible parameters and odbc states. |
| 08W01 | Error | 2036 | -100L | "Database server not found" | The database server is not running, or is in the process of starting up or shutting down, or the interface library is unable to find it. Click here for a list of possible parameters and odbc states. |
| 08W02 | Error | 2045 | -108L | "Connection not found" | The specified connection name on a DISCONNECT or SET CONNECTION statement is invalid. Click here for a list of possible parameters and odbc states. |