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 |
|---|---|---|---|---|---|
| -701L | Error | 2326 | WJ011 | "Cannot access instance member through a class" | Non-static fields or methods must be accessed through an object instance. 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. |
| -710L | Error | 2338 | 52W25 | "Invalid comparison" | An attempt was made to compare two arguments that do not support comparison. For example, it is not valid to compare a Java object with another Java object, unless the class of the object supports a valid compareTo method. Click here for a list of possible parameters and odbc states. |
| -711L | Error | 2340 | 08W47 | "Incorrect database store DLL (%1) version" | The database store DLL and server DLL versions do not match. Click here for a list of possible parameters and odbc states. |
| -712L | Error | 2339 | WO013 | "External login for server '%1' could not be found" | An external login for the server and user does not exist. Click here for a list of possible parameters and odbc states. |
| -713L | Error | 2341 | WJ013 | "An internal error occurred in a '%1'" | This is an internal native Java object error. If it can be reproduced, it should be reported to iAnywhere. Click here for a list of possible parameters and odbc states. |
| -714L | Error | 2342 | WJ014 | "Invalid operation on a closed '%1'" | An illegal attempt was made to access a closed native Java object. Click here for a list of possible parameters and odbc states. |
| -715L | Error | 2344 | WB006 | "Contents of backup files are inconsistent" | During a RESTORE, the contents of a backup that was done to two or more disk or tape devices were found to be inconsistent. Click here for a list of possible parameters and odbc states. |
| -716L | Error | 2345 | WB007 | "Backup file format is invalid" | The format of an archive file to be used during a RESTORE is invalid. Click here for a list of possible parameters and odbc states. |
| -717L | Error | 2346 | WB008 | "RESTORE unable to open file '%1'" | RESTORE was unable to open one of the database files. Click here for a list of possible parameters and odbc states. |
| -718L | Error | 2347 | WB009 | "RESTORE unable to write to file '%1'" | RESTORE was unable to write to one of the database files. Click here for a list of possible parameters and odbc states. |
| -719L | Error | 2348 | WB010 | "RESTORE unable to start database '%1'" | After a RESTORE, the resulting database could not be started. Click here for a list of possible parameters and odbc states. |
| -720L | Error | 2349 | 42W51 | "VALIDATE statement must refer to a base table" | The VALIDATE statement must refer to a local base table; it cannot refer to a view, an IQ table, or an object on a remote server. Click here for a list of possible parameters and odbc states. |