Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
Error 902 | "Too few columns" |
---|---|
Constant | FOR_XML_EXPLICIT_TOO_FEW_COLUMNS |
SAP Sybase Error Number | 2568 |
SQL State | WX010 |
SQL Code | -902L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | FOR XML EXPLICIT and FOR JSON EXPLICIT require at least three columns: the tag column, the parent column, and one or more data columns. |
Error 903 | "CDATA has a name" |
---|---|
Constant | FOR_XML_EXPLICIT_NAMED_CDATA |
SAP Sybase Error Number | 2569 |
SQL State | WX011 |
SQL Code | -903L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A CDATA directive in a FOR XML EXPLICIT query must not be given a name. |
Error 904 | "Illegal ORDER BY in aggregate function" |
---|---|
Constant | INVALID_ORDERBY_IN_AGGREGATE |
SAP Sybase Error Number | 2570 |
SQL State | 42W90 |
SQL Code | -904L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | An ORDER BY can be used in an aggregate function only if there are no DISTINCT aggregates in the SELECT list, or there is a single DISTINCT aggregate with the DISTINCT column equal to the first column of the ORDER BY. Also, multiple ordered aggregates cannot be used in the same SELECT list unless they have the exact same ORDER BY clause. |
Error 905 | "Invalid XQuery constructor" |
---|---|
Constant | INVALID_XQUERY_CONSTRUCTOR |
SAP Sybase Error Number | 2571 |
SQL State | WX012 |
SQL Code | -905L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The XQuery constructor passed as the first argument to XMLGEN was not valid. |
Error 906 | "XMLGEN evaluation failure" |
---|---|
Constant | XMLGEN_EVALUATION_FAILURE |
SAP Sybase Error Number | 2572 |
SQL State | WX013 |
SQL Code | -906L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | One of the variables referenced in the XQuery constructor was not found in the list of arguments. |
Error 907 | "No name for argument" |
---|---|
Constant | NO_SQLX_ARGUMENT_NAME |
SAP Sybase Error Number | 2573 |
SQL State | WX014 |
SQL Code | -907L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Unnamed arguments cannot be used as XML element or attribute names. Name unnamed items in the argument list using AS. |
Error 908 | "Invalid operation on a closed object" |
---|---|
Constant | ULTRALITE_OBJ_CLOSED |
SAP Sybase Error Number | 2574 |
SQL State | 55W14 |
SQL Code | -908L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An illegal attempt was made to access a closed UltraLite object. |
Error 910 | "System command failed with return code %1" |
---|---|
Constant | SYSTEM_COMMAND_FAILED |
SAP Sybase Error Number | 2575 |
SQL State | 38W01 |
SQL Code | -910L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Return code value. |
Probable Cause | A non-zero return code resulted when executing a system command. |
Error 911 | "Control character in XML output" |
---|---|
Constant | CONTROL_CHARACTER_IN_XML_OUTPUT |
SAP Sybase Error Number | 2576 |
SQL State | WX015 |
SQL Code | -911L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A non-space character less than hex 20 was encountered while generating XML content. Consider base64 encoding strings that contain control characters before using them as XML content. This can be accomplished in a FOR XML query or SQLX function by casting the string to a type such as LONG BINARY. |
Error 912 | "Insufficient memory for OPENXML query" |
---|---|
Constant | XQUERY_MEMORY_ERROR |
SAP Sybase Error Number | 2577 |
SQL State | WX016 |
SQL Code | -912L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The memory used by an OPENXML query may be proportional to the maximum distance between elements or attributes returned by a single row. For example, a query where some row uses the value from both the first and last element in the document may use memory proportional to the size of the document. One solution is to increase the cache size. Another is to break a query that refers to distant elements into several queries that refer to nearby elements and join the results. |
Error 913 | "A transaction log file is required for auditing" |
---|---|
Constant | AUDITING_WITHOUT_TRANSACTION_LOG |
SAP Sybase Error Number | 2578 |
SQL State | 42W91 |
SQL Code | -913L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | This database is running without a transaction log file. You must use the Transaction Log utility (dblog) to create a transaction log file before using auditing. |
Error 914 | "Cycle in common table expression references" |
---|---|
Constant | COMMON_TABLE_EXPRESSION_CYCLE |
SAP Sybase Error Number | 2579 |
SQL State | 42W93 |
SQL Code | -914L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | Cycles involving multiple common table expressions are not allowed. |
Error 915 | "Service type required for CREATE SERVICE" |
---|---|
Constant | SERVICE_TYPE_REQUIRED |
SAP Sybase Error Number | 2580 |
SQL State | 42W92 |
SQL Code | -915L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The CREATE SERVICE statement requires a service type to be specified. |
Error 916 | "'%1' is an unrecognized service type" |
---|---|
Constant | UNKNOWN_SERVICE_TYPE |
SAP Sybase Error Number | 2581 |
SQL State | 42W94 |
SQL Code | -916L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The service type that is unrecognized. |
Probable Cause | An unrecognized service type was specified. |
Error 918 | "A user name must be specified if AUTHORIZATION is Off" |
---|---|
Constant | SERVICE_REQUIRES_USER_NAME |
SAP Sybase Error Number | 2583 |
SQL State | 42W96 |
SQL Code | -918L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A valid user name must be specified if AUTHORIZATION is Off. |
Error 919 | "Service '%1' already exists" |
---|---|
Constant | SERVICE_ALREADY_EXISTS |
SAP Sybase Error Number | 2584 |
SQL State | 42W97 |
SQL Code | -919L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the service that already exists. |
Probable Cause | You have attempted to create a service with a name that already exists in the database. |
Error 920 | "Service '%1' not found" |
---|---|
Constant | SERVICE_NOT_FOUND |
SAP Sybase Error Number | 2585 |
SQL State | 42W98 |
SQL Code | -920L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the specified service that could not be found. |
Probable Cause | You have attempted to reference a service with a name that does not exist in the database. |
Error 921 | "Invalid recursive query" |
---|---|
Constant | INVALID_RECURSION |
SAP Sybase Error Number | 2586 |
SQL State | 42W99 |
SQL Code | -921L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | A recursive query must consist of the UNION ALL of an initial query and an iteration query. The only set operation allowed in the iteration query is UNION ALL. A recursive reference to the name of the common table expression can only appear in the iteration query, and must not be in a SELECT that uses DISTINCT, ORDER BY, or an aggregate function. A recursive reference also cannot appear on the NULL-supplying side of an outer join, or in a subquery. |
Error 922 | "No column list for recursive query" |
---|---|
Constant | NO_RECURSIVE_COLUMN_LIST |
SAP Sybase Error Number | 2587 |
SQL State | 42W9A |
SQL Code | -922L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | A common table expression defining a recursive query must have a column list. |
Error 923 | "Too many recursive iterations" |
---|---|
Constant | TOO_MANY_RECURSIVE_ITERATIONS |
SAP Sybase Error Number | 2588 |
SQL State | 57015 |
SQL Code | -923L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A recursive query ran for more iterations than allowed by the current max_recursive_iterations option setting. |