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 |
|---|---|---|---|---|---|
| 2559 | Warning | 01W21 | 130L | "A row was dropped because it could not be converted to the new schema format" | A row that was valid in the old schema is no longer valid. This could be because a column domain changed and the old value cannot be cast to the new domain. Rows are also dropped if a uniqueness or foreign key constraint cannot be satisfied. Click here for a list of possible parameters and odbc states. |
| 2560 | Error | 42W82 | -896L | "Cannot delete PUBLIC option '%1' since user settings exist" | 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. Click here for a list of possible parameters and odbc states. |
| 2561 | Error | WT034 | -1512L | "Text index with external prefilter cannot contain both binary and string columns" | One or more, but not all, of the columns specified for the text index is of type binary, and the text configuration object has a prefilter library specified. Text indexes using a prefilter library can contain either binary columns or string data type columns, but not both. Click here for a list of possible parameters and odbc states. |
| 2562 | Warning | 01W23 | 132L | "Cannot output the histogram for string column '%1'" | You tried to get the histogram for a column containing strings. Histograms on string information cannot be output in a readable format; as a result, no information was retrieved. Consider using the ESTIMATE function to get information on a specific value or range in the column. Click here for a list of possible parameters and odbc states. |
| 2563 | Error | WX005 | -897L | "Illegal FOR XML EXPLICIT tag value: '%1'" | FOR XML EXPLICIT tag values must be greater than 0 and less than 256. Also, NULL values are not allowed in the Tag column. Click here for a list of possible parameters and odbc states. |
| 2564 | Error | WX006 | -898L | "Unknown FOR XML EXPLICIT directive: '%1'" | Legal FOR XML EXPLICIT directives are: id, idref, idrefs, hide, element, xml, cdata. Click here for a list of possible parameters and odbc states. |
| 2565 | Error | WX007 | -899L | "Illegal column name: '%1'" | FOR XML EXPLICIT column names can consist of up to four fields separated by exclamation marks. The first two columns must be named Tag and Parent. Click here for a list of possible parameters and odbc states. |
| 2566 | Error | WX008 | -900L | "Parent not open: '%1'" | FOR XML EXPLICIT requires 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 clause removed. Click here for a list of possible parameters and odbc states. |
| 2567 | Error | WX009 | -901L | "Undeclared tag ID: '%1'" | Every value appearing in the Tag column of the table must be declared in the TagNumber field of at least one column name. Click here for a list of possible parameters and odbc states. |
| 2568 | Error | WX010 | -902L | "Too few columns" | FOR XML EXPLICIT requires at least three columns: the tag column, the parent column, and one or more data columns. Click here for a list of possible parameters and odbc states. |
| 2569 | Error | WX011 | -903L | "CDATA has a name" | A CDATA directive in a FOR XML EXPLICIT query must not be given a name. Click here for a list of possible parameters and odbc states. |
| 2570 | Error | 42W90 | -904L | "Illegal ORDER BY in aggregate function" | 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. Click here for a list of possible parameters and odbc states. |
| 2571 | Error | WX012 | -905L | "Invalid XQuery constructor" | The XQuery constructor passed as the first argument to XMLGEN was not valid. Click here for a list of possible parameters and odbc states. |
| 2572 | Error | WX013 | -906L | "XMLGEN evaluation failure" | One of the variables referenced in the XQuery constructor was not found in the list of arguments. Click here for a list of possible parameters and odbc states. |
| 2573 | Error | WX014 | -907L | "No name for argument" | Unnamed arguments cannot be used as XML element or attribute names. Name unnamed items in the argument list using AS. Click here for a list of possible parameters and odbc states. |
| 2574 | Error | 55W14 | -908L | "Invalid operation on a closed object" | An illegal attempt was made to access a closed UltraLite object. Click here for a list of possible parameters and odbc states. |
| 2575 | Error | 38W01 | -910L | "System command failed with return code %1" | A non-zero return code resulted when executing a system command. Click here for a list of possible parameters and odbc states. |
| 2576 | Error | WX015 | -911L | "Control character in XML output" | 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. Click here for a list of possible parameters and odbc states. |
| 2577 | Error | WX016 | -912L | "Insufficient memory for OPENXML query" | 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. Click here for a list of possible parameters and odbc states. |
| 2578 | Error | 42W91 | -913L | "A transaction log file is required for auditing" | 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. Click here for a list of possible parameters and odbc states. |