Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 831 | "Definition for alias '%1' must appear before its first reference" |
|---|---|
Constant | ALIAS_NOT_YET_DEFINED |
SAP Sybase Error Number | 2478 |
SQL State | 42W61 |
SQL Code | -831L |
ODBC 2 State | 37000 |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the alias. |
Probable Cause | An expression contains a reference to an alias, but the alias is defined later in the SELECT list. The alias definition must appear before its first reference. |
| Error 832 | "Connection error: %1" |
|---|---|
Constant | CONNECTION_ERROR |
SAP Sybase Error Number | 2479 |
SQL State | 08W60 |
SQL Code | -832L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | Description of the connection error. |
Probable Cause | An error occurred while attempting to establish a connection with the database server, but before attempting to connect to a database. Failure to initialize a communication link during the connection attempt is an example of this error. Creating a debug log file using the LogFile connection parameter may provide more information. |
| Error 833 | "Row in table '%1' was modified or deleted in BEFORE trigger" |
|---|---|
Constant | ROW_REMODIFIED_OR_DELETED |
SAP Sybase Error Number | 2480 |
SQL State | 42W62 |
SQL Code | -833L |
ODBC 2 State | 37000 |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the table. |
Probable Cause | A BEFORE trigger has updated or deleted the row that caused the trigger to fire, preventing the original operation from completing. The trigger must be re-written so that it does not attempt to change the row via UPDATE or DELETE statements. |
| Error 834 | "Column '%1' not found in table '%2'" |
|---|---|
Constant | COLUMN_NOT_FOUND_IN_TABLE |
SAP Sybase Error Number | 2083 |
SQL State | 52005 |
SQL Code | -834L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S22 |
Severity Code | |
Parameter 1 | Name of the column that could not be found. |
Parameter 2 | Name of the table that was supposed to contain the column. |
Probable Cause | You misspelled the name of a column, or the column you are looking for is in a different table. |
| Error 835 | "Event '%1' in use" |
|---|---|
Constant | EVENT_IN_USE |
SAP Sybase Error Number | 2482 |
SQL State | WE009 |
SQL Code | -835L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the event that is in use. |
Probable Cause | You have attempted to drop an event that is currently in use. |
| Error 836 | "Procedure '%1' is no longer valid" |
|---|---|
Constant | PROCEDURE_NO_LONGER_VALID |
SAP Sybase Error Number | 2483 |
SQL State | 42W63 |
SQL Code | -836L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the procedure. |
Probable Cause | A procedure definition cannot be loaded from the catalog. Check for tables or columns that have been renamed or that may be reserved words. If this procedure is an internal procedure, you may have an older version. Database upgrade may be needed to run it successfully. |
| Error 837 | "Trigger or foreign key for table '%1' is no longer valid" |
|---|---|
Constant | TRIGGER_NO_LONGER_VALID |
SAP Sybase Error Number | 2484 |
SQL State | 42W64 |
SQL Code | -837L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the table. |
Probable Cause | A trigger definition cannot be loaded from the catalog. Check for tables or columns that have been renamed or that may be reserved words. The trigger may be a system-generated trigger to enforce the referential actions of a foreign key. |
| Error 838 | "TLS initialization on server failed" |
|---|---|
Constant | TLS_INIT_FAILED_ON_SRV |
SAP Sybase Error Number | 2485 |
SQL State | 08W61 |
SQL Code | -838L |
ODBC 2 State | 08S01 |
ODBC 3 State | 08S01 |
Severity Code | |
Probable Cause | The connection failed because the initialization of the TLS library on the server failed. |
| Error 839 | "Download failed because of conflicts with existing rows" |
|---|---|
Constant | DOWNLOAD_CONFLICT |
SAP Sybase Error Number | 2486 |
SQL State | 0AW11 |
SQL Code | -839L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | During synchronization, there was a conflict between one or more rows in the download stream and rows modified locally in the UltraLite database. The download has been rolled back. You can avoid this error by coordinating local database modifications with synchronization, or synchronizing again when the local modifications are complete. |
| Error 840 | "Incorrect or missing encryption key" |
|---|---|
Constant | BAD_ENCRYPTION_KEY |
SAP Sybase Error Number | 2487 |
SQL State | 08W62 |
SQL Code | -840L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The database is encrypted with a key. There was no key given to start the database, or the specified key was incorrect. |
| Error 843 | "Cannot find synchronization user with the name '%1'" |
|---|---|
Constant | SYNC_SITE_NOT_FOUND |
SAP Sybase Error Number | 2490 |
SQL State | 5RW37 |
SQL Code | -843L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the synchronization user. |
Probable Cause | You misspelled the name of a synchronization site or you did not qualify it correctly with a user name. |
| Error 845 | "Owner '%1' used in a qualified column reference does not match correlation name '%2'" |
|---|---|
Constant | INVALID_COLUMN_QUALIFICATION |
SAP Sybase Error Number | 2492 |
SQL State | 42U02 |
SQL Code | -845L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | The owner name specified in the column reference. |
Parameter 2 | The correlation name that is incorrectly referenced. |
Probable Cause | Your query contains a qualified column reference to a table name, but either a correlation name has been used for that table, or the owner of the table does not match the owner name specified in the column reference. Remove the owner qualification, and qualify column references only by correlation name. |
| Error 846 | "SET clause for column '%1' used incorrectly" |
|---|---|
Constant | INVALID_SET_CLAUSE |
SAP Sybase Error Number | 2493 |
SQL State | 42U03 |
SQL Code | -846L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S03 |
Severity Code | |
Parameter 1 | The SET clause that is invalid. |
Probable Cause | Your UPDATE statement contains an invalid SET clause, for example, there are multiple SET clauses for the same column. |
| Error 849 | "Referential integrity actions other than RESTRICT not allowed for temporary tables" |
|---|---|
Constant | INVALID_FOREIGN_KEY_ACTION |
SAP Sybase Error Number | 2496 |
SQL State | 42R01 |
SQL Code | -849L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to specify an unsupported referential integrity action for a temporary table. |
| Error 850 | "Tables related by key constraint must both be permanent, or both be temporary and not created with ON COMMIT DELETE ROWS. For global temporary tables they must both be shared if one is shared." |
|---|---|
Constant | INVALID_FOREIGN_KEY_TABLE |
SAP Sybase Error Number | 2497 |
SQL State | 42R02 |
SQL Code | -850L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | Tables involved in a key constraint relationship must both be permanent user tables or both be temporary tables not created with ON COMMIT DELETE ROWS. Change the definition of one or both tables using ALTER TABLE. |
| Error 851 | "Decryption error: %1" |
|---|---|
Constant | DECRYPT_ERROR |
SAP Sybase Error Number | 2498 |
SQL State | 08W63 |
SQL Code | -851L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | Description of the error that occurred. |
Probable Cause | An error occurred during decryption. |
| Error 852 | "Table name '%1' is ambiguous" |
|---|---|
Constant | AMBIGUOUS_TABLE_NAME |
SAP Sybase Error Number | 2499 |
SQL State | 52W42 |
SQL Code | -852L |
ODBC 2 State | S0013 |
ODBC 3 State | 42S13 |
Severity Code | |
Parameter 1 | Name of an ambiguous table. |
Probable Cause | A statement has referred to a table name that is not unique. Preface the table name by an owner name. |
| Error 853 | "Cursor not in a valid state" |
|---|---|
Constant | CURSOR_INVALID_STATE |
SAP Sybase Error Number | 2501 |
SQL State | 24000 |
SQL Code | -853L |
ODBC 2 State | 24000 |
ODBC 3 State | 24000 |
Severity Code | |
Probable Cause | You attempted to use a cursor that is not in a valid state for the attempted operation. For example, the cursor may have encountered an error. In UltraLite, this error occurs if you attempt to set parameters for a prepared statement while a result set (cursor) is open for the statement. |
| Error 854 | "Function or column reference to '%1' in the ORDER BY clause is invalid" |
|---|---|
Constant | INVALID_ORDERBY_COLUMN |
SAP Sybase Error Number | 2502 |
SQL State | 42W65 |
SQL Code | -854L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the column referenced directly, or in an expression, in the ORDER BY clause. |
Probable Cause | You specified a function or column reference in the ORDER BY clause that is semantically invalid. For example, for DISTINCT queries the ORDER BY clause may only refer to items in the query's SELECT list. |
| Error 855 | "Trigger name '%1' is ambiguous" |
|---|---|
Constant | AMBIGUOUS_TRIGGER_NAME |
SAP Sybase Error Number | 2503 |
SQL State | 42W66 |
SQL Code | -855L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the ambiguous trigger. |
Probable Cause | A statement has referred to a trigger name that is not unique. Qualify the trigger name with the table and/or owner name. |