Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Warning 117 | "Unsupported character set '%1' and unsupported language '%2'; language used is '%3' instead" |
|---|---|
Constant | UNSUPPORTED_CHARSET_AND_LANGUAGE |
SAP Sybase Error Number | 2376 |
SQL State | 01W15 |
SQL Code | 117L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | Name of the character set that could not be supported. |
Parameter 2 | Name of the language that could not be supported. |
Parameter 3 | Name of the language that the server will use to send language strings. |
Probable Cause | The character set that the application requested is not supported by the server to which the application is connecting. The language that the application requested is not supported either. Language strings will be sent in the language specified. |
| Error 118 | "Table '%1' has no primary key" |
|---|---|
Constant | NO_PRIMARY_KEY |
SAP Sybase Error Number | 2055 |
SQL State | 55008 |
SQL Code | -118L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the table that does not have a primary key. |
Probable Cause | You attempted an operation that required the referenced table to have a primary key. Examples of these operations include adding a foreign key, or using the ON EXISTING clause of an INSERT statement, while referring to a table that does not have a primary key. You must add a primary key to the referenced table. |
| Warning 118 | "Illegal user selectivity estimate specified" |
|---|---|
Constant | INVALID_USER_ESTIMATE |
SAP Sybase Error Number | 2381 |
SQL State | 01W16 |
SQL Code | 118L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Probable Cause | You specified a user selectivity estimate that is either not a literal constant or is outside the range 0.0 to 100.0 (estimates are specified as percentages). The estimate has been ignored. |
| Error 119 | "Primary key column '%1' already defined" |
|---|---|
Constant | PRIMARY_KEY_COLUMN_DEFINED |
SAP Sybase Error Number | 2056 |
SQL State | 52009 |
SQL Code | -119L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the column that is already in the primary key. |
Probable Cause | You listed the same column name twice in the definition of a primary key. |
| Warning 119 | "Unable to open backup log '%1'" |
|---|---|
Constant | UNABLE_TO_OPEN_BACKUP_LOG |
SAP Sybase Error Number | 2412 |
SQL State | WB011 |
SQL Code | 119L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Backup log file name. |
Probable Cause | The server was unable to open the backup log to record the execution of a BACKUP or RESTORE statement. Check the settings of the environment variables used to locate the backup log file. The directory to contain the log must already exist. |
| Error 120 | "User '%1' already has GRANT OPTION" |
|---|---|
Constant | ALREADY_HAS_GRANT_PERMS |
SAP Sybase Error Number | 2065 |
SQL State | 42W01 |
SQL Code | -120L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the user that already has GRANT OPTION. |
Probable Cause | You attempted to give GRANT OPTION to a user that already has it. |
| Warning 120 | "'%1' is an unknown option" |
|---|---|
Constant | UNKNOWN_OPTION |
SAP Sybase Error Number | 2384 |
SQL State | 01W17 |
SQL Code | 120L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | The option that is unknown to the server. |
Probable Cause | You attempted to set the value of an option that is not known to the server. |
| Error 121 | "Permission denied: %1" |
|---|---|
Constant | PERMISSION_DENIED |
SAP Sybase Error Number | 2066 |
SQL State | 42501 |
SQL Code | -121L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Description of the type of permission required. |
Probable Cause | You do not have the required permission to perform the specified action. The message specifies the actual permission required and the object being acted upon. |
| Warning 121 | "Cursor option values changed" |
|---|---|
Constant | CURSOR_OPTIONS_CHANGED |
SAP Sybase Error Number | 2500 |
SQL State | 01S02 |
SQL Code | 121L |
ODBC 2 State | 01S02 |
ODBC 3 State | 01S02 |
Severity Code | |
Probable Cause | The database server could not support the requested cursor option values for the associated query. Similar option settings were substituted. |
| Error 122 | "Operation would cause a group cycle" |
|---|---|
Constant | GROUP_CYCLE |
SAP Sybase Error Number | 2067 |
SQL State | 42W02 |
SQL Code | -122L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to add a member to group that would result in a member belonging to itself. The membership may be direct or indirect. |
| Warning 122 | "The result returned is non-deterministic" |
|---|---|
Constant | NONDETERMINISTIC_RESULT |
SAP Sybase Error Number | 2529 |
SQL State | 01W18 |
SQL Code | 122L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Probable Cause | FIRST or TOP n are used in a SELECT statement to limit the size of a result. The statement must also have an ORDER BY if the result is to be well-defined. If it does not have an ORDER BY, then the server is free to return any subset of the result that has the requested number of rows. |
| Error 123 | "User '%1' is not a user group" |
|---|---|
Constant | NOT_A_GROUP |
SAP Sybase Error Number | 2068 |
SQL State | 42W03 |
SQL Code | -123L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of user you thought was a group. |
Probable Cause | You attempted to add a member to group, but the user ID specified as a group has not been granted GROUP permission. |
| Warning 124 | "Invalid data conversion: NULL was inserted for column '%1' on row %2" |
|---|---|
Constant | CANNOT_CONVERT_LOAD_TABLE |
SAP Sybase Error Number | 2532 |
SQL State | 01W01 |
SQL Code | 124L |
ODBC 2 State | 07006 |
ODBC 3 State | 07006 |
Severity Code | |
Parameter 1 | Name of the column where NULL was inserted. |
Parameter 2 | Row number in the data file where the invalid data conversion took place. |
Probable Cause | The database could not convert a value to the required type. The value being converted was supplied to the database in a data file and inserted using LOAD TABLE. A NULL value has been inserted into the column. |
| Error 124 | "Dropping all columns from table '%1' is not allowed" |
|---|---|
Constant | TOO_MANY_COLUMNS_DELETED |
SAP Sybase Error Number | 2253 |
SQL State | 42W44 |
SQL Code | -124L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the table from which the columns could not be dropped. |
Probable Cause | The number of columns in a table can never fall below one. Your ALTER TABLE has more drop/delete column clauses than the current number of columns in the table. |
| Error 125 | "ALTER clause conflict" |
|---|---|
Constant | ALTER_CLAUSE_CONFLICT |
SAP Sybase Error Number | 2057 |
SQL State | 53W01 |
SQL Code | -125L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A primary key clause, foreign key clause, or a uniqueness clause must be the only clause of an ALTER TABLE statement. |
| Warning 125 | "An invalid multi-byte input character was encountered when converting from %1 to %2" |
|---|---|
Constant | ILLEGAL_MULTIBYTE_WARNING |
SAP Sybase Error Number | 2538 |
SQL State | 01WC1 |
SQL Code | 125L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | The character set of the input string. |
Parameter 2 | The character set of the output string. |
Probable Cause | While the server was performing character set conversion on an input string, an invalid multi-byte character was encountered. The illegal character was directly copied without conversion. Data following the illegal character may be misinterpreted. See on_charset_conversion_failure option. |
| Error 126 | "Table cannot have two primary keys" |
|---|---|
Constant | PRIMARY_KEY_TWICE |
SAP Sybase Error Number | 2058 |
SQL State | 52W05 |
SQL Code | -126L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You specified the primary key twice in a CREATE TABLE statement. |
| Error 127 | "Cannot alter a column in an index" |
|---|---|
Constant | COLUMN_IN_INDEX |
SAP Sybase Error Number | 2059 |
SQL State | 53W05 |
SQL Code | -127L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You may have attempted to delete or modify the definition of a column that is part of a primary or foreign key. You may have attempted to delete a column that has an index on it. In this case, DROP the index or key, perform the ALTER statement, and then add the index or key again. |
| Warning 127 | "Character substitution occurred when converting from %1 to %2" |
|---|---|
Constant | SIMPLE_SUBSTITUTION_WARNING |
SAP Sybase Error Number | 2542 |
SQL State | 01WC3 |
SQL Code | 127L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | The character set of the input string. |
Parameter 2 | The character set of the output string. |
Probable Cause | While the server was performing character set conversion on an input string, some characters could not be represented in the database character set. Those characters were substituted. See on_charset_conversion_failure option. |
| Error 128 | "Cannot drop a user that owns tables in runtime system" |
|---|---|
Constant | USER_OWNS_TABLES |
SAP Sybase Error Number | 2060 |
SQL State | 55W03 |
SQL Code | -128L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to drop a user that owns tables while running the runtime server. This operation would result in dropping tables. The runtime server cannot drop tables. Use the full server. |