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 |
|---|---|---|---|---|---|
| 2859 | Error | WT015 | -1182L | "Statement not allowed on IMMEDIATE REFRESH text index" | 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. Click here for a list of possible parameters and odbc states. |
| 2860 | Error | 0AW22 | -1183L | "Support for permissions on dbspaces is not available for this database" | 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. Click here for a list of possible parameters and odbc states. |
| 2861 | Error | 55W21 | -1184L | "Cannot drop last unique index of an immediate materialized view" | 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. Click here for a list of possible parameters and odbc states. |
| 2862 | Error | WI002 | -1185L | "Index validation failed for table %1, index %2 with code: %3" | UltraLite database validation failed while validating the specified index. The code provides more specific information on the validation failure. Click here for a list of possible parameters and odbc states. |
| 2863 | Error | WI003 | -1186L | "Database page validation failed with code: %1" | UltraLite database validation failed while validating the database pages. The code provides more specific information on the validation failure. Click here for a list of possible parameters and odbc states. |
| 2864 | Error | WL012 | -1187L | "Cannot append when using compression or encryption" | 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. Click here for a list of possible parameters and odbc states. |
| 2865 | Error | WL013 | -1188L | "LOAD TABLE error: %1" | The LOAD TABLE statement failed. The message specifies the actual problem that occurred. Click here for a list of possible parameters and odbc states. |
| 2866 | Error | WC004 | -1189L | "The UTF-16 endian specified does not match the Byte Order Mark found in the data" | 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. Click here for a list of possible parameters and odbc states. |
| 2867 | Error | WL014 | -1190L | "LOAD TABLE is not allowed on a materialized view %1" | LOAD TABLE statement is not allowed on a materialized view. Click here for a list of possible parameters and odbc states. |
| 2868 | Error | WL015 | -1191L | "LOAD TABLE not allowed: initialized immediate materialized view %1 depends on %2" | LOAD TABLE is not permitted on any table that has dependent initialized immediate materialized views. Click here for a list of possible parameters and odbc states. |
| 2869 | Error | 55W29 | -1192L | "Cannot update multiple tables immediate materialized view %1 depends on" | 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. Click here for a list of possible parameters and odbc states. |
| 2870 | Error | 55W30 | -1193L | "TRUNCATE TABLE not allowed: initialized immediate materialized view %1 depends on %2" | TRUNCATE TABLE is not permitted on any table that has dependent initialized immediate materialized views. Click here for a list of possible parameters and odbc states. |
| 2871 | Error | WW097 | -1194L | "Login policy \"%1\" already exists" | An attempt was made to create a login policy that already exists in the database. Click here for a list of possible parameters and odbc states. |
| 2872 | Error | WW098 | -1195L | "Login policy \"%1\" not found" | The named login policy was not found in the database. Click here for a list of possible parameters and odbc states. |
| 2873 | Error | WW099 | -1196L | "Login policies are not supported for this database" | The current database does not have catalog support for login policies. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |
| 2874 | Error | WW100 | -1197L | "Login policy \"%1\" in use" | 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. Click here for a list of possible parameters and odbc states. |
| 2875 | Error | WW101 | -1198L | "User \"%1\" already exists" | An attempt was made to create a user that already exists in the database. Click here for a list of possible parameters and odbc states. |
| 2876 | Error | 42WC6 | -1199L | "The materialized view cannot be changed to immediate because COUNT(*) must be part of the SELECT list." | You attempted to change the refresh type to immediate for a materialized view whose definition does not include COUNT(*) in the SELECT list. Click here for a list of possible parameters and odbc states. |
| 2877 | Error | WW103 | -1200L | "Client library reported a permissions error accessing object ('%1') during transfer" | The client application reported a permissions error while attempting to access the object for a data transfer request from the server. The client application likely does not have the necessary operating system authorization required to access the object. Click here for a list of possible parameters and odbc states. |
| 2878 | Error | WW102 | -1201L | "Client library reported an error opening object ('%1') during transfer" | The client application reported an error while attempting to open the object for a data transfer request from the server. Reasons could include an invalid name for the object or a missing object. Click here for a list of possible parameters and odbc states. |