Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1179 | "Unable to start database server: missing license file" |
|---|---|
Constant | UNABLE_TO_START_ENGINE_MISSING_LICENSE |
SAP Sybase Error Number | 2856 |
SQL State | 08WA2 |
SQL Code | -1179L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | It was not possible to start the database server because the server license file was not found. The server license file has the same name as the server executable with the extension ".lic". |
| Error 1180 | "Cannot set database option \"%1\" because it is on the options watch list" |
|---|---|
Constant | OPTION_ON_WATCH_LIST |
SAP Sybase Error Number | 2857 |
SQL State | WW096 |
SQL Code | -1180L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the option. |
Probable Cause | An attempt was made to set a database option that is on the options watch list. The options watch list is used to help find references to options that have been removed or deprecated. |
| Error 1181 | "The materialized view cannot be changed to immediate because its definition must not contain more than one query block" |
|---|---|
Constant | UPDATABLE_MATVIEW_MULTIBLE_BLOCK_ERR |
SAP Sybase Error Number | 2858 |
SQL State | 42WC5 |
SQL Code | -1181L |
ODBC 2 State | 42000 |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to change the refresh type to immediate for a materialized view whose definition contains more than one query block. |
| Error 1182 | "Statement not allowed on IMMEDIATE REFRESH text index" |
|---|---|
Constant | TEXT_IMMEDIATE_NOT_ALLOWED |
SAP Sybase Error Number | 2859 |
SQL State | WT015 |
SQL Code | -1182L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You cannot use REFRESH TEXT INDEX or TRUNCATE TEXT INDEX on an index that is created with immediate refresh. You cannot alter a text index to use or stop using immediate refresh. |
| Error 1183 | "Support for permissions on dbspaces is not available for this database" |
|---|---|
Constant | DBSPACE_PERMS_NOT_SUPPORTED |
SAP Sybase Error Number | 2860 |
SQL State | 0AW22 |
SQL Code | -1183L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The statement being executed requires support for permissions on dbspaces, but the database being used does not have this capability. The database must be recreated or upgraded using a version of the server that supports permissions on dbspaces. |
| Error 1184 | "Cannot drop last unique index of an immediate materialized view" |
|---|---|
Constant | DELETE_UPDATABLE_MATVIEW_INDEX_ERR |
SAP Sybase Error Number | 2861 |
SQL State | 55W21 |
SQL Code | -1184L |
ODBC 2 State | 42000 |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to drop the last unique index on non-nullable columns of an immediate materialized view. Immediate materialized view needs at least one unique index on non-nullable columns to be valid. |
| Error 1185 | "Index validation failed for table %1, index %2 with code: %3" |
|---|---|
Constant | CORRUPT_ULTRALITE_INDEX |
SAP Sybase Error Number | 2862 |
SQL State | WI002 |
SQL Code | -1185L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the table. |
Parameter 2 | The name of the index. |
Parameter 3 | The specific kind of corruption that was found. |
Probable Cause | UltraLite database validation failed while validating the specified index. The code provides more specific information on the validation failure. |
| Error 1186 | "Database page validation failed with code: %1" |
|---|---|
Constant | CORRUPT_ULTRALITE_DATABASE |
SAP Sybase Error Number | 2863 |
SQL State | WI003 |
SQL Code | -1186L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The specific kind of corruption that was found. |
Probable Cause | UltraLite database validation failed while validating the database pages. The code provides more specific information on the validation failure. |
| Error 1187 | "Cannot append when using compression or encryption" |
|---|---|
Constant | UNLOAD_CANNOT_APPEND |
SAP Sybase Error Number | 2864 |
SQL State | WL012 |
SQL Code | -1187L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The UNLOAD statement cannot append to a file when using compression or encryption. Either the compressed or encrypted keywords were specified, or the file being appended to is compressed or encrypted. |
| Error 1188 | "LOAD TABLE error: %1" |
|---|---|
Constant | LOAD_TABLE_ERROR |
SAP Sybase Error Number | 2865 |
SQL State | WL013 |
SQL Code | -1188L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Description of the failure encountered |
Probable Cause | The LOAD TABLE statement failed. The message specifies the actual problem that occurred. |
| Error 1189 | "The UTF-16 endian specified does not match the Byte Order Mark found in the data" |
|---|---|
Constant | UTF16_ENDIAN_MISMATCH |
SAP Sybase Error Number | 2866 |
SQL State | WC004 |
SQL Code | -1189L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The specified UTF-16 encoding explicitly specifies the expected endian of the data; however, the Byte Order Mark found at the beginning of the data indicates that the data is encoded in the opposite endian. |
| Error 1190 | "LOAD TABLE is not allowed on a materialized view %1" |
|---|---|
Constant | LOAD_TABLE_ON_MATVIEW_ERROR |
SAP Sybase Error Number | 2867 |
SQL State | WL014 |
SQL Code | -1190L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the materialized view on which load was attempted. |
Probable Cause | LOAD TABLE statement is not allowed on a materialized view. |
| Error 1191 | "LOAD TABLE not allowed: initialized immediate materialized view %1 depends on %2" |
|---|---|
Constant | LOAD_TABLE_WITH_IMV |
SAP Sybase Error Number | 2868 |
SQL State | WL015 |
SQL Code | -1191L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the dependent initialized immediate materialized view. |
Parameter 2 | Name of the table on which load was performed. |
Probable Cause | LOAD TABLE is not permitted on any table that has dependent initialized immediate materialized views. |
| Error 1192 | "Cannot update multiple tables immediate materialized view %1 depends on" |
|---|---|
Constant | CANNOT_UPDATE_TWO_TABLES_IMV |
SAP Sybase Error Number | 2869 |
SQL State | 55W29 |
SQL Code | -1192L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the view that depends on two or more tables in the update statement. |
Probable Cause | You attempted to simultaneously update two or more tables initialized immediate materialized view depends on. No more than one base table an immediate materialized view depends on can be updated in a statement. |
| Error 1193 | "TRUNCATE TABLE not allowed: initialized immediate materialized view %1 depends on %2" |
|---|---|
Constant | TRUNCATE_TABLE_WITH_IMV |
SAP Sybase Error Number | 2870 |
SQL State | 55W30 |
SQL Code | -1193L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the dependent initialized immediate materialized view. |
Parameter 2 | Name of the table on which TRUNCATE TABLE was performed. |
Probable Cause | TRUNCATE TABLE is not permitted on any table that has dependent initialized immediate materialized views. |
| Error 1194 | "Login policy \"%1\" already exists" |
|---|---|
Constant | LOGIN_POLICY_ALREADY_EXISTS |
SAP Sybase Error Number | 2871 |
SQL State | WW097 |
SQL Code | -1194L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the login policy. |
Probable Cause | An attempt was made to create a login policy that already exists in the database. |
| Error 1195 | "Login policy \"%1\" not found" |
|---|---|
Constant | LOGIN_POLICY_NOT_FOUND |
SAP Sybase Error Number | 2872 |
SQL State | WW098 |
SQL Code | -1195L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the login policy. |
Probable Cause | The named login policy was not found in the database. |
| Error 1196 | "Login policies are not supported for this database" |
|---|---|
Constant | LOGIN_POLICY_UPGRADE |
SAP Sybase Error Number | 2873 |
SQL State | WW099 |
SQL Code | -1196L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The current database does not have catalog support for login policies. To use this feature, upgrade your database to the most recent version. |
| Error 1197 | "Login policy \"%1\" in use" |
|---|---|
Constant | LOGIN_POLICY_IN_USE |
SAP Sybase Error Number | 2874 |
SQL State | WW100 |
SQL Code | -1197L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the login policy. |
Probable Cause | The named login policy is associated with a user in the database. Any users associated with the login policy must be assigned a different login policy before the named login policy can be dropped. |
| Error 1198 | "User \"%1\" already exists" |
|---|---|
Constant | USER_ALREADY_EXISTS |
SAP Sybase Error Number | 2875 |
SQL State | WW101 |
SQL Code | -1198L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the user. |
Probable Cause | An attempt was made to create a user that already exists in the database. |