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 |
|---|---|---|---|---|---|
| 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 statement identifier generated by a PREPARE passed to the database for a further operation is invalid. 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. |
| 08W03 | Error | 2038 | -102L | "Database server connection limit exceeded" | You exceeded the number of computers allowed to connect to the server. If you are running the network database server, the limit is spelled out in your license agreement. The server may be running low on cache such that it cannot accept any more database connections. The personal database server is restricted to 10 connections. Click here for a list of possible parameters and odbc states. |
| 08W04 | Error | 2035 | -99L | "Connections to database have been disabled" | Connections to the network database server have been disabled. You will receive this error until connections have been enabled. Click here for a list of possible parameters and odbc states. |
| 08W05 | Error | 2043 | -106L | "Cannot open transaction log file -- %1" | The database server was unable to open the named transaction log file. The log file name may include an invalid device or directory. If this is the case, you can use the Transaction Log utility (dblog) to find out where the transaction log should be and perhaps change it. Click here for a list of possible parameters and odbc states. |
| 08W06 | Error | 2046 | -109L | "There are still active database connections" | You attempted to shut down a database that still has active connections. Click here for a list of possible parameters and odbc states. |