Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1283 | "A CONTAINS query is not allowed on the view or derived table '%1'." |
|---|---|
Constant | TEXT_INVALID_VIEW_FOR_CONTAINS |
SAP Sybase Error Number | 2970 |
SQL State | WT020 |
SQL Code | -1283L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the view or derived table that cannot be queried with CONTAINS. |
Probable Cause | A view or derived table can only be queried using CONTAINS if it does not use TOP, FIRST, DISTINCT, GROUP BY, or FOR XML. In addition, the list of columns to search must all come from a single base table in the FROM clause of the view. They cannot come from multiple tables, or from another view or derived table in the FROM clause. |
| Error 1284 | "Invalid partition key specification: must use '%1'. " |
|---|---|
Constant | CANNOT_CHANGE_PARTITION_KEY |
SAP Sybase Error Number | 2971 |
SQL State | WW233 |
SQL Code | -1284L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The partition key column name. |
Probable Cause | Partition key cannot be changed for ALTER TABLE ADD PARTITION. It must specify the same partition key column as the CREATE TABLE did. |
| Error 1285 | "%1 -- Transaction rolled back" |
|---|---|
Constant | IQ_TRANSACTION_ROLLBACK |
SAP Sybase Error Number | 2973 |
SQL State | 40W09 |
SQL Code | -1285L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Error because of which the transaction rolled back. |
Probable Cause | This transaction has been rolled back because the server encountered an error during a critical operation. |
| Error 1286 | "Immediate materialized view definition cannot contain a SUM function over a nullable expression." |
|---|---|
Constant | UPDATABLE_MATVIEW_SUM_NULL_EXPR |
SAP Sybase Error Number | 2974 |
SQL State | 42WCD |
SQL Code | -1286L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to change the refresh type to immediate for a materialized view whose definition contains a SUM function over a nullable expression. |
| Error 1287 | "Operation not allowed on global temporary table %1 as it is in use. Reconnect and try again." |
|---|---|
Constant | IQ_GTT_ALTER_DROP_NOTALLOWED |
SAP Sybase Error Number | 2975 |
SQL State | 55W35 |
SQL Code | -1287L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the table. |
Probable Cause | A global temporary table cannot be modified if it is in use. The user must reconnect and re-execute the statement. |
| Error 1288 | "'%1' statement is not allowed on a mirrored database" |
|---|---|
Constant | STMT_NOT_ALLOWED_WITH_MIRRORING |
SAP Sybase Error Number | 2976 |
SQL State | WW120 |
SQL Code | -1288L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Statement that generates the error. |
Probable Cause | You attempted to execute a statement that is not allowed when using a mirrored database. |
| Error 1289 | "LOAD TABLE option '%1' not allowed with FORMAT %2" |
|---|---|
Constant | INVALID_LOAD_TABLE_OPTION |
SAP Sybase Error Number | 2977 |
SQL State | WL016 |
SQL Code | -1289L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the option. |
Parameter 2 | The load table format. |
Probable Cause | The specified LOAD TABLE option is not meaningful for the LOAD TABLE FORMAT. |
| Error 1290 | "FOR UPDATE or FOR READ ONLY clause must be specified on PREPARE (not on DECLARE CURSOR)" |
|---|---|
Constant | CURSOR_UPDATABILITY_CHANGED |
SAP Sybase Error Number | 2978 |
SQL State | 42WD4 |
SQL Code | -1290L |
ODBC 2 State | S1009 |
ODBC 3 State | HY092 |
Severity Code | |
Probable Cause | You specified the FOR UPDATE or FOR READ ONLY clause on a DECLARE CURSOR statement. The FOR UPDATE or FOR READ ONLY clause must be specified on the PREPARE statement and not the DECLARE CURSOR statement. |
| Error 1291 | "Column '%1' Partition '%2' may not be assigned to a dbspace because partitioning is not supported for datatype '%3'." |
|---|---|
Constant | INVALID_COL_PARTITION_PLACEMENT |
SAP Sybase Error Number | 2979 |
SQL State | WW235 |
SQL Code | -1291L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The column name |
Parameter 2 | The partition name |
Parameter 3 | The data type |
Probable Cause | The column storage for certain datatypes (such as the BIT datatype) cannot be assigned to a dbspace. |
| Error 1292 | "Column '%1' may not be assigned to a dbspace because partitioning is not supported for datatype '%2'." |
|---|---|
Constant | INVALID_COL_PLACEMENT |
SAP Sybase Error Number | 2980 |
SQL State | WW236 |
SQL Code | -1292L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The column name |
Parameter 2 | The data type |
Probable Cause | The column storage for certain datatypes (such as the BIT datatype) cannot be assigned to a dbspace. |
| Error 1293 | "Partition key of '%1' is unsupported." |
|---|---|
Constant | UNSUPPORTED_PARTITION_KEY |
SAP Sybase Error Number | 2981 |
SQL State | WW237 |
SQL Code | -1293L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The column datatype |
Probable Cause | Partitioning over the specified datatype is not supported. |
| Error 1294 | "Parameter (%1) length has exceeded its limit (%2)." |
|---|---|
Constant | IQ_PARAM_LENGTH_EXCEED_LIMIT |
SAP Sybase Error Number | 2983 |
SQL State | WW122 |
SQL Code | -1294L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Parameter name. |
Parameter 2 | Allowed Maximum length. |
Probable Cause | Given parameter's length has exceeded the specified limit. |
| Error 1295 | "Database path must be absolute." |
|---|---|
Constant | IQ_MPX_ABS_DBPATH |
SAP Sybase Error Number | 2984 |
SQL State | WW123 |
SQL Code | -1295L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Specified Database path must be absolute. |
| Error 1296 | "(%1) is not unique." |
|---|---|
Constant | IQ_PARAM_VALUE_NOT_UNIQUE |
SAP Sybase Error Number | 2985 |
SQL State | WW124 |
SQL Code | -1296L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Parameter name. |
Probable Cause | Specified value for a given parameter already exist in the multiplex configuration. |
| Error 1297 | "No of servers in multiplex setup has reached to the maximum limit." |
|---|---|
Constant | IQ_MULTIPLEX_SERVER_LIMIT_EXCEEDED |
SAP Sybase Error Number | 2986 |
SQL State | WW125 |
SQL Code | -1297L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | No of servers in multiplex setup has reached to the maximum limit. User cannot add any more secondary servers. |
| Error 1298 | "Cannot alter multiplex failover node and other multiplex server properties in the same statement." |
|---|---|
Constant | IQ_INVALID_CONFIG_FAILOVER_COMBINATION |
SAP Sybase Error Number | 2987 |
SQL State | WW126 |
SQL Code | -1298L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Users are not allowed to alter the multiplex failover node status and other multiplex server properties in the same statement. |
| Error 1299 | "Drop multiplex server is allowed only in a multiplex setup." |
|---|---|
Constant | IQ_DROP_MPX_ALLOWED_ONLY_IN_MPX |
SAP Sybase Error Number | 2988 |
SQL State | WW127 |
SQL Code | -1299L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Drop multiplex server is allowed only in a multiplex setup. |
| Error 1300 | "Cannot add first multiplex server with excluded status." |
|---|---|
Constant | IQ_FIRST_SECONDARY_SERVER_CANNOT_BE_EXCLUDED |
SAP Sybase Error Number | 2989 |
SQL State | WW128 |
SQL Code | -1300L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Users are not allowed to add the first multiplex server with status excluded. |
| Error 1301 | "Cannot create multiplex server with role coordinator." |
|---|---|
Constant | IQ_CANNOT_CREATE_MPX_COORDINATOR |
SAP Sybase Error Number | 2990 |
SQL State | WW129 |
SQL Code | -1301L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Users are not allowed to create a multiplex server with role as coordinator. |
| Error 1302 | "Host Port specification (%1) is invalid." |
|---|---|
Constant | IQ_INVALID_HOSTNAME |
SAP Sybase Error Number | 2982 |
SQL State | WW121 |
SQL Code | -1302L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Host Port Specification. |
Probable Cause | Host port specification is invalid. |