Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 710 | "Invalid comparison" |
|---|---|
Constant | INVALID_COMPARISON |
SAP Sybase Error Number | 2338 |
SQL State | 52W25 |
SQL Code | -710L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 711 | "Incorrect database store DLL (%1) version" |
|---|---|
Constant | STORE_VERSION_MISMATCH |
SAP Sybase Error Number | 2340 |
SQL State | 08W47 |
SQL Code | -711L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the database store DLL. |
Probable Cause | The database store DLL and server DLL versions do not match. |
| Error 712 | "External login for server '%1' could not be found" |
|---|---|
Constant | OMNI_EXTLOGIN_NOT_FOUND |
SAP Sybase Error Number | 2339 |
SQL State | WO013 |
SQL Code | -712L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the remote server. |
Probable Cause | An external login for the server and user does not exist. |
| Error 715 | "Contents of backup files are inconsistent" |
|---|---|
Constant | RESTORE_INCONSISTENT |
SAP Sybase Error Number | 2344 |
SQL State | WB006 |
SQL Code | -715L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | During a RESTORE, the contents of a backup that was done to two or more disk or tape devices were found to be inconsistent. |
| Error 716 | "Backup file format is invalid" |
|---|---|
Constant | RESTORE_INVALID_FORMAT |
SAP Sybase Error Number | 2345 |
SQL State | WB007 |
SQL Code | -716L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The format of an archive file to be used during a RESTORE is invalid. |
| Error 717 | "RESTORE unable to open file '%1'" |
|---|---|
Constant | RESTORE_UNABLE_TO_OPEN |
SAP Sybase Error Number | 2346 |
SQL State | WB008 |
SQL Code | -717L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | File name of database file. |
Probable Cause | RESTORE was unable to open one of the database files. |
| Error 718 | "RESTORE unable to write to file '%1'" |
|---|---|
Constant | RESTORE_UNABLE_TO_WRITE |
SAP Sybase Error Number | 2347 |
SQL State | WB009 |
SQL Code | -718L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | File name of database file. |
Probable Cause | RESTORE was unable to write to one of the database files. |
| Error 719 | "RESTORE unable to start database '%1'" |
|---|---|
Constant | RESTORE_UNABLE_TO_START |
SAP Sybase Error Number | 2348 |
SQL State | WB010 |
SQL Code | -719L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | File name of database file. |
Probable Cause | After a RESTORE, the resulting database could not be started. |
| Error 720 | "VALIDATE statement must refer to a base table" |
|---|---|
Constant | CANNOT_VALIDATE_OBJECT |
SAP Sybase Error Number | 2349 |
SQL State | 42W51 |
SQL Code | -720L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | The VALIDATE statement must refer to a local base table; it cannot refer to a view, an SAP Sybase IQ table, or an object on a remote server. |
| Error 721 | "The data type specified for column '%1' is not compatible with the actual data type" |
|---|---|
Constant | OMNI_DATATYPE_MISMATCH |
SAP Sybase Error Number | 2354 |
SQL State | WO015 |
SQL Code | -721L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the column. |
Probable Cause | 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. |
| Error 722 | "The column '%1' does not exist in the remote table" |
|---|---|
Constant | OMNI_NOSUCH_COLUMN |
SAP Sybase Error Number | 2355 |
SQL State | WO016 |
SQL Code | -722L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the column. |
Probable Cause | The column specified in the CREATE EXISTING statement does not exist in the remote table. |
| Error 723 | "The length specified for column '%1' is different than the actual length" |
|---|---|
Constant | OMNI_LENGTH_MISMATCH |
SAP Sybase Error Number | 2356 |
SQL State | WO017 |
SQL Code | -723L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The name of the column. |
Probable Cause | The length of the column specified in the CREATE EXISTING statement is different than the length of the column in the remote table. |
| Error 724 | "NULL attribute mismatch for column '%1'" |
|---|---|
Constant | OMNI_NULL_MISMATCH |
SAP Sybase Error Number | 2357 |
SQL State | WO018 |
SQL Code | -724L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The name of the column. |
Probable Cause | The NULL attribute of the column specified in the CREATE EXISTING statement differs from the NULL attribute of the actual column. |
| Error 725 | "Identity attribute mismatch for column '%1'" |
|---|---|
Constant | OMNI_IDENTITY_MISMATCH |
SAP Sybase Error Number | 2358 |
SQL State | WO019 |
SQL Code | -725L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The name of the column. |
Probable Cause | The identity attribute of the column specified in the CREATE EXISTING statement differs from the identity attribute of the actual column. |
| Error 726 | "The table specification '%1' identifies more than one remote table" |
|---|---|
Constant | OMNI_RMT_TABLE_NOTUNIQUE |
SAP Sybase Error Number | 2359 |
SQL State | WO020 |
SQL Code | -726L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The complete name of the remote table. |
Probable Cause | More than one table was found on the remote server for the given table specification. Add a database or owner name to the specification. |
| Error 727 | "The optimizer was unable to construct a valid access plan" |
|---|---|
Constant | CANNOT_OPTIMIZE_QUERY |
SAP Sybase Error Number | 2362 |
SQL State | WI010 |
SQL Code | -727L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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 SAP Sybase. You may be able to work around this problem by modifying the query statement. |
| Error 728 | "Update operation attempted on non-updatable remote query" |
|---|---|
Constant | NON_UPDATEABLE_EXT_TAB |
SAP Sybase Error Number | 2372 |
SQL State | 42W35 |
SQL Code | -728L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 729 | "The specified foreign key (%1) cannot be enforced" |
|---|---|
Constant | UNENFORCEABLE_FOREIGN_KEY |
SAP Sybase Error Number | 2373 |
SQL State | 23507 |
SQL Code | -729L |
ODBC 2 State | 23000 |
ODBC 3 State | 23000 |
Severity Code | |
Parameter 1 | Name of the foreign key. |
Probable Cause | 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. |
| Error 730 | "Invalid JAR file" |
|---|---|
Constant | BAD_JAR_FILE |
SAP Sybase Error Number | 2374 |
SQL State | WP010 |
SQL Code | -730L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A file passed to the INSTALL JAVA statement was not a valid JAR file. |
| Error 731 | "Cannot drop a user that owns objects involved in replication" |
|---|---|
Constant | USER_OWNS_REPLICATED_OBJECTS |
SAP Sybase Error Number | 2377 |
SQL State | 55W06 |
SQL Code | -731L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |