Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 682 | "%1" |
|---|---|
Constant | OMNI_DEBUG |
SAP Sybase Error Number | 2309 |
SQL State | WO010 |
SQL Code | -682L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The debug message for the console. |
Probable Cause | This message is used for displaying component integration services debug messages in the messages window. |
| Error 683 | "The cursor name '%1' already exists" |
|---|---|
Constant | DUPLICATE_CURSOR_NAME |
SAP Sybase Error Number | 2312 |
SQL State | WJ004 |
SQL Code | -683L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the cursor. |
Probable Cause | You attempted to declare a cursor with a name that already exists. Cursor names must be unique within a connection. |
| Error 684 | "Rollback occurred due to deadlock during prefetch" |
|---|---|
Constant | ROLLBACK_ON_PREFETCH |
SAP Sybase Error Number | 2313 |
SQL State | WW019 |
SQL Code | -684L |
ODBC 2 State | 40001 |
ODBC 3 State | 40001 |
Severity Code | |
Probable Cause | 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. |
| Error 685 | "Resource governor for '%1' exceeded" |
|---|---|
Constant | RESOURCE_GOVERNOR_EXCEEDED |
SAP Sybase Error Number | 2314 |
SQL State | WP009 |
SQL Code | -685L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The resource whose limit has been exceeded. |
Probable Cause | The resource governor for the stated resource has determined that the usage of the resource has exceeded its limit. |
| Error 686 | "Insufficient cache to start Java VM" |
|---|---|
Constant | JAVA_VM_INSUFFICIENT_CACHE |
SAP Sybase Error Number | 2524 |
SQL State | WP015 |
SQL Code | -686L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Insufficient cache was available to start the Java VM. Restart the database server with a larger cache size. |
| Error 687 | "Syntax error, cannot specify SAP Sybase IQ specific options without specifying IQ PATH" |
|---|---|
Constant | IQ_PATH_SYNTAX_ERROR |
SAP Sybase Error Number | 2072 |
SQL State | 42W48 |
SQL Code | -687L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | The IQ PATH clause must be specified when one or more options specified in the CREATE DATABASE statement are SAP Sybase IQ specific. |
| Error 689 | "Input parameter index out of range" |
|---|---|
Constant | BAD_PARAM_INDEX |
SAP Sybase Error Number | 2317 |
SQL State | WJ005 |
SQL Code | -689L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The range for valid parameters is from 1 up to the number of host variables specified in the prepared/callable statement. |
| Error 691 | "Could not load the backup/restore DLL \"%1\No message |
|---|---|
Constant | BACKUP_NOT_LOADED |
SAP Sybase Error Number | 2319 |
SQL State | 08W44 |
SQL Code | -691L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the DLL that could not be loaded. |
Probable Cause | An attempt to load the backup/restore DLL failed. |
| Error 692 | "Could not execute backup/restore DLL (%1) entry point" |
|---|---|
Constant | BACKUP_ENTRY_NOT_FOUND |
SAP Sybase Error Number | 2320 |
SQL State | 08W45 |
SQL Code | -692L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the entry point that could not be found. |
Probable Cause | An attempt to locate or execute the backup/restore DLL entry point failed. |
| Error 697 | "Error during backup/restore: %1" |
|---|---|
Constant | BACKUP_ERROR |
SAP Sybase Error Number | 2325 |
SQL State | 08W46 |
SQL Code | -697L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | A message describing the error that occurred. |
Probable Cause | An error occurred during a BACKUP or RESTORE statement. |
| Error 698 | "The remote server does not support an auto-incrementing data type" |
|---|---|
Constant | OMNI_AUTOINC_NOT_SUPPORTED |
SAP Sybase Error Number | 2329 |
SQL State | WO011 |
SQL Code | -698L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Auto-incrementing data types can only be supported in a proxy table when the remote server supports this feature. |
| Error 700 | "SQLDA fields inconsistent for a multi-row SQLDA" |
|---|---|
Constant | SQLDA_INCONSISTENT |
SAP Sybase Error Number | 2328 |
SQL State | 07W04 |
SQL Code | -700L |
ODBC 2 State | 07001 |
ODBC 3 State | 07W04 |
Severity Code | |
Probable Cause | 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. |
| Error 702 | "TRUNCATE TABLE statement cannot be used on a view" |
|---|---|
Constant | CANNOT_TRUNCATE_VIEW |
SAP Sybase Error Number | 2330 |
SQL State | 42W49 |
SQL Code | -702L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to use TRUNCATE TABLE on a view, which is not permitted. |
| Error 703 | "Cannot insert or update computed column '%1'" |
|---|---|
Constant | COMPUTED_COLUMN_WRITE_ATTEMPTED |
SAP Sybase Error Number | 2331 |
SQL State | WW023 |
SQL Code | -703L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the column. |
Probable Cause | Computed column values cannot be modified explicitly. Their value is determined implicitly from the computed expression value. |
| Error 704 | "Cannot create an index on Java class '%1'" |
|---|---|
Constant | CANNOT_INDEX_ON_JAVA_CLASS |
SAP Sybase Error Number | 2332 |
SQL State | WW022 |
SQL Code | -704L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the class. |
Probable Cause | An operation requiring an index was attempted in which an attempt was made to create an index on a Java class type. |
| Error 705 | "Return type of void from procedure '%1' cannot be used in any expression" |
|---|---|
Constant | PROCEDURE_RETURNS_VOID |
SAP Sybase Error Number | 2333 |
SQL State | 53019 |
SQL Code | -705L |
ODBC 2 State | 07006 |
ODBC 3 State | 07006 |
Severity Code | |
Parameter 1 | Name of the procedure. |
Probable Cause | The Java type void does not map onto any SQL type, hence a procedure returning void cannot be used in any SQL expression. |
| Error 706 | "Remote server does not have the ability to support this statement" |
|---|---|
Constant | OMNI_SERVER_NOT_CAPABLE |
SAP Sybase Error Number | 2334 |
SQL State | WO012 |
SQL Code | -706L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to execute a statement that requires a capability that is not supported by a remote server. |
| Error 707 | "Statement is not allowed in passthrough mode" |
|---|---|
Constant | STMT_NOT_ALLOWED_IN_PASSTHROUGH |
SAP Sybase Error Number | 2335 |
SQL State | 0AW05 |
SQL Code | -707L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You tried to execute a statement that cannot be executed while in passthrough mode. For example, you may have executed a batch statement. |
| Error 708 | "READTEXT or WRITETEXT statement cannot refer to a view" |
|---|---|
Constant | TEXT_OPERATION_ON_VIEW |
SAP Sybase Error Number | 2336 |
SQL State | 42W50 |
SQL Code | -708L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 709 | "Computed columns are not supported in this database" |
|---|---|
Constant | COMPUTED_COLUMNS_NOT_SUPPORTED |
SAP Sybase Error Number | 2337 |
SQL State | 0AW06 |
SQL Code | -709L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |