Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Warning 106 | "Value for column '%1' in table '%2' has changed" |
|---|---|
Constant | COLUMN_VALUE_CHANGED |
SAP Sybase Error Number | 2007 |
SQL State | 01W06 |
SQL Code | 106L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Name of the column whose value has changed. |
Parameter 2 | Name of the table containing the column. |
Probable Cause | A replicated UPDATE has found a value in an updated column that does not match the value when the original UPDATE was made. |
| Error 106 | "Cannot open transaction log file -- %1" |
|---|---|
Constant | CANNOT_OPEN_LOG |
SAP Sybase Error Number | 2043 |
SQL State | 08W05 |
SQL Code | -106L |
ODBC 2 State | 08003 |
ODBC 3 State | 08003 |
Severity Code | |
Parameter 1 | Reason why the transaction log file cannot be opened. |
Probable Cause | The database server was unable to open the named transaction log file. The transaction log file name may include an invalid device or directory. If this is the case, you can use the Transaction Log utility (dblog) to find out where the transaction log should be and perhaps change it. |
| Error 107 | "Error writing to transaction log file" |
|---|---|
Constant | ERROR_WRITING_LOG |
SAP Sybase Error Number | 2044 |
SQL State | 08W17 |
SQL Code | -107L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The database server got an I/O error writing the transaction log file. The disk may be full or the log file name could be invalid. |
| Warning 107 | "Language extension detected in syntax near '%1' on line %2" |
|---|---|
Constant | SYNTAX_EXTENSION_WARNING |
SAP Sybase Error Number | 2238 |
SQL State | 01W07 |
SQL Code | 107L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | The word or symbol where the syntax has been detected. |
Parameter 2 | Line number. |
Probable Cause | The statement you are executing contains syntax that is not allowed with the current setting of the option SQL_FLAGGER_WARNING_LEVEL. Modify the offending statement or set the SQL_FLAGGER_WARNING_LEVEL option to a different value. |
| Error 108 | "Connection not found" |
|---|---|
Constant | CONNECTION_NOT_FOUND |
SAP Sybase Error Number | 2045 |
SQL State | 08W02 |
SQL Code | -108L |
ODBC 2 State | 08003 |
ODBC 3 State | 08003 |
Severity Code | |
Probable Cause | The specified connection name on a DISCONNECT or SET CONNECTION statement is invalid. |
| Error 109 | "There are still active database connections" |
|---|---|
Constant | STILL_ACTIVE_CONNECTIONS |
SAP Sybase Error Number | 2046 |
SQL State | 08W06 |
SQL Code | -109L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to shut down a database that still has active connections. |
| Warning 109 | "Null value eliminated in aggregate function" |
|---|---|
Constant | NULL_VALUE_ELIMINATED |
SAP Sybase Error Number | 2241 |
SQL State | 01003 |
SQL Code | 109L |
ODBC 2 State | 01000 |
ODBC 3 State | 01003 |
Severity Code | |
Probable Cause | The expression argument of the aggregate function evaluated to NULL for one or more rows. |
| Error 110 | "Item '%1' already exists" |
|---|---|
Constant | NAME_NOT_UNIQUE |
SAP Sybase Error Number | 2047 |
SQL State | 52010 |
SQL Code | -110L |
ODBC 2 State | S0001 |
ODBC 3 State | 42S01 |
Severity Code | |
Parameter 1 | Name of the item that already exists. |
Probable Cause | You attempted to create a file, table, view, column, constraint, foreign key, or publication with the same name as an existing one. |
| Warning 110 | "Transaction log backup page only partially full" |
|---|---|
Constant | BACKUP_PAGE_INCOMPLETE |
SAP Sybase Error Number | 2249 |
SQL State | 01W10 |
SQL Code | 110L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | A DB_LOG_BACKUP_READ_WAIT was issued against the transaction log and the page returned was not full. The application should reissue the request for the same page. |
| Warning 111 | "Statement cannot be executed" |
|---|---|
Constant | CANNOT_EXECUTE_STMT |
SAP Sybase Error Number | 2008 |
SQL State | 01W08 |
SQL Code | 111L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | You specified a SQL statement for the PREPARE...WITH EXECUTE statement that cannot be executed. If you specified an output SQLDA, it may contain a DESCRIBE of the prepared statement. It is normal for this warning to appear in the request log during the successful execution of a statement. |
| Error 111 | "Index name '%1' not unique" |
|---|---|
Constant | INDEX_NAME_NOT_UNIQUE |
SAP Sybase Error Number | 2048 |
SQL State | 52W04 |
SQL Code | -111L |
ODBC 2 State | S0011 |
ODBC 3 State | 42S11 |
Severity Code | |
Parameter 1 | Name of the invalid index. |
Probable Cause | You attempted to create an index with the same name as an existing index. |
| Error 112 | "Table already has a primary key" |
|---|---|
Constant | EXISTING_PRIMARY_KEY |
SAP Sybase Error Number | 2049 |
SQL State | 55013 |
SQL Code | -112L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to add a primary key on a table that already has a primary key defined. You must delete the current primary key before adding a new one. |
| Warning 112 | "More information required" |
|---|---|
Constant | MORE_INFO |
SAP Sybase Error Number | 2252 |
SQL State | 01W09 |
SQL Code | 112L |
ODBC 2 State | 37000 |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | More information is required to complete the request. This is used internally in the database interface library to process a unified login. It should not be returned to an application. |
| Error 113 | "Column '%1' in foreign key has a different definition than primary key" |
|---|---|
Constant | INVALID_FOREIGN_KEY_DEF |
SAP Sybase Error Number | 2050 |
SQL State | 53030 |
SQL Code | -113L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the problematic column. |
Probable Cause | The data type of the column in the foreign key is not the same as the data type of the column in the primary key. Change the definition of one of the columns using ALTER TABLE. |
| Warning 113 | "Database option '%1' for user '%2' has an invalid setting" |
|---|---|
Constant | INVALID_OPTION_ON_CONNECT |
SAP Sybase Error Number | 2255 |
SQL State | 01W11 |
SQL Code | 113L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | Name of the database option that has the invalid value. |
Parameter 2 | Name of the user attempting to connect. |
Probable Cause | Upon processing a connection request for a specific user, the server processed a database option that has an invalid setting. The server will use the default option value. |
| Error 114 | "Number of columns defined for the view does not match SELECT statement" |
|---|---|
Constant | VIEW_DEFINITION_ERROR |
SAP Sybase Error Number | 2051 |
SQL State | 53011 |
SQL Code | -114L |
ODBC 2 State | 21S02 |
ODBC 3 State | 21S02 |
Severity Code | |
Probable Cause | You attempted to create a view, but the column list specified as part of the CREATE VIEW statement does not correspond to the list of items in the view's SELECT statement. |
| Warning 114 | "Character set conversion to '%1' cannot be performed; '%2' is used instead" |
|---|---|
Constant | CANNOT_PERFORM_CHAR_TRANSLATION |
SAP Sybase Error Number | 2350 |
SQL State | 01W12 |
SQL Code | 114L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | Name of character set the application requested. |
Parameter 2 | Name of character set the database will be using. |
Probable Cause | The server is unable to perform a character conversion from the character set the database is using to the character set the application requested. |
| Warning 115 | "Database server cannot convert data from/to character set '%1', conversion may not be correct" |
|---|---|
Constant | UNSUPPORTED_CHARACTER_SET_WARNING |
SAP Sybase Error Number | 2360 |
SQL State | 01W13 |
SQL Code | 115L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | Name of the requested character set. |
Probable Cause | The database server cannot convert character data from/to the character set requested by the application because the character set is not supported. The connection succeeds, but character conversion may not be correct for all characters. |
| Error 116 | "Table must be empty" |
|---|---|
Constant | TABLE_MUST_BE_EMPTY |
SAP Sybase Error Number | 2053 |
SQL State | 55W02 |
SQL Code | -116L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to modify a table, and the database server can only perform the change if there are no rows in the table. |
| Warning 116 | "Language '%1' is not supported, '%2' will be used" |
|---|---|
Constant | UNSUPPORTED_LANGUAGE |
SAP Sybase Error Number | 2375 |
SQL State | 01W14 |
SQL Code | 116L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | Name of the language that was requested by the client. |
Parameter 2 | Name of the language that the server will use to send message strings. |
Probable Cause | The language that the application requested is not supported by the server to which the application is connecting. Instead, the server will send message strings in the language stated. |