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 |
|---|---|---|---|---|---|
| -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. |
| -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. |
| -721L | Error | 2354 | WO015 | "The data type specified for column '%1' is not compatible with the actual data type" | The data type of the column specified in the CREATE EXISTING statement is not compatible with the actual data type of the column in the remote table. Click here for a list of possible parameters and odbc states. |
| -722L | Error | 2355 | WO016 | "The column '%1' does not exist in the remote table" | The column specified in the CREATE EXISTING statement does not exist in the remote table. Click here for a list of possible parameters and odbc states. |
| -723L | Error | 2356 | WO017 | "The length specified for column '%1' is different than the actual length" | The length of the column specified in the CREATE EXISTING statement is different than the length of the column in the remote table. Click here for a list of possible parameters and odbc states. |
| -724L | Error | 2357 | WO018 | "NULL attribute mismatch for column '%1'" | The NULL attribute of the column specified in the CREATE EXISTING statement differs from the NULL attribute of the actual column. Click here for a list of possible parameters and odbc states. |
| -725L | Error | 2358 | WO019 | "Identity attribute mismatch for column '%1'" | The identity attribute of the column specified in the CREATE EXISTING statement differs from the identity attribute of the actual column. Click here for a list of possible parameters and odbc states. |
| -726L | Error | 2359 | WO020 | "The table specification '%1' identifies more than one remote table" | More than one table was found on the remote server for the given table specification. Add a database or owner name to the specification. Click here for a list of possible parameters and odbc states. |
| -727L | Error | 2362 | WI010 | "The optimizer was unable to construct a valid access plan" | The database server was unable to construct a valid access plan for the given request. This is a SQL Anywhere internal error. If it can be reproduced, it should be reported to iAnywhere. You may be able to work around this problem by modifying the query statement. Click here for a list of possible parameters and odbc states. |
| -728L | Error | 2372 | 42W35 | "Update operation attempted on non-updatable remote query" | You attempted an update or delete operation on a remote table that is currently not supported. Examples of such operations include positioned updates or deletes and updates or deletes that involve a join between local and proxy tables. Updates or deletes that involve a join between proxy tables on different remote servers will also give this error. Click here for a list of possible parameters and odbc states. |
| -729L | Error | 2373 | 23507 | "The specified foreign key (%1) cannot be enforced" | You attempted to create a foreign key that cannot be enforced. To be enforceable, the primary and foreign table for the specified key must exist on the same server. You can use the UNENFORCED keyword to create a foreign key specification that is not to be enforced. Click here for a list of possible parameters and odbc states. |
| -730L | Error | 2374 | WP010 | "Invalid JAR file" | A file passed to the INSTALL JAVA statement was not a valid JAR file. Click here for a list of possible parameters and odbc states. |
| -731L | Error | 2377 | 55W06 | "Cannot drop a user that owns objects involved in replication" | You attempted to drop a user that is the creator of a database object involved in replication. For example, the user may own a table that is part of a publication. Click here for a list of possible parameters and odbc states. |