Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1077 | "Cannot use materialized view '%1' because it has not yet been initialized" |
|---|---|
Constant | CANNOT_USE_MATVIEW |
SAP Sybase Error Number | 2746 |
SQL State | 42WBC |
SQL Code | -1077L |
ODBC 2 State | 42000 |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the materialized view. |
Probable Cause | You attempted to use a materialized view but it has not yet been initialized. In order for a materialized view to become available for first use after being created or enabled, it must be initialized at least once using the REFRESH MATERIALIZED VIEW statement. |
| Error 1078 | "Cycle in computed column dependencies" |
|---|---|
Constant | COMPUTED_COLUMN_CYCLE |
SAP Sybase Error Number | 2747 |
SQL State | 42WBD |
SQL Code | -1078L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | The table has a cycle in the dependencies between its computed columns. Cycles are not allowed. |
| Error 1079 | "Backup is unable to open database file '%1'" |
|---|---|
Constant | BACKUP_UNABLE_TO_OPEN_FILE |
SAP Sybase Error Number | 2748 |
SQL State | WB017 |
SQL Code | -1079L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the file. |
Probable Cause | The database file cannot be opened by the backup. It may have been erased or otherwise corrupted. |
| Error 1080 | "Cannot revoke these permissions while user '%1' is actively replicating transactions" |
|---|---|
Constant | MUST_NOT_BE_REPLICATING |
SAP Sybase Error Number | 2749 |
SQL State | 42WBE |
SQL Code | -1080L |
ODBC 2 State | 40001 |
ODBC 3 State | 40001 |
Severity Code | |
Parameter 1 | The name of the user. |
Probable Cause | You attempted to revoke permissions from a user while there are transactions currently being replicated for that user. This is not allowed. |
| Error 1081 | "Could not refresh tracing: at least one enabled tracing level must be specified" |
|---|---|
Constant | NO_TRACING_LEVELS |
SAP Sybase Error Number | 2750 |
SQL State | 55W24 |
SQL Code | -1081L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Table sa_diagnostic_tracing_level contains no rows (tracing levels) or no tracing levels are enabled. |
| Error 1082 | "Could not refresh tracing: invalid tracing specification on sa_diagnostic_tracing_level row %1" |
|---|---|
Constant | INVALID_TRACING_SPEC |
SAP Sybase Error Number | 2751 |
SQL State | WW066 |
SQL Code | -1082L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The primary key of the row that is invalid. |
Probable Cause | You specified an invalid combination of values for the tracing level. Some invalid combinations are: specified condition is not valid for the tracing type, or specified tracing type is not valid for the scope. |
| Error 1083 | "Could not refresh tracing: failed to find object %1 on row %2" |
|---|---|
Constant | TRACING_OBJ_NOT_FOUND |
SAP Sybase Error Number | 2752 |
SQL State | WW067 |
SQL Code | -1083L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The specified name of the object. |
Parameter 2 | The primary key of the row on which the check failed. |
Probable Cause | You misspelled the object name, or you did not qualify the name with user (and, possibly, table) name. For example, you might have referred to Employees instead of "DBA"."Employees", or you might have referred to Employees_trigger instead of "DBA"."Employees"."Employees_trigger". |
| Error 1084 | "Use of feature '%1' is not allowed" |
|---|---|
Constant | SECURE_FEATURE |
SAP Sybase Error Number | 2753 |
SQL State | 57W02 |
SQL Code | -1084L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the SQL statement or feature. |
Probable Cause | You have attempted to use a feature that was disabled by the server administrator when the database server was started. |
| Error 1085 | "Duplicate key column (%1)" |
|---|---|
Constant | DUPLICATE_KEY_COLUMN |
SAP Sybase Error Number | 2754 |
SQL State | 42WC0 |
SQL Code | -1085L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The name of the duplicate column. |
Probable Cause | You supplied a duplicate column name in the list of columns for the key of a primary key, foreign key, or unique constraint, or an index. |
| Error 1087 | "Could not refresh tracing: volatile_statistics have to be collected in order for %1 specified on row %2 to be collected" |
|---|---|
Constant | NO_VOLATILE_LEVEL_SPEC |
SAP Sybase Error Number | 2756 |
SQL State | WW068 |
SQL Code | -1087L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The tracing level that caused the error. |
Parameter 2 | The primary key of the row on which the check failed. |
Probable Cause | Volatile statistics have to be collected in order for the non-volatile and connection statistics to be collected. |
| Error 1088 | "ATTACH TRACING TO LOCAL DATABASE cannot be used with a strongly encrypted database" |
|---|---|
Constant | NO_LOCAL_CONNECTIONS_TO_ENCRYPTED |
SAP Sybase Error Number | 2757 |
SQL State | WW069 |
SQL Code | -1088L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The local database is strongly encrypted, so you cannot use the LOCAL DATABASE clause of the ATTACH TRACING statement. You must specify a connection string with the encryption key for the database. |
| Error 1089 | "Invalid commit action for shared temporary table" |
|---|---|
Constant | INVALID_SHARED_COMMIT_ACTION |
SAP Sybase Error Number | 2758 |
SQL State | 52W26 |
SQL Code | -1089L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A global shared temporary table must be declared as ON COMMIT PRESERVE ROWS or NOT TRANSACTIONAL. |
| Error 1090 | "Function '%1' has invalid parameter '%2' ('%3')" |
|---|---|
Constant | INVALID_PARAMETER_W_PARM |
SAP Sybase Error Number | 2759 |
SQL State | 08W94 |
SQL Code | -1090L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Parameter 1 | The name of the function. |
Parameter 2 | The name of the parameter. |
Parameter 3 | Information about the parameter that caused the error. |
Probable Cause | An error occurred while evaluating a parameter. |
| Error 1091 | "Constraint '%1' violated: Invalid value in table '%2'" |
|---|---|
Constant | TABLE_CONSTRAINT_VIOLATED |
SAP Sybase Error Number | 2760 |
SQL State | 23508 |
SQL Code | -1091L |
ODBC 2 State | 42000 |
ODBC 3 State | 23000 |
Severity Code | |
Parameter 1 | Name of the constraint (if defined) that was violated by an invalid value. |
Parameter 2 | Name of the table containing the column. |
Probable Cause | You attempted an insert or update that violates a CHECK constraint. A CHECK constraint is violated if it evaluates to FALSE; it is deemed to hold if the condition evaluates to TRUE or UNKNOWN. |
| Error 1092 | "The method you attempted to invoke was not enabled for your application" |
|---|---|
Constant | FEATURE_NOT_ENABLED |
SAP Sybase Error Number | 2762 |
SQL State | 0A001 |
SQL Code | -1092L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to call a method or use a feature that has not been enabled. In UltraLite, features are enabled using ULEnable functions or by using ULInitDatabaseManager instead of ULInitDatabaseManagerNoSQL. |
| Error 1093 | "The size of the character column, variable, or value data type exceeds 32767" |
|---|---|
Constant | CHAR_FIELD_SIZE_EXCEEDED |
SAP Sybase Error Number | 2763 |
SQL State | 54W09 |
SQL Code | -1093L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The declaration or conversion has specified a character type with byte length greater than 32767. |
| Error 1094 | "The HTTP header '%1' is reserved and cannot be modified" |
|---|---|
Constant | HTTP_HEADER_ATTRIBUTE_RESERVED_XXX |
SAP Sybase Error Number | 2764 |
SQL State | WW070 |
SQL Code | -1094L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The header causing the failure. |
Probable Cause | The specified HTTP header is reserved and cannot be modified. |
| Error 1095 | "The specified HTTP header contains illegal or non-ASCII characters" |
|---|---|
Constant | HTTP_HEADER_ATTRIBUTE_ASCII |
SAP Sybase Error Number | 2765 |
SQL State | WW071 |
SQL Code | -1095L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | HTTP headers must contain printable ASCII characters. |
| Error 1096 | "The specified HTTP header is malformed" |
|---|---|
Constant | HTTP_HEADER_ATTRIBUTE_MALFORMED |
SAP Sybase Error Number | 2766 |
SQL State | WW072 |
SQL Code | -1096L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The HTTP header is missing the colon delimiter or a folding construct is malformed. |
| Error 1097 | "ATTACH TRACING could not connect to the tracing database" |
|---|---|
Constant | ATTACH_TRACING_FAILED |
SAP Sybase Error Number | 2767 |
SQL State | 08W95 |
SQL Code | -1097L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A connection to the tracing database could not be established. Check your connection string and verify that other clients can connect. Note that if you are trying to attach tracing to another server, perhaps the connection is being blocked by a firewall. |