Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| -742L | Error | 2388 | WJ015 | "JDBC SAStatement batch execute abandoned" | An error occurred when executing a statement in the batch. The rest of the statements in the batch will be abandoned. Click here for a list of possible parameters and odbc states. |
| -743L | Error | 2389 | WJ016 | "Seek absolute 0 was attempted on a JDBC SAResultSet" | There is no row zero on JDBC resultSets. The valid row numbers are 1, 2, ..., -2, -1. Click here for a list of possible parameters and odbc states. |
| -744L | Error | 2390 | 08W51 | "Invalid IQ database command line option or parameter value: %1" | An invalid command line option was used. The option began with -iq, but is either invalid or contained a bad parameter. Click here for a list of possible parameters and odbc states. |
| -745L | Error | 2391 | 08W52 | "Cannot initialize IQ memory manager: %1" | System V shared memory was requested but could not be allocated. Click here for a list of possible parameters and odbc states. |
| -746L | Error | 2392 | 08W53 | "Cannot allocate System V resources" | IQ was unable to allocate System V resources. Delete unused System V semaphores and shared memory segments or increase operating system configuration values for these resources. Click here for a list of possible parameters and odbc states. |
| -747L | Error | 2393 | WJ017 | "Invalid JDBC resultset type" | An invalid resultset type was used when creating a JDBC statement. Click here for a list of possible parameters and odbc states. |
| -748L | Error | 2394 | WJ018 | "Invalid JDBC resultset concurrency" | An invalid resultset concurrency was used when creating a JDBC statement. Click here for a list of possible parameters and odbc states. |
| -749L | Error | 2395 | 0AW07 | "Feature not available with UltraLite" | You attempted to execute a statement or use a feature that is not supported in an UltraLite database. Click here for a list of possible parameters and odbc states. |
| -750L | Error | 2396 | 42W55 | "User owns procedures in use" | You attempted to drop a user that owns a procedure being used by other active users of the database. Click here for a list of possible parameters and odbc states. |
| -751L | Error | 2397 | 42W56 | "User owns tables in use" | You attempted to REVOKE CONNECT from a user that owns a table being used by other active users of the database. Click here for a list of possible parameters and odbc states. |
| -752L | Error | 2398 | WJ019 | "Cannot call the '%1' function on a JDBC resultset when it is positioned on an insert row" | Some resultset functions such as updateRow and deleteRow are invalid when the cursor of the resultset is positioned at the insert row. Click here for a list of possible parameters and odbc states. |
| -753L | Error | 2399 | WJ020 | "The JDBC resultset must be positioned on an insert row in order to use the '%1' function" | Resultset functions such as insertRow can only be called when the resultset is positioned on the insert row. Click here for a list of possible parameters and odbc states. |
| -754L | Error | 2400 | 08W54 | "Parse error: %1" | An invalid data source name was used in the connection string. Click here for a list of possible parameters and odbc states. |
| -755L | Error | 2401 | 0AW08 | "You cannot synchronize or upgrade with uncommitted transactions" | You attempted to synchronize or upgrade the schema of an UltraLite database and there are changes in the UltraLite database that have not been committed. Click here for a list of possible parameters and odbc states. |
| -756L | Error | 2402 | WJ021 | "Cannot uniquely identify column '%2' of table '%1' in the current JDBC resultset" | Failed to identify a column in a JDBC resultset with the given table name and column name. This can happen if the given names are not found or if they are ambiguous. Click here for a list of possible parameters and odbc states. |
| -757L | Error | 2404 | 55W08 | "Modifications not permitted for read-only database" | You attempted an update operation on a database that was declared as read-only. Click here for a list of possible parameters and odbc states. |
| -758L | Error | 2405 | WJ022 | "The database does not support the Java Virtual Machine" | The Java Virtual Machine could not be started because the database does not have the proper support. It may be that the database was created with an older version of the software, or was created with the Java support disabled. If the database was created with an older version of the software the database should be upgraded to the most recent version. If the database was created with Java support disabled, then the instjava.sql script should be run against the database to enable Java support. Click here for a list of possible parameters and odbc states. |
| -759L | Error | 2406 | 07W05 | "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. |
| -760L | Error | 2407 | 07W06 | "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. |
| -761L | Error | 2343 | WO014 | "Server capability name '%1' could not be found in the database." | An ALTER SERVER statement was attempted on a capability that was not defined. Click here for a list of possible parameters and odbc states. |