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 |
|---|---|---|---|---|---|
| -681L | Error | 2308 | 52W24 | "Invalid join type used with Transact-SQL outer join" | An invalid join type was used with a query that contains Transact-SQL outer join comparison operators. Click here for a list of possible parameters and odbc states. |
| -682L | Error | 2309 | WO010 | "%1" | This message is used for displaying component integration services debug messages on the console. Click here for a list of possible parameters and odbc states. |
| -683L | Error | 2312 | WJ004 | "The cursor name '%1' already exists" | You attempted to declare a cursor with a name that already exists. Cursor names must be unique within a connection. Click here for a list of possible parameters and odbc states. |
| -684L | Error | 2313 | WW019 | "Rollback occurred due to deadlock during prefetch" | One of the cursors that was opened with prefetch enabled was performing fetch operations, and a deadlock occurred during a prefetch. This is a deadlock situation and your transaction has been chosen as the one to rollback. The request that received this error was not executed, unless the request was to close the cursor, in which case the cursor was closed. Click here for a list of possible parameters and odbc states. |
| -685L | Error | 2314 | WP009 | "Resource governor for '%1' exceeded" | The resource governor for the stated resource has determined that the usage of the resource has exceeded its limit. Click here for a list of possible parameters and odbc states. |
| -686L | Error | 2524 | WP015 | "Insufficient cache to start Java Virtual Machine" | Insufficient cache was available to start the Java Virtual Machine. Restart the database server with a larger cache size. Click here for a list of possible parameters and odbc states. |
| -687L | Error | 2072 | 42W48 | "Syntax error, cannot specify IQ specific options without specifying IQ PATH" | The database server cannot understand the statement you are trying to execute. If you used a keyword (such as DATE) for a column name, try enclosing the keyword in quotation marks ("DATE"). Click here for a list of possible parameters and odbc states. |
| -688L | Error | 2525 | 55W13 | "Strongly-encrypted database files are not supported in the runtime server" | You attempted to start a strongly-encrypted database with the runtime server. Use the full server. Click here for a list of possible parameters and odbc states. |
| -689L | Error | 2317 | WJ005 | "Input parameter index out of range" | The range for valid parameters is from 1 up to the number of host variables specified in the prepared/callable statement. Click here for a list of possible parameters and odbc states. |
| -690L | Error | 2318 | WJ006 | "Return value cannot be set" | Setting a value for the return parameter of a callable statement is not allowed. Click here for a list of possible parameters and odbc states. |
| -691L | Error | 2319 | 08W44 | "Could not load the backup/restore DLL \"%1\No message | An attempt to load the backup/restore DLL failed. Click here for a list of possible parameters and odbc states. |
| -692L | Error | 2320 | 08W45 | "Could not execute backup/restore DLL (%1) entry point" | An attempt to locate or execute the backup/restore DLL entry point failed. Click here for a list of possible parameters and odbc states. |
| -693L | Error | 2321 | WJ007 | "JDBC feature '%1' not supported" | An attempt was made to use a feature of JDBC that is not supported. Click here for a list of possible parameters and odbc states. |
| -694L | Error | 2322 | WJ008 | "Could not change an opened prepared statement or callable statement" | You attempted to change the SQL statement of an open prepared statement or callable statement. Prepared statements and callable statements must be closed before attempting such changes. Click here for a list of possible parameters and odbc states. |
| -695L | Error | 2323 | WJ009 | "An internal error occurred in a '%1'" | This is an internal JDBC object error. If it can be reproduced, it should be reported to iAnywhere. Click here for a list of possible parameters and odbc states. |
| -696L | Error | 2324 | WJ010 | "Invalid operation on a closed '%1'" | An illegal attempt was made to access a closed JDBC object. Click here for a list of possible parameters and odbc states. |
| -697L | Error | 2325 | 08W46 | "Error during backup/restore: %1" | An error occurred during a BACKUP or RESTORE statement. Click here for a list of possible parameters and odbc states. |
| -698L | Error | 2329 | WO011 | "The remote server does not support an auto-incrementing data type" | Auto-incrementing data types can only be supported in a proxy table when the remote server supports this feature. Click here for a list of possible parameters and odbc states. |
| -699L | Error | 2327 | WJ012 | "Cannot update member fields qualified with \"final\" modifier" | An attempt was made to modify a Java member that was qualified with the "final" modifier. Such members are constant and cannot be modified. Click here for a list of possible parameters and odbc states. |
| -700L | Error | 2328 | 07W04 | "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. |