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 |
|---|---|---|---|---|---|
| 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. |
| 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. |
| 2517 | Error | 0AW13 | -867L | "Cannot change synchronization user_name when status of the last upload is unknown" | 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. Click here for a list of possible parameters and odbc states. |
| 2518 | Error | WC001 | -868L | "'%1' is an unknown character set encoding label" | The specified character set label is not recognized, so conversion from/to that character set is not possible. Click here for a list of possible parameters and odbc states. |
| 2519 | Error | 08W64 | -869L | "Database server cannot convert data from/to character set '%1'" | 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. Click here for a list of possible parameters and odbc states. |
| 2520 | Error | WC002 | -870L | "Cannot convert between requested character set '%1' and database character set '%2'" | 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. Click here for a list of possible parameters and odbc states. |
| 2521 | Error | WJ029 | -871L | "The database needs to be restarted for this Java related command" | Java support in the database requires a database restart after some Java related commands are performed, for example, some Java commands like ALTER DATABASE UPGRADE JAVA ON require a restart before one performs any Java related commands that load a Java class into the database. Click here for a list of possible parameters and odbc states. |
| 2522 | Error | WP014 | -872L | "%1 does not return a result set" | A procedure called in the FROM clause of a SELECT statement must return a result set. Click here for a list of possible parameters and odbc states. |
| 2523 | Error | WP013 | -873L | "%1 returned multiple result sets" | A procedure called in the FROM clause of a SELECT statement cannot return multiple result sets. Click here for a list of possible parameters and odbc states. |
| 2524 | Error | WP015 | -686L | "Insufficient cache to start Java Virtual Machine" | Insufficient cache was available to start the Java Virtual Machine. Restart the database server with a larger cache size. Click here for a list of possible parameters and odbc states. |
| 2525 | Error | 55W13 | -688L | "Strongly-encrypted database files are not supported in the runtime server" | You attempted to start a strongly-encrypted database with the runtime server. Use the full server. Click here for a list of possible parameters and odbc states. |
| 2526 | Error | WX001 | -874L | "Column must be named: %1" | Unnamed columns cannot be used as XML element or attribute names. Name unnamed columns in the select list using AS. Click here for a list of possible parameters and odbc states. |
| 2527 | Error | 42W73 | -875L | "There is no way to join to '%1'" | 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. Click here for a list of possible parameters and odbc states. |