Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
Error 945 | "Recursive column %1: conversion from '%2' to '%3' loses precision" |
---|---|
Constant | BAD_RECURSIVE_COLUMN_CONVERSION |
SAP Sybase Error Number | 2609 |
SQL State | 42WA2 |
SQL Code | -945L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Column number of the recursive subquery. |
Parameter 2 | Type converted from. |
Parameter 3 | Type converted to. |
Probable Cause | Every column in the recursive subquery must be convertible to the type of the corresponding column in the initial subquery without loss of precision. Try casting the column in the initial subquery to an appropriate type. |
Error 946 | "Result set not permitted in '%1'" |
---|---|
Constant | RESULT_SET_NOT_PERMITTED |
SAP Sybase Error Number | 2610 |
SQL State | 09W03 |
SQL Code | -946L |
ODBC 2 State | 07005 |
ODBC 3 State | 07005 |
Severity Code | |
Parameter 1 | Name of object containing the invalid statement. |
Probable Cause | You attempted to execute a SELECT statement in a context where a result set is not permitted. |
Error 947 | "Window '%1' not found" |
---|---|
Constant | WINDOW_NOT_FOUND |
SAP Sybase Error Number | 2611 |
SQL State | 42WA3 |
SQL Code | -947L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the window that could not be found. |
Probable Cause | You have attempted to reference a window name that is not defined in the window list of the SELECT statement. |
Error 948 | "PARTITION BY not allowed in reference to window '%1'" |
---|---|
Constant | PARTITIONBY_NOT_ALLOWED |
SAP Sybase Error Number | 2612 |
SQL State | 42WA4 |
SQL Code | -948L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the window. |
Probable Cause | When an existing window name is referenced from an inline window specification, the inline specification must not have a PARTITION BY clause. |
Error 949 | "ORDER BY not allowed in window '%1'" |
---|---|
Constant | ORDERBY_NOT_ALLOWED |
SAP Sybase Error Number | 2613 |
SQL State | 42WA5 |
SQL Code | -949L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the window. |
Probable Cause | When an existing window name is referenced from an inline window specification, either the inline window or the referenced window may have an ORDER BY, but not both. |
Error 950 | "Frame not allowed for window '%1'" |
---|---|
Constant | FRAME_NOT_ALLOWED |
SAP Sybase Error Number | 2614 |
SQL State | 42WA6 |
SQL Code | -950L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the window. |
Probable Cause | Frames are not allowed on windows referenced from inline window specifications. |
Error 951 | "Cannot access schema file '%1'" |
---|---|
Constant | CANNOT_ACCESS_SCHEMA_FILE |
SAP Sybase Error Number | 2615 |
SQL State | WW031 |
SQL Code | -951L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the file or indication that no name was given. |
Probable Cause | UltraLite requires a schema file to perform the current operation. Either no schema file was specified or the one specified was not accessible or was corrupt. |
Error 952 | "The status of the last synchronization upload is unknown" |
---|---|
Constant | SYNC_STATUS_UNKNOWN |
SAP Sybase Error Number | 2616 |
SQL State | WW032 |
SQL Code | -952L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The status of the last synchronization upload is unknown. The current operation cannot proceed until a successful upload is synchronized. |
Error 953 | "A schema upgrade is not currently allowed" |
---|---|
Constant | SCHEMA_UPGRADE_NOT_ALLOWED |
SAP Sybase Error Number | 2617 |
SQL State | WW033 |
SQL Code | -953L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A schema upgrade cannot proceed because of concurrent use of the database. For example, all cursors must be closed before a schema upgrade can occur. |
Error 954 | "The database '%1' was not found" |
---|---|
Constant | ULTRALITE_DATABASE_NOT_FOUND |
SAP Sybase Error Number | 2618 |
SQL State | WW034 |
SQL Code | -954L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the database specified or the default database name. |
Probable Cause | The named database was not found. Ensure your connection string properly names the desired database. |
Error 955 | "This connection already exists" |
---|---|
Constant | CONNECTION_ALREADY_EXISTS |
SAP Sybase Error Number | 2619 |
SQL State | WW035 |
SQL Code | -955L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A connection with the given SQLCA and name (or no name) already exists. Before connecting you must disconnect the existing connection, or specify a different connection name. |
Error 956 | "Information for synchronization is incomplete or invalid, check '%1'" |
---|---|
Constant | SYNC_INFO_INVALID |
SAP Sybase Error Number | 2620 |
SQL State | WW036 |
SQL Code | -956L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the parameter not properly initialized. |
Probable Cause | Information for synchronization is incomplete or invalid. Correct the indicated parameter before attempting to synchronize again. If 'init_verify' is indicated, the InitSyncInfo function was not called. |
Error 957 | "Invalid preceding or following size in OLAP function" |
---|---|
Constant | INVALID_FRAME_BOUNDARY |
SAP Sybase Error Number | 2621 |
SQL State | 22X13 |
SQL Code | -957L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The expression for the preceding or following size evaluated to NULL or a negative value. |
Error 958 | "Password cannot be longer than %1 characters" |
---|---|
Constant | PASSWORD_TOO_LONG |
SAP Sybase Error Number | 2622 |
SQL State | 54W08 |
SQL Code | -958L |
ODBC 2 State | 37000 |
ODBC 3 State | 54000 |
Severity Code | |
Probable Cause | The password is longer than that allowed by the server. |
Error 959 | "Compression error: %1" |
---|---|
Constant | COMPRESSION_ERROR |
SAP Sybase Error Number | 2623 |
SQL State | WW037 |
SQL Code | -959L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An error occurred during compression. |
Error 960 | "Decompression error: %1" |
---|---|
Constant | DECOMPRESSION_ERROR |
SAP Sybase Error Number | 2624 |
SQL State | WW038 |
SQL Code | -960L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An error occurred during decompression. |
Error 961 | "Input string is not base64-encoded" |
---|---|
Constant | BASE64_DECODING_ERROR |
SAP Sybase Error Number | 2625 |
SQL State | WW039 |
SQL Code | -961L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An error occurred during base64 decoding. |
Error 962 | "Argument to GROUPING aggregate must be a grouping column in the GROUP BY clause" |
---|---|
Constant | INVALID_GROUPING_AGGREGATE |
SAP Sybase Error Number | 2626 |
SQL State | 42WA7 |
SQL Code | -962L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | Only a grouping column is permitted as an argument to the GROUPING aggregate function. An argument that contains anything other than a single grouping column expression will not be accepted. |
Error 963 | "Password contains an illegal character" |
---|---|
Constant | ILLEGAL_PASSWORD |
SAP Sybase Error Number | 2627 |
SQL State | 08005 |
SQL Code | -963L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | The specified password contains an illegal character. |
Error 964 | "Window function used in predicate" |
---|---|
Constant | ILLEGAL_WINDOW_PREDICATE |
SAP Sybase Error Number | 2628 |
SQL State | 42WA8 |
SQL Code | -964L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A window function was used in the WHERE or HAVING clause of a SELECT statement. Consider making the SELECT into a derived table, putting the window function in the SELECT list of the derived table, and changing the predicate to reference the derived column. |