Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1052 | "Cannot update materialized view because option '%1' has an inappropriate setting" |
|---|---|
Constant | CANNOT_UPDATE_MATVIEW |
SAP Sybase Error Number | 2721 |
SQL State | 42WB7 |
SQL Code | -1052L |
ODBC 2 State | 42000 |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the option with the incorrect setting. |
Probable Cause | You attempted to update/refresh a materialized view but one of the database options is currently set to a value that is not permitted while updating a materialized view, or, the option's setting does not match the value when the view was created. |
| Error 1053 | "'%1' is an invalid value for '%2'" |
|---|---|
Constant | INVALID_OPTION_VALUE |
SAP Sybase Error Number | 2722 |
SQL State | 42W85 |
SQL Code | -1053L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The invalid value. |
Parameter 2 | Name of the option. |
Probable Cause | You supplied an invalid value for an option. Some options only allow numeric values and some options only allow true or false. Also, many options do not permit the empty string as a value. |
| Error 1054 | "Snapshot isolation disabled or pending" |
|---|---|
Constant | SNAPSHOT_ISOLATION_DISABLED |
SAP Sybase Error Number | 2723 |
SQL State | 55W23 |
SQL Code | -1054L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Snapshot isolation is disabled or its activation is still pending. You must enable snapshot isolation before using it. |
| Error 1057 | "BACKUP clause '%1' conflicts with '%2'" |
|---|---|
Constant | INVALID_BACKUP_STATEMENT |
SAP Sybase Error Number | 2726 |
SQL State | WB016 |
SQL Code | -1057L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | First BACKUP clause. |
Parameter 2 | Second BACKUP clause. |
Probable Cause | Clauses specified in the BACKUP STATEMENT are mutually exclusive. |
| Error 1060 | "Operation conflict with publication type" |
|---|---|
Constant | CONFLICTING_PUB_TYPE |
SAP Sybase Error Number | 2729 |
SQL State | 5RW38 |
SQL Code | -1060L |
ODBC 2 State | 42000 |
ODBC 3 State | 42S02 |
Severity Code | |
Probable Cause | 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. |
| Error 1061 | "Table created or altered after start of snapshot" |
|---|---|
Constant | SNAPSHOT_TABLE_CHANGED |
SAP Sybase Error Number | 2730 |
SQL State | 42WB8 |
SQL Code | -1061L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A snapshot transaction attempted to use a table that was created or altered after the transaction began. |
| Error 1062 | "Statement not allowed during snapshot" |
|---|---|
Constant | STATEMENT_NOT_ALLOWED_IN_SNAPSHOT |
SAP Sybase Error Number | 2731 |
SQL State | 42WB9 |
SQL Code | -1062L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
| Error 1063 | "Unable to start database %1: Cannot use read-only mode if auditing is enabled" |
|---|---|
Constant | AUDITING_DB_READ_ONLY |
SAP Sybase Error Number | 2732 |
SQL State | 08W93 |
SQL Code | -1063L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | Name of the database. |
Probable Cause | The specified database has auditing enabled, and cannot be started read-only. |
| Error 1064 | "Update conflict on snapshot transaction" |
|---|---|
Constant | SNAPSHOT_UPDATE_CONFLICT |
SAP Sybase Error Number | 2733 |
SQL State | 42WBA |
SQL Code | -1064L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A snapshot transaction attempted to update or delete a row that was changed by another transaction after the snapshot began. |
| Error 1065 | "Attempt to use snapshot isolation in a non-snapshot transaction" |
|---|---|
Constant | NON_SNAPSHOT_TRANSACTION |
SAP Sybase Error Number | 2734 |
SQL State | 42WBB |
SQL Code | -1065L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A transaction tried to use snapshot isolation but did not begin with snapshot isolation. |
| Error 1066 | "File system error: %1" |
|---|---|
Constant | OMNI_FILE_SYSTEM_ERROR |
SAP Sybase Error Number | 2735 |
SQL State | WO027 |
SQL Code | -1066L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Error description. |
Probable Cause | This error results from an error in the underlying file system that was encountered while accessing a file directory as a proxy table. |
| Error 1068 | "Default dbspace '%1' not found" |
|---|---|
Constant | DEFAULT_DBSPACE_NOT_FOUND |
SAP Sybase Error Number | 2737 |
SQL State | 52W43 |
SQL Code | -1068L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the default dbspace that could not be found. |
Probable Cause | You tried to create a table with the default_dbspace option set to a dbspace that could not be found. |
| Error 1069 | "Kerberos login failed" |
|---|---|
Constant | KERBEROS_LOGON_FAILED |
SAP Sybase Error Number | 2738 |
SQL State | 28W12 |
SQL Code | -1069L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | 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. |
| Error 1070 | "Kerberos logins are not supported" |
|---|---|
Constant | KERBEROS_LOGONS_UNSUPPORTED |
SAP Sybase Error Number | 2739 |
SQL State | 28W13 |
SQL Code | -1070L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | 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. |
| Error 1071 | "The %1 algorithm is not available in FIPS mode" |
|---|---|
Constant | FIPS_NOT_AVAILABLE |
SAP Sybase Error Number | 2740 |
SQL State | 0AW16 |
SQL Code | -1071L |
ODBC 2 State | ERROR |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | Name of the algorithm. |
Probable Cause | The specified algorithm is not available when the server is running in FIPS mode. |
| Error 1072 | "'%1' is not a valid character set encoding for use with collation '%2'" |
|---|---|
Constant | INVALID_ENCODING_FOR_COLLATION |
SAP Sybase Error Number | 2741 |
SQL State | WC009 |
SQL Code | -1072L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The character set encoding that is invalid. |
Parameter 2 | The collation for which the character set encoding is invalid. |
Probable Cause | The specified character set cannot be used with the specified collation. |
| Error 1073 | "'%1' cannot be used as the NCHAR collation: only UCA and UTF8BIN may be used" |
|---|---|
Constant | INVALID_NCHAR_COLLATION |
SAP Sybase Error Number | 2742 |
SQL State | WC010 |
SQL Code | -1073L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The collation that cannot be used as the NCHAR collation. |
Probable Cause | The specified collation cannot be used as the NCHAR collation. NCHAR always uses UTF-8, so the collation must be either UCA or UTF8BIN. |
| Error 1074 | "Login mode '%1' not permitted by login_mode setting" |
|---|---|
Constant | LOGON_MODE_NOT_PERMITTED |
SAP Sybase Error Number | 2743 |
SQL State | 28W14 |
SQL Code | -1074L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Parameter 1 | Name of the login mode not included in the current login_mode database option setting. |
Probable Cause | 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. |
| Error 1075 | "Failed to convert from character set '%1' to '%2'" |
|---|---|
Constant | FAILED_TO_CONVERT_CHARSET |
SAP Sybase Error Number | 2744 |
SQL State | WC011 |
SQL Code | -1075L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The character set of the input string. |
Parameter 2 | The character set of the output string. |
Probable Cause | The server failed to convert between the two specified character sets. This could happen when the dbicu and dbicudt DLLs are not installed. |
| Error 1076 | "dbicu libraries are required but not installed" |
|---|---|
Constant | ICU_NOT_AVAILABLE |
SAP Sybase Error Number | 2745 |
SQL State | WC012 |
SQL Code | -1076L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The server is unable to load ICU components that are required by this database. Ensure that the dbicu and dbicudt DLLs are installed. |