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 |
|---|---|---|---|---|---|
| -682L | Error | 2309 | WO010 | "%1" | This message is used for displaying component integration services debug messages in the messages window. 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 VM" | Insufficient cache was available to start the Java VM. 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. |
| -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. |
| -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. |
| -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. |
| -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. |
| -702L | Error | 2330 | 42W49 | "TRUNCATE TABLE statement cannot be used on a view" | You attempted to use TRUNCATE TABLE on a view, which is not permitted. Click here for a list of possible parameters and odbc states. |
| -703L | Error | 2331 | WW023 | "Cannot insert or update computed column '%1'" | Computed column values cannot be modified explicitly. Their value is determined implicitly from the computed expression value. Click here for a list of possible parameters and odbc states. |
| -704L | Error | 2332 | WW022 | "Cannot create an index on Java class '%1'" | An operation requiring an index was attempted in which an attempt was made to create an index on a Java class type. Click here for a list of possible parameters and odbc states. |
| -705L | Error | 2333 | 53019 | "Return type of void from procedure '%1' cannot be used in any expression" | The Java type void does not map onto any SQL type, hence a procedure returning void cannot be used in any SQL expression. Click here for a list of possible parameters and odbc states. |
| -706L | Error | 2334 | WO012 | "Remote server does not have the ability to support this statement" | You attempted to execute a statement that requires a capability that is not supported by a remote server. Click here for a list of possible parameters and odbc states. |
| -707L | Error | 2335 | 0AW05 | "Statement is not allowed in passthrough mode" | You tried to execute a statement that cannot be executed while in passthrough mode. For example, you may have executed a batch statement. Click here for a list of possible parameters and odbc states. |
| -708L | Error | 2336 | 42W50 | "READTEXT or WRITETEXT statement cannot refer to a view" | A Transact-SQL READTEXT or WRITETEXT statement cannot refer to text columns in a view. Replace the view reference with the name of a base table. Click here for a list of possible parameters and odbc states. |
| -709L | Error | 2337 | 0AW06 | "Computed columns are not supported in this database" | The current database is an older database and does not have catalog support for computed (materialized) columns. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |