Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 660 | "Server '%1': %2" |
|---|---|
Constant | OMNI_REMOTE_ERROR |
SAP Sybase Error Number | 2286 |
SQL State | WO005 |
SQL Code | -660L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the remote server. |
Parameter 2 | The message from the remote server. |
Probable Cause | A message was generated by a remote server. The message text is included. |
| Error 661 | "Backward scrolling cursors are not supported for remote objects" |
|---|---|
Constant | OMNI_BACKWARDS_CURSOR |
SAP Sybase Error Number | 2287 |
SQL State | WO006 |
SQL Code | -661L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Backward scrolling cursors are not supported for remote objects. Use forward scrolling cursors only. |
| Error 662 | "Cannot serialize Java object with class '%1'" |
|---|---|
Constant | JAVA_SERIALIZATION_ERROR |
SAP Sybase Error Number | 2288 |
SQL State | WI009 |
SQL Code | -662L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The class of the value that cannot be serialized. |
Probable Cause | The Java object cannot be serialized as a persistent database column. |
| Error 663 | "Cannot deserialize Java object" |
|---|---|
Constant | JAVA_DESERIALIZATION_ERROR |
SAP Sybase Error Number | 2289 |
SQL State | WW018 |
SQL Code | -663L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The persistent Java object cannot be read from the database column. Possibly, the class of the object has been removed or modified. |
| Error 664 | "Database is active" |
|---|---|
Constant | DATABASE_ACTIVE |
SAP Sybase Error Number | 2290 |
SQL State | 08W40 |
SQL Code | -664L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The attempted operation (CREATE ENCRYPTED, CREATE DECRYPTED, ALTER DATABASE) cannot be performed while the database is running. Stop the database to perform the operation. |
| Error 665 | "Database \"%1\" needs recovery" |
|---|---|
Constant | DATABASE_NEEDS_RECOVERY |
SAP Sybase Error Number | 2291 |
SQL State | 08W41 |
SQL Code | -665L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The file name of the database that needs recovery. |
Probable Cause | The database quit abnormally the last time it was used. Database recovery must be performed before proceeding. |
| Error 666 | "The remote table '%1' could not be found" |
|---|---|
Constant | OMNI_RMT_TABLE_NOTFOUND |
SAP Sybase Error Number | 2292 |
SQL State | WO007 |
SQL Code | -666L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The complete name of the remote table. |
Probable Cause | The table could not be found on the remote server. Check the remote table name and the user privileges on that table. |
| Error 667 | "Could not access column information for the table '%1'" |
|---|---|
Constant | OMNI_RMT_COLUMNS_NOTFOUND |
SAP Sybase Error Number | 2293 |
SQL State | WO008 |
SQL Code | -667L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The complete name of the remote table. |
Probable Cause | Column information for the table could not be accessed. Check permissions for the table. |
| Error 668 | "Cursor is restricted to FETCH NEXT operations" |
|---|---|
Constant | NO_SCROLL_CURSOR |
SAP Sybase Error Number | 2294 |
SQL State | 09W06 |
SQL Code | -668L |
ODBC 2 State | S1106 |
ODBC 3 State | HY106 |
Severity Code | |
Probable Cause | An illegal FETCH operation has been detected for a NO SCROLL cursor. For a forward-only cursor the only permitted FETCH operations are FETCH RELATIVE 0 and FETCH NEXT (FETCH RELATIVE 1). |
| Error 669 | "Method '%1' cannot be called at this time" |
|---|---|
Constant | METHOD_CANNOT_BE_CALLED |
SAP Sybase Error Number | 2295 |
SQL State | WJ001 |
SQL Code | -669L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the method. |
Probable Cause | The method cannot be called at this time. Check that the method is not being called out of order. |
| Error 670 | "Invalid class byte code" |
|---|---|
Constant | BAD_CLASS_BYTE_CODE |
SAP Sybase Error Number | 2296 |
SQL State | WP005 |
SQL Code | -670L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A binary expression passed to the INSTALL JAVA statement was not a valid Java class. |
| Error 672 | "Database upgrade failed" |
|---|---|
Constant | DATABASE_UPGRADE_FAILED |
SAP Sybase Error Number | 2298 |
SQL State | 08W42 |
SQL Code | -672L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Probable Cause | Your attempt to upgrade a database failed. This could be caused by a failure to locate one of the SQL script files used to define the system table changes. |
| Error 673 | "Database upgrade not possible" |
|---|---|
Constant | DATABASE_UPGRADE_NOT_POSSIBLE |
SAP Sybase Error Number | 2299 |
SQL State | 08W43 |
SQL Code | -673L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Probable Cause | An attempt to upgrade a database failed. The database is too old to be upgraded. |
| Error 674 | "Statement's size limit is invalid" |
|---|---|
Constant | INVALID_CURSOR_RANGE |
SAP Sybase Error Number | 2300 |
SQL State | 09W07 |
SQL Code | -674L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | FIRST or TOP n are used in a SELECT statement to limit the size of a result. The size limit must be a constant integer greater than 0 and less than 32767. |
| Error 675 | "External environment could not be started, '%1' could not be found" |
|---|---|
Constant | EXTENV_NOT_STARTED |
SAP Sybase Error Number | 2301 |
SQL State | WP006 |
SQL Code | -675L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The component (executable or file) that could not be found and is needed to run the VM. |
Probable Cause | A problem was encountered starting the External Environment. A component that is needed to run the environment could not be found. |
| Error 676 | "The specified transaction isolation is invalid" |
|---|---|
Constant | INVALID_TRANSACTION_ISOLATION |
SAP Sybase Error Number | 2303 |
SQL State | WJ003 |
SQL Code | -676L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The specified transaction isolation is invalid. |
| Error 677 | "Table '%1' has a foreign key with a referential action" |
|---|---|
Constant | TABLE_HAS_REFACTION |
SAP Sybase Error Number | 2304 |
SQL State | 56001 |
SQL Code | -677L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the table with the referential action. |
Probable Cause | The table could not be renamed as it has a foreign key with a referential action. To rename the table, first drop the foreign key constraints. |
| Error 678 | "Index name '%1' is ambiguous" |
|---|---|
Constant | AMBIGUOUS_INDEX_NAME |
SAP Sybase Error Number | 2305 |
SQL State | 52W40 |
SQL Code | -678L |
ODBC 2 State | S0011 |
ODBC 3 State | 42S11 |
Severity Code | |
Parameter 1 | Name of the ambiguous index. |
Probable Cause | A statement has referred to an index name that is not unique. Preface the index name with the table and/or owner name. |
| Error 680 | "Invalid expression in WHERE clause of Transact-SQL outer join" |
|---|---|
Constant | INVALID_TSQL_OJ_EXPRESSION |
SAP Sybase Error Number | 2307 |
SQL State | 52W23 |
SQL Code | -680L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | An expression in the WHERE clause of a query that uses Transact-SQL syntax contains a comparison of a column from the NULL-supplying table with a subquery or an expression that references a column from another table. |
| Error 681 | "Invalid join type used with Transact-SQL outer join" |
|---|---|
Constant | INVALID_TSQL_JOIN_TYPE |
SAP Sybase Error Number | 2308 |
SQL State | 52W24 |
SQL Code | -681L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | An invalid join type was used with a query that contains Transact-SQL outer join comparison operators. |