Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2497 | Error | 42R02 | -850L | "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." | 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. Click here for a list of possible parameters and odbc states. |
| 2498 | Error | 08W63 | -851L | "Decryption error: %1" | An error occurred during decryption. Click here for a list of possible parameters and odbc states. |
| 2499 | Error | 52W42 | -852L | "Table name '%1' is ambiguous" | A statement has referred to a table name that is not unique. Preface the table name by an owner name. Click here for a list of possible parameters and odbc states. |
| 2500 | Warning | 01S02 | 121L | "Cursor option values changed" | The database server could not support the requested cursor option values for the associated query. Similar option settings were substituted. Click here for a list of possible parameters and odbc states. |
| 2501 | Error | 24000 | -853L | "Cursor not in a valid state" | 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. Click here for a list of possible parameters and odbc states. |
| 2502 | Error | 42W65 | -854L | "Function or column reference to '%1' in the ORDER BY clause is invalid" | 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. Click here for a list of possible parameters and odbc states. |
| 2503 | Error | 42W66 | -855L | "Trigger name '%1' is ambiguous" | A statement has referred to a trigger name that is not unique. Qualify the trigger name with the table and/or owner name. Click here for a list of possible parameters and odbc states. |
| 2504 | Error | 07W08 | -856L | "Invalid sqllen field in SQLDA" | An invalid length was specified in a SQLDA sqllen field. All variable length types must have a non-negative length. The DT_BINARY and DT_VARCHAR types must have length greater than one. Click here for a list of possible parameters and odbc states. |
| 2505 | Error | 0AW12 | -857L | "Synchronization failed due to an error on the server: %1" | Synchronization failed at the server. More details can be found in the synchronization log file. Click here for a list of possible parameters and odbc states. |
| 2506 | Error | 42W67 | -858L | "CREATE/DROP STATISTICS statement cannot refer to virtual tables" | You attempted to use CREATE/DROP STATISTICS to create/drop one or more histograms on a virtual database object, such as a view or remote table. The CREATE STATISTICS and DROP STATISTICS statements can only refer to base tables, local temporary tables, or global temporary tables in the SQL Anywhere database that you are connected to. Click here for a list of possible parameters and odbc states. |
| 2507 | Error | WQ006 | -1523L | "Cannot reassign logical server '%1' to login policy '%2'." | Logical Server - Login Policy assignment already exists. Click here for a list of possible parameters and odbc states. |
| 2508 | Error | WQ007 | -1524L | "Cannot drop a non-existing assignment between logical server '%1' and login policy '%2'." | Logical Server - Login Policy assignment does not exist. Click here for a list of possible parameters and odbc states. |
| 2509 | Error | WW028 | -860L | "At least one of the specified dbspaces was not calibrated" | You attempted to calibrate a dbspace that was not open or was too small. Click here for a list of possible parameters and odbc states. |
| 2510 | Error | 42W68 | -861L | "Aggregated expression '%1' contains multiple columns of which one or more are outer references" | A subselect within the nested query contains an aggregate function whose parameters include an outer reference. In such cases, the outer reference must be the only column referenced in the expression. Click here for a list of possible parameters and odbc states. |
| 2511 | Error | 42W69 | -862L | "The aggregate expression '%1' must appear in either the SELECT list or a HAVING clause subquery" | An aggregated expression containing an outer reference must either appear in a SELECT list expression (a subselect), or in a HAVING clause subquery in the query whose FROM clause contains the table with the column being aggregated. Click here for a list of possible parameters and odbc states. |
| 2512 | Error | 42W70 | -863L | "Grouped query contains more than one distinct aggregate function" | Two or more DISTINCT aggregate functions were specified in the same grouped query. This is only permitted if the Hash Group By operator is available. Any query block can only contain at most one DISTINCT aggregate function if the Hash Group By operator is not available. Click here for a list of possible parameters and odbc states. |
| 2513 | Error | 40W05 | -303L | "Disk write failure '%1' -- transaction rolled back" | A disk write failed. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| 2514 | Error | 42W71 | -864L | "Statement contains an illegal usage of the NUMBER(*) function" | The NUMBER and IDENTITY functions can only appear in the SELECT list of the outer-most SELECT block. It cannot be used in any subquery or in a predicate. Click here for a list of possible parameters and odbc states. |
| 2515 | Error | 42R03 | -865L | "Key constraint between temporary tables requires a primary key (not unique constraint)" | The key constraint between temporary tables requires a primary key (not a UNIQUE constraint) if the database uses combined indexes. Change the definition of the primary table using ALTER TABLE or rebuild the database. Click here for a list of possible parameters and odbc states. |
| 2516 | Error | WP012 | -866L | "%1 returned a result set with a different schema than expected" | When calling a procedure in the FROM clause of a SELECT statement, the expected schema of the result is taken from the WITH clause. If no WITH clause is given, the expected schema is taken from the system catalog. The result set returned from the call must match the expected schema or it must be possible to convert every column so that it matches. Click here for a list of possible parameters and odbc states. |