Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 810 | "External object '%1' not found" |
|---|---|
Constant | EXTENV_OBJECT_NOT_FOUND |
SAP Sybase Error Number | 2457 |
SQL State | 42W57 |
SQL Code | -810L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the Java class or external object. |
Probable Cause | The Java class or external object with this name does not exist in the database. |
| Error 811 | "JAR '%1' not found" |
|---|---|
Constant | JAR_NOT_FOUND |
SAP Sybase Error Number | 2458 |
SQL State | 42W58 |
SQL Code | -811L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the JAR. |
Probable Cause | The JAR with this name does not exist in the database. |
| Error 812 | "The SELECT list for the derived table '%1' has no expression to match '%2'" |
|---|---|
Constant | NO_MATCHING_SELECT_ITEM |
SAP Sybase Error Number | 2459 |
SQL State | 42W59 |
SQL Code | -812L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the derived table. |
Parameter 2 | Name of the alias for which there is no matching expression. |
Probable Cause | The specified alias from the derived table's AS clause has no matching expression from the SELECT statement for that derived table. Ensure that each SELECT list item has a matching alias in the derived table's AS clause, and vice-versa. |
| Error 813 | "FOR UPDATE has been incorrectly specified for a READ ONLY cursor" |
|---|---|
Constant | NON_UPDATEABLE_CURSOR |
SAP Sybase Error Number | 2460 |
SQL State | 42W36 |
SQL Code | -813L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to declare a cursor FOR UPDATE on a query that is not updatable. Queries that contain DISTINCT, GROUP BY, HAVING, INTERSECT, EXCEPT, or UNION, or that contain aggregate functions are read-only. If the ansi_update_constraints option is on, then queries that contain a join are read-only. If the query references a view then the view may be non-updatable. |
| Error 814 | "Cannot update column '%1' since it appears in the ORDER BY clause" |
|---|---|
Constant | CANNOT_UPDATE_ORDER_BY_COLUMN |
SAP Sybase Error Number | 2461 |
SQL State | 42W37 |
SQL Code | -814L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the column that appears in the ORDER BY clause. |
Probable Cause | You attempted to update a column that appears in the ORDER BY clause. The ansi_update_constraints option controls whether this update is allowed. |
| Error 815 | "Cannot update column '%1' since it does not appear in the SELECT clause" |
|---|---|
Constant | UPDATE_NOT_IN_SELECT |
SAP Sybase Error Number | 2462 |
SQL State | 42W38 |
SQL Code | -815L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the column that does not appear in the SELECT clause. |
Probable Cause | You attempted to update a column that does not explicitly appear in the SELECT list. The ansi_update_constraints option controls whether this update is allowed. |
| Error 816 | "Specified database file already in use" |
|---|---|
Constant | FILE_IN_USE |
SAP Sybase Error Number | 2463 |
SQL State | 08W56 |
SQL Code | -816L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The database server could not start the specified database because the file is already in use. |
| Error 817 | "Too many temporary tables in connection" |
|---|---|
Constant | TOO_MANY_TEMP_TABLES |
SAP Sybase Error Number | 2464 |
SQL State | 52W41 |
SQL Code | -817L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A CREATE TABLE or DECLARE LOCAL TEMPORARY TABLE statement attempted to create a temporary table, but the resulting number of distinct table IDs used for temporary tables in the current connection would exceed the limit. |
| Error 818 | "Version 'V%1' interface used by external function call '%2' is not supported for execution in the current context." |
|---|---|
Constant | INCOMPATIBLE_EXTERNAL_CALL |
SAP Sybase Error Number | 2465 |
SQL State | WW026 |
SQL Code | -818L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | API version of the external function that is being called. |
Parameter 2 | Name of the external function that is being called. |
Probable Cause | You attempted to call an external function. The attempt to load the associated library failed because of incompatibility with the server. Incompatibility may arise because the dynamic library is using an external function API that is either not supported by the server or is newer than the one supported by the server. It may also arise if the external API is not compatible with the data in the current context. |
| Error 819 | "Table '%1' is part of a synchronization subscription and can only be ALTERed within a synchronization schema change" |
|---|---|
Constant | SYNC_CONTAINS_TABLE |
SAP Sybase Error Number | 2466 |
SQL State | 5RW35 |
SQL Code | -819L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | The name of the table. |
Probable Cause | A table belonging to a synchronization subscription cannot be altered except within a synchronization schema change or by using dbmlsync. |
| Error 820 | "Invalid scroll position '%1'" |
|---|---|
Constant | INVALID_POSITION |
SAP Sybase Error Number | 2467 |
SQL State | 24504 |
SQL Code | -820L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The scroll position that is invalid. |
Probable Cause | You attempted to scroll to a position that is not supported. Scroll positions must be between -2147483647 and 2147483646. |
| Error 821 | "Dbspace for table '%1' not found" |
|---|---|
Constant | DBSPACE_FOR_TABLE_UNAVAILABLE |
SAP Sybase Error Number | 2468 |
SQL State | 52W19 |
SQL Code | -821L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the table whose dbspace could not be found. |
Probable Cause | You tried to access a table in a dbspace that the database server could not find. You may need to change the file name associated with the dbspace using the ALTER DBSPACE statement. |
| Error 822 | "Table '%1' is already included" |
|---|---|
Constant | TABLE_ALREADY_INCLUDED |
SAP Sybase Error Number | 2469 |
SQL State | 5RW36 |
SQL Code | -822L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | The name of the table. |
Probable Cause | You attempted to add or modify a publication or synchronization definition such that the same table is included twice. |
| Error 823 | "Cannot handle expressions involving remote tables inside stored procedures" |
|---|---|
Constant | OMNI_EXPRESSION_IN_PROC |
SAP Sybase Error Number | 2470 |
SQL State | WO023 |
SQL Code | -823L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The server encountered an expression involving remote tables inside a stored procedure. The expression was too complicated to process. |
| Error 824 | "Illegal reference to correlation name '%1'" |
|---|---|
Constant | INVALID_CORRELATION_NAME_REFERENCE |
SAP Sybase Error Number | 2471 |
SQL State | 42U01 |
SQL Code | -824L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | The correlation name that is incorrectly referenced. |
Probable Cause | Your query contains a reference in a table expression to a correlation name that is not contained in that table expression. |
| Error 825 | "Previous error lost before RESIGNAL" |
|---|---|
Constant | PREVIOUS_ERROR_LOST |
SAP Sybase Error Number | 2472 |
SQL State | WP011 |
SQL Code | -825L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A RESIGNAL statement in an exception handler of a stored procedure was executed but the context of the previous error was unavailable. A possible cause of this error is a SELECT statement that returns a result set in the exception handler. |
| Error 826 | "Database upgrade not possible; RowGenerator table not owned by user dbo" |
|---|---|
Constant | DBO_DOES_NOT_OWN_ROWGENERATOR |
SAP Sybase Error Number | 2473 |
SQL State | 08W57 |
SQL Code | -826L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Probable Cause | An attempt to upgrade a database failed. The RowGenerator table is not owned by user dbo. |
| Error 827 | "Database upgrade not possible; user tables have table IDs in system table range" |
|---|---|
Constant | USER_TABLES_IN_SYSTEM_RANGE |
SAP Sybase Error Number | 2474 |
SQL State | 08W58 |
SQL Code | -827L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Probable Cause | An attempt to upgrade a database failed. User table IDs should not be in system table ID range. |
| Error 828 | "A conflict with the dbmlsync download phase was detected" |
|---|---|
Constant | RECORDING_CONFLICT_DETECTED |
SAP Sybase Error Number | 2475 |
SQL State | WW027 |
SQL Code | -828L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Dbmlsync uses this error to detect download phase conflicts with rows modified by other connections. |
| Error 829 | "TLS handshake failure" |
|---|---|
Constant | TLS_HANDSHAKE_FAILED |
SAP Sybase Error Number | 2476 |
SQL State | 08W59 |
SQL Code | -829L |
ODBC 2 State | 08S01 |
ODBC 3 State | 08S01 |
Severity Code | |
Probable Cause | The connection failed because of a failure in the TLS handshaking process. |