Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| 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. |
| Error 878 | "Index '%1' cannot be clustered" |
|---|---|
Constant | CLUSTERED_INDEX_NOT_ALLOWED |
SAP Sybase Error Number | 2535 |
SQL State | 42W74 |
SQL Code | -878L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the index that could not be made clustered. |
Probable Cause | You attempted to create a clustered index (including key indexes) but the new index cannot be created, for example, because the table already has a clustered index. |
| Error 879 | "An invalid multi-byte input character was encountered when converting from %1 to %2" |
|---|---|
Constant | ILLEGAL_MULTIBYTE_ERROR |
SAP Sybase Error Number | 2536 |
SQL State | WC003 |
SQL Code | -879L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The character set of the input string. |
Parameter 2 | The character set of the output string. |
Probable Cause | While the server was performing character set conversion on an input string, an invalid multi-byte character was encountered. The operation was aborted. |
| Error 881 | "Character substitution was required when converting from %1 to %2" |
|---|---|
Constant | SIMPLE_SUBSTITUTION_ERROR |
SAP Sybase Error Number | 2540 |
SQL State | WC005 |
SQL Code | -881L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The character set of the input string. |
Parameter 2 | The character set of the output string. |
Probable Cause | While the server was performing character set conversion on an input string, some characters could not be represented in the database character set. The operation was aborted. See on_charset_conversion_failure option. |
| Error 883 | "Character conversion error or warning report is not available when the single-byte converter is used" |
|---|---|
Constant | CHARACTER_CONVERSION_REPORT_NOT_AVAILABLE |
SAP Sybase Error Number | 2544 |
SQL State | WC007 |
SQL Code | -883L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to set the on_charset_conversion_failure option to produce either a warning or error report. This setting is not available when the single-byte to single-byte converter is used. |
| Error 887 | "Virtual index creation with more than %1 columns" |
|---|---|
Constant | TOO_MANY_VIRTUAL_INDEX_COLUMNS |
SAP Sybase Error Number | 2548 |
SQL State | 54W50 |
SQL Code | -887L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The maximum number of virtual index columns. |
Probable Cause | You attempted to create a virtual index with more than the maximum number of columns. |
| Error 888 | "XML parser error: %1" |
|---|---|
Constant | XML_PARSER_ERROR |
SAP Sybase Error Number | 2550 |
SQL State | WX002 |
SQL Code | -888L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The error message returned by the XML parser. |
Probable Cause | An XML instance will only parse correctly if it is well-formed as defined by the XML 1.0 specification. |
| Error 889 | "Statement contains an illegal usage of the non-deterministic function '%1'" |
|---|---|
Constant | NONDETERMINISTIC_FUNCTION |
SAP Sybase Error Number | 2551 |
SQL State | 42W79 |
SQL Code | -889L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The name of the non-deterministic user-defined function used in error. |
Probable Cause | Non-deterministic functions cannot appear in a CHECK constraint, or any other type of integrity constraint. They may appear anywhere within a query, view, or derived table. However, if an aliased SELECT list expression contains a non-deterministic function, that alias cannot be referred to elsewhere in the query. |
| Error 890 | "Statement size or complexity exceeds server limits" |
|---|---|
Constant | SYNTACTIC_LIMIT |
SAP Sybase Error Number | 2553 |
SQL State | 54W01 |
SQL Code | -890L |
ODBC 2 State | 37000 |
ODBC 3 State | 54000 |
Severity Code | |
Probable Cause | The statement contains one or more constructs whose size make it impossible to process. Increasing the maximum cache size, page size, or stack size may resolve this error. Consider rewriting the query so that the internal limit is not exceeded. For example, if the query contains a large IN-list, consider inserting the IN-list's values into a temporary table. Then rewrite the query to join this temporary table to the other table(s) in the original statement. |
| Error 891 | "Cannot convert between requested character sets '%1' and '%2'" |
|---|---|
Constant | FAILED_TO_START_CONVERTER_2_CHARSETS |
SAP Sybase Error Number | 2554 |
SQL State | WC008 |
SQL Code | -891L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the first requested character set encoding. |
Parameter 2 | The name of the second requested character set encoding. |
Probable Cause | The server is unable to convert between the two specified character sets. This could happen when the dbicu and dbicudt DLLs are not installed. |
| Error 892 | "XPath parser error: %1" |
|---|---|
Constant | XQUERY_PARSER_ERROR |
SAP Sybase Error Number | 2555 |
SQL State | WX003 |
SQL Code | -892L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The error message returned by the XPath parser. |
Probable Cause | The XPath expression is illegal or uses features that are not currently supported. |
| Error 893 | "Illegal flags value passed to OPENXML" |
|---|---|
Constant | BAD_OPENXML_FLAG |
SAP Sybase Error Number | 2556 |
SQL State | WX004 |
SQL Code | -893L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The flags value passed to OPENXML as the third argument must be either 1 (attribute-centric mapping), or 2 (element-centric mapping). |
| Error 894 | "Plan cannot be generated for this type of statement" |
|---|---|
Constant | STMT_NOT_ALLOWED_IN_PLAN |
SAP Sybase Error Number | 2557 |
SQL State | 0AW14 |
SQL Code | -894L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You tried to get the execution plan for a statement type that is not supported. |
| Error 895 | "Encryption error: %1" |
|---|---|
Constant | ENCRYPT_ERROR |
SAP Sybase Error Number | 2558 |
SQL State | 08W66 |
SQL Code | -895L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | Description of the error that occurred. |
Probable Cause | An error occurred during encryption. |
| Error 896 | "Cannot delete PUBLIC option '%1' since user settings exist" |
|---|---|
Constant | UNSET_PUBLIC_ID |
SAP Sybase Error Number | 2560 |
SQL State | 42W82 |
SQL Code | -896L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the option. |
Probable Cause | You tried to delete a PUBLIC option, but there are user settings for the same option. The user settings must be deleted before the PUBLIC option is deleted. |
| Error 897 | "Illegal tag value: '%1'" |
|---|---|
Constant | BAD_FOR_XML_EXPLICIT_TAG |
SAP Sybase Error Number | 2563 |
SQL State | WX005 |
SQL Code | -897L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The illegal tag value. |
Probable Cause | FOR XML EXPLICIT and FOR JSON EXPLICIT tag values must be greater than 0 and less than 256. NULL values are not allowed in the Tag column. |
| Error 898 | "Unknown FOR XML EXPLICIT directive: '%1'" |
|---|---|
Constant | BAD_FOR_XML_EXPLICIT_DIRECTIVE |
SAP Sybase Error Number | 2564 |
SQL State | WX006 |
SQL Code | -898L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The unknown directive. |
Probable Cause | Legal FOR XML EXPLICIT directives are: id, idref, idrefs, hide, element, xml, and cdata. Legal FOR JSON EXPLICIT directives are: hide, and element. |
| Error 899 | "Illegal column name: '%1'" |
|---|---|
Constant | BAD_FOR_XML_EXPLICIT_COLUMN_NAME |
SAP Sybase Error Number | 2565 |
SQL State | WX007 |
SQL Code | -899L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The reason the column name was illegal. |
Probable Cause | FOR XML EXPLICIT and FOR JSON EXPLICIT column names can consist of up to four fields separated by exclamation marks. The first two columns must be named Tag and Parent. |
| Error 900 | "Parent not open: '%1'" |
|---|---|
Constant | EXPLICIT_TAG_NOT_OPEN |
SAP Sybase Error Number | 2566 |
SQL State | WX008 |
SQL Code | -900L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The parent tag ID that is not among the open tags. |
Probable Cause | FOR XML EXPLICIT and FOR JSON EXPLICIT require the parent tag for a row to be opened when that row is read. Check the order of the rows returned by the query with the FOR XML EXPLICIT or FOR JSON EXPLICIT clause removed. |
| Error 901 | "Undeclared tag ID: '%1'" |
|---|---|
Constant | UNDECLARED_FOR_XML_EXPLICIT_TAG |
SAP Sybase Error Number | 2567 |
SQL State | WX009 |
SQL Code | -901L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The value of the undeclared tag ID. |
Probable Cause | Every value appearing in the Tag column of the table must be declared in the TagNumber field of at least one column name. |