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 |
|---|---|---|---|---|---|
| 2729 | Error | 5RW38 | -1060L | "Operation conflict with publication type" | You attempted to perform an operation not applicable to the type of publication. For example, you applied operations specific to a scripted upload publication to a logscan publication. Click here for a list of possible parameters and odbc states. |
| 2730 | Error | 42WB8 | -1061L | "Table created or altered after start of snapshot" | A snapshot transaction attempted to use a table that was created or altered after the transaction began. Click here for a list of possible parameters and odbc states. |
| 2731 | Error | 42WB9 | -1062L | "Statement not allowed during snapshot" | A connection with an outstanding snapshot attempted to use CREATE INDEX, DROP INDEX, ALTER INDEX or ALTER TABLE. Make sure all cursors for the connection are closed. Click here for a list of possible parameters and odbc states. |
| 2732 | Error | 08W93 | -1063L | "Unable to start database %1: Cannot use read-only mode if auditing is enabled" | The specified database has auditing enabled, and cannot be started read-only. Click here for a list of possible parameters and odbc states. |
| 2733 | Error | 42WBA | -1064L | "Update conflict on snapshot transaction" | A snapshot transaction attempted to update or delete a row that was changed by another transaction after the snapshot began. Click here for a list of possible parameters and odbc states. |
| 2734 | Error | 42WBB | -1065L | "Attempt to use snapshot isolation in a non-snapshot transaction" | A transaction tried to use snapshot isolation but did not begin with snapshot isolation. Click here for a list of possible parameters and odbc states. |
| 2735 | Error | WO027 | -1066L | "File system error: %1" | This error results from an error in the underlying file system that was encountered while accessing a file directory as a proxy table. Click here for a list of possible parameters and odbc states. |
| 2736 | Error | WT022 | -1370L | "Text queries cannot contain more than 300 terms." | A text query should contain 300 terms or less. Click here for a list of possible parameters and odbc states. |
| 2737 | Error | 52W43 | -1068L | "Default dbspace '%1' not found" | You tried to create a table with the default_dbspace option set to a dbspace that could not be found. Click here for a list of possible parameters and odbc states. |
| 2738 | Error | 28W12 | -1069L | "Kerberos login failed" | The Kerberos login failed due to a failure of the client to authenticate the user's principal with the KDC or a failure of the server to authenticate the client. The most likely causes are the Kerberos principal may not be signed in, the principal's ticket may have expired, or the client, server, or KDC's system time are not within a few minutes of each other. The LogFile connection parameter or the server's -z option may provide more information. Click here for a list of possible parameters and odbc states. |
| 2739 | Error | 28W13 | -1070L | "Kerberos logins are not supported" | The client and/or server does not support Kerberos logins. Kerberos may not be supported by the platform, the Kerberos client software including the GSS-API runtime may not be installed or found on the client, or Kerberos was not enabled on the server. The LogFile connection parameter or the server's -z option may provide more information. Click here for a list of possible parameters and odbc states. |
| 2740 | Error | 0AW16 | -1071L | "The %1 algorithm is not available in FIPS mode" | The specified algorithm is not available when the server is running in FIPS mode. Click here for a list of possible parameters and odbc states. |
| 2741 | Error | WC009 | -1072L | "'%1' is not a valid character set encoding for use with collation '%2'" | The specified character set cannot be used with the specified collation. Click here for a list of possible parameters and odbc states. |
| 2742 | Error | WC010 | -1073L | "'%1' cannot be used as the NCHAR collation: only UCA and UTF8BIN may be used" | The specified collation cannot be used as the NCHAR collation. NCHAR always uses UTF-8, so the collation must be either UCA or UTF8BIN. Click here for a list of possible parameters and odbc states. |
| 2743 | Error | 28W14 | -1074L | "Login mode '%1' not permitted by login_mode setting" | You attempted to connect using a login mode not included in the current login_mode database option setting. Change the option setting or connect using a different login mode. Click here for a list of possible parameters and odbc states. |
| 2744 | Error | WC011 | -1075L | "Failed to convert from character set '%1' to '%2'" | The server failed to convert between the two specified character sets. This could happen when the dbicu and dbicudt DLLs are not installed. Click here for a list of possible parameters and odbc states. |
| 2745 | Error | WC012 | -1076L | "dbicu libraries are required but not installed" | The server is unable to load ICU components that are required by this database. Ensure that the dbicu and dbicudt DLLs are installed. Click here for a list of possible parameters and odbc states. |
| 2746 | Error | 42WBC | -1077L | "Cannot use materialized view '%1' because it has not yet been initialized" | 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. Click here for a list of possible parameters and odbc states. |
| 2747 | Error | 42WBD | -1078L | "Cycle in computed column dependencies" | The table has a cycle in the dependencies between its computed columns. Cycles are not allowed. Click here for a list of possible parameters and odbc states. |
| 2748 | Error | WB017 | -1079L | "Backup is unable to open database file '%1'" | The database file can not be opened by the backup. It may have been erased or otherwise corrupted. Click here for a list of possible parameters and odbc states. |