Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 856 | "Invalid sqllen field in SQLDA" |
|---|---|
Constant | INVALID_SQLLEN |
SAP Sybase Error Number | 2504 |
SQL State | 07W08 |
SQL Code | -856L |
ODBC 2 State | HY090 |
ODBC 3 State | HY090 |
Severity Code | |
Probable Cause | 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. |
| Error 857 | "Synchronization failed due to an error on the server: %1" |
|---|---|
Constant | SERVER_SYNCHRONIZATION_ERROR |
SAP Sybase Error Number | 2505 |
SQL State | 0AW12 |
SQL Code | -857L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The description of the error from the server. |
Probable Cause | Synchronization failed at the server. More details can be found in the synchronization log file. |
| Error 858 | "CREATE/DROP STATISTICS statement cannot refer to virtual tables" |
|---|---|
Constant | HISTOGRAMS_NOT_SUPPORTED_ON_OBJECT |
SAP Sybase Error Number | 2506 |
SQL State | 42W67 |
SQL Code | -858L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 860 | "At least one of the specified dbspaces was not calibrated" |
|---|---|
Constant | DBSPACE_NOT_CALIBRATED |
SAP Sybase Error Number | 2509 |
SQL State | WW028 |
SQL Code | -860L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to calibrate a dbspace that was not open or was too small. |
| Error 861 | "Aggregated expression '%1' contains multiple columns of which one or more are outer references" |
|---|---|
Constant | MULTIPLE_AGGREGATE_COLUMNS |
SAP Sybase Error Number | 2510 |
SQL State | 42W68 |
SQL Code | -861L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The aggregated expression in error. |
Probable Cause | 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. |
| Error 862 | "The aggregate expression '%1' must appear in either the SELECT list or a HAVING clause subquery" |
|---|---|
Constant | INVALID_AGGREGATE_PLACEMENT |
SAP Sybase Error Number | 2511 |
SQL State | 42W69 |
SQL Code | -862L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The aggregated expression in error. |
Probable Cause | 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. |
| Error 863 | "Grouped query contains more than one distinct aggregate function" |
|---|---|
Constant | INVALID_DISTINCT_AGGREGATE |
SAP Sybase Error Number | 2512 |
SQL State | 42W70 |
SQL Code | -863L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 864 | "Statement contains an illegal usage of the NUMBER(*) function" |
|---|---|
Constant | INVALID_NUMBER |
SAP Sybase Error Number | 2514 |
SQL State | 42W71 |
SQL Code | -864L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 865 | "Key constraint between temporary tables requires a primary key (not unique constraint)" |
|---|---|
Constant | INVALID_FOREIGN_KEY_INDEX |
SAP Sybase Error Number | 2515 |
SQL State | 42R03 |
SQL Code | -865L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 866 | "%1 returned a result set with a different schema than expected" |
|---|---|
Constant | BAD_RESULT_SET |
SAP Sybase Error Number | 2516 |
SQL State | WP012 |
SQL Code | -866L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the procedure that returned the incorrect result set. |
Probable Cause | 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. |
| Error 867 | "Cannot change synchronization user_name when status of the last upload is unknown" |
|---|---|
Constant | CANNOT_CHANGE_USER_NAME |
SAP Sybase Error Number | 2517 |
SQL State | 0AW13 |
SQL Code | -867L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | The MobiLink server uses the user_name to track synchronizations. If the status of the previous upload is unknown then you must resolve this condition before changing the user. |
| Error 868 | "'%1' is an unknown character set encoding label" |
|---|---|
Constant | UNKNOWN_CHARSET |
SAP Sybase Error Number | 2518 |
SQL State | WC001 |
SQL Code | -868L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The character set encoding label that is not recognized. |
Probable Cause | The specified character set label is not recognized, so conversion from/to that character set is not possible. |
| Error 869 | "Database server cannot convert data from/to character set '%1'" |
|---|---|
Constant | UNSUPPORTED_CHARACTER_SET_ERROR |
SAP Sybase Error Number | 2519 |
SQL State | 08W64 |
SQL Code | -869L |
ODBC 2 State | 08S01 |
ODBC 3 State | 08S01 |
Severity Code | |
Parameter 1 | Name of the requested character set. |
Probable Cause | The database server cannot convert character data from/to the character set requested by the application because the character set is not supported. The connection fails. |
| Error 870 | "Cannot convert between requested character set '%1' and database character set '%2'" |
|---|---|
Constant | FAILED_TO_START_CONVERTER |
SAP Sybase Error Number | 2520 |
SQL State | WC002 |
SQL Code | -870L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the requested character set encoding. |
Parameter 2 | The name of the database character set encoding. |
Probable Cause | The server is unable to convert between the connection character set that was specified and the database character set. This could happen when the dbicu and dbicudt DLLs are not installed. |
| Error 872 | "%1 does not return a result set" |
|---|---|
Constant | NO_RESULT_SET |
SAP Sybase Error Number | 2522 |
SQL State | WP014 |
SQL Code | -872L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the procedure. |
Probable Cause | A procedure called in the FROM clause of a SELECT statement must return a result set. |
| Error 873 | "%1 returned multiple result sets" |
|---|---|
Constant | TOO_MANY_RESULT_SETS |
SAP Sybase Error Number | 2523 |
SQL State | WP013 |
SQL Code | -873L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the procedure. |
Probable Cause | A procedure called in the FROM clause of a SELECT statement cannot return multiple result sets. |
| Error 874 | "Column must be named: %1" |
|---|---|
Constant | NO_XML_IDENTIFIER |
SAP Sybase Error Number | 2526 |
SQL State | WX001 |
SQL Code | -874L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The number of the column that must be named. |
Probable Cause | Unnamed columns cannot be used as XML element or attribute names. Unnamed JSON columns can only be used within the top-level SELECT where the tag and parent are defined. In this context, the unnamed column is a directive to generate a JSON value rather than a JSON object for the given column. Name unnamed columns in the SELECT list by using AS. |
| Error 875 | "There is no way to join to '%1'" |
|---|---|
Constant | CANNOT_JOIN_TABEXPR |
SAP Sybase Error Number | 2527 |
SQL State | 42W73 |
SQL Code | -875L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of table or view that cannot be joined. |
Probable Cause | The server cannot discover a valid join condition involving this table. If the join is an outer join, you may be missing an ON clause. If the join is a KEY JOIN, the server cannot discover a foreign key-primary key relationship with this table that can be used to generate the join condition. If the join is a NATURAL JOIN, the table has no common column names with the table expression it is being joined to. |
| Error 876 | "Client out of memory" |
|---|---|
Constant | CLIENT_OUT_OF_MEMORY |
SAP Sybase Error Number | 2528 |
SQL State | 08W65 |
SQL Code | -876L |
ODBC 2 State | S1001 |
ODBC 3 State | HY001 |
Severity Code | |
Probable Cause | A failure occurred when the database client was trying to allocate memory. |
| Error 877 | "SETUSER not allowed in procedures, triggers, events, or batches" |
|---|---|
Constant | SETUSER_NOT_IN_PROCEDURES |
SAP Sybase Error Number | 2534 |
SQL State | 42W09 |
SQL Code | -877L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The SETUSER statement is not allowed in stored procedures, triggers, event handlers, or batches, and cannot be called from an EXECUTE IMMEDIATE statement. |