Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Warning 140 | "Encryption has not been enabled." |
|---|---|
Constant | ENCRYPTION_NOT_ENABLED_WARNING |
SAP Sybase Error Number | 2817 |
SQL State | 01005 |
SQL Code | 140L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | An encryption key was provided, but encryption has not been enabled, nor is the database encrypted. |
| Error 141 | "Table '%1' not found" |
|---|---|
Constant | TABLE_NOT_FOUND |
SAP Sybase Error Number | 2081 |
SQL State | 42W33 |
SQL Code | -141L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the table that could not be found. |
Probable Cause | You misspelled the name of a table, or you did not qualify a table name with the owner name. For example, you might have referred to "table_name" instead of "owner"."table_name". |
| Error 142 | "Correlation name '%1' not found" |
|---|---|
Constant | CORRELATION_NAME_NOT_FOUND |
SAP Sybase Error Number | 2082 |
SQL State | 52W02 |
SQL Code | -142L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the invalid correlation name. |
Probable Cause | You misspelled a correlation name, or you used a table name instead of the correlation name. |
| Warning 142 | "UltraLite database state was restored" |
|---|---|
Constant | DATABASE_STATE_RESTORED |
SAP Sybase Error Number | 2921 |
SQL State | WW114 |
SQL Code | 142L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | The database state was restored from the temporary file. This includes suspended connections, transactions, and cursors. |
| Error 143 | "Column '%1' not found" |
|---|---|
Constant | COLUMN_NOT_FOUND |
SAP Sybase Error Number | 2481 |
SQL State | 52003 |
SQL Code | -143L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S22 |
Severity Code | |
Parameter 1 | Name of the column that could not be found. |
Probable Cause | You misspelled the name of a column, or the column you are looking for is in a different table. |
| Warning 143 | "Retrying read of corrupt page (page '%1')" |
|---|---|
Constant | CORRUPT_PAGE_READ_RETRY |
SAP Sybase Error Number | 2922 |
SQL State | WW115 |
SQL Code | 143L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The page ID. |
Probable Cause | UltraLite detected a corrupt database page and will attempt the read operation again. If a mirror file is enabled, it is used for the retry. If the retry fails, an error will be signaled. |
| Error 144 | "Column '%1' found in more than one table or it is used more than once in the SELECT list -- it needs a correlation name" |
|---|---|
Constant | COLUMN_AMBIGUOUS |
SAP Sybase Error Number | 2084 |
SQL State | 52002 |
SQL Code | -144L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the ambiguous column. |
Probable Cause | You have not specified a correlation name on a column which is found in more than one of the tables referenced in a query block or which appears more than once in the SELECT list of a query block. You need to add a correlation name to the column. |
| Warning 144 | "Mirror file requires higher checksum_level" |
|---|---|
Constant | MIRROR_FILE_REQUIRES_CHECKSUMS |
SAP Sybase Error Number | 2923 |
SQL State | WW116 |
SQL Code | 144L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | To effectively protect against media failures, page checksums must be enabled when using the mirror file. Specify the checksum_level database creation option. |
| Error 145 | "Foreign key name '%1' not found" |
|---|---|
Constant | FOREIGN_KEY_NAME_NOT_FOUND |
SAP Sybase Error Number | 2085 |
SQL State | 52W07 |
SQL Code | -145L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the non-existing foreign key. |
Probable Cause | You misspelled the name of a foreign key, or the foreign key does not exist. |
| Warning 145 | "Two rows with the same primary key have been downloaded for table '%1'" |
|---|---|
Constant | DUPLICATE_ROW_FOUND_IN_DOWNLOAD |
SAP Sybase Error Number | 2943 |
SQL State | 01W27 |
SQL Code | 145L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Parameter 1 | Name of the table being downloaded. |
Probable Cause | The synchronization scripts are producing duplicate rows with the same primary key in your download. Generally this behavior indicates a problem with the synchronization scripts. No guarantees are made about which of the downloaded rows will be applied to the database. |
| Error 146 | "There is no way to join '%1' to '%2'" |
|---|---|
Constant | CANNOT_JOIN |
SAP Sybase Error Number | 2086 |
SQL State | 53W04 |
SQL Code | -146L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of first table that cannot be joined. |
Parameter 2 | Name of second table that cannot be joined. |
Probable Cause | You may have attempted a KEY JOIN between two tables and there is no foreign key on one of the tables that references the primary key of the other table. You may have attempted a NATURAL JOIN between two tables that have no common column names. |
| Warning 146 | "Event notification queue '%1' is full, notification discarded" |
|---|---|
Constant | EVENT_NOTIFICATION_QUEUE_FULL |
SAP Sybase Error Number | 2947 |
SQL State | WE011 |
SQL Code | 146L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The name of the event notification queue. |
Probable Cause | The named queue is full and will not receive any event notifications until notifications are read from the queue. The pending notification has been discarded. |
| Error 147 | "There is more than one way to join '%1' to '%2'" |
|---|---|
Constant | AMBIGUOUS_JOIN |
SAP Sybase Error Number | 2087 |
SQL State | 52W08 |
SQL Code | -147L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of first table that cannot be joined. |
Parameter 2 | Name of second table that cannot be joined. |
Probable Cause | You are attempting to KEY JOIN two tables, and there are two or more foreign keys relating the two tables. There may be two foreign keys from the first table to the second table. It may be that each table has a foreign key to the other table. You must use a correlation name for the primary key table that is the same as the role name of the desired foreign key relationship. |
| Warning 147 | "Event notifications lost on queue '%1'" |
|---|---|
Constant | EVENT_NOTIFICATIONS_LOST |
SAP Sybase Error Number | 2948 |
SQL State | WE012 |
SQL Code | 147L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The name of the event notification queue. |
Probable Cause | Event notifications have been lost on the named queue. This behavior occurs if there are pending notifications when the queue is destroyed. The notifications are discarded. |
| Error 148 | "Unknown function '%1'" |
|---|---|
Constant | UNKNOWN_FUNC |
SAP Sybase Error Number | 2091 |
SQL State | 42W05 |
SQL Code | -148L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Function name that is not a database function. |
Probable Cause | You misspelled the name of a database function (such as MAXIMUM instead of MAX) in a query definition or in a query column name. |
| Warning 148 | "Event notification queue '%1' not found warning" |
|---|---|
Constant | EVENT_NOTIFICATION_QUEUE_NOT_FOUND_WARN |
SAP Sybase Error Number | 2949 |
SQL State | WE013 |
SQL Code | 148L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The name of the event notification queue. |
Probable Cause | The named event notification queue was not found. The operation will be skipped. |
| Error 149 | "Function or column reference to '%1' must also appear in a GROUP BY" |
|---|---|
Constant | INVALID_GROUP_SELECT |
SAP Sybase Error Number | 2092 |
SQL State | 53003 |
SQL Code | -149L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the column referenced directly, or in an expression, that must be in the GROUP BY clause. |
Probable Cause | You used a non-aggregate function or column reference in the SELECT list or in a nested query block that does not appear in the GROUP BY clause. In a query using GROUP BY, SELECT list items that are not aggregate functions must also appear in the GROUP BY clause. If the SELECT list item is a column reference or an alias, you may add the column name or alias to the GROUP BY clause. If the SELECT list item is a scalar function, ensure that the function's arguments in the GROUP BY clause match exactly with those in the SELECT list. You may be able to use the MAX function (or another aggregate function) on the column name instead of adding the column to the GROUP BY clause. |
| Warning 149 | "Automatic database upgrade applied" |
|---|---|
Constant | DATABASE_UPGRADE_WARNING |
SAP Sybase Error Number | 2972 |
SQL State | WW234 |
SQL Code | 149L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | The database is from an older version of the software. An automatic database upgrade occurs during startup. Subsequently the database can no longer be opened with the older version of the software. |
| Error 150 | "Invalid use of an aggregate function" |
|---|---|
Constant | AGGREGATES_NOT_ALLOWED |
SAP Sybase Error Number | 2093 |
SQL State | 42W06 |
SQL Code | -150L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to use an aggregate function inappropriately. For example, a SELECT statement cannot contain an aggregate function within a predicate in the WHERE clause unless the aggregate function constitutes an outer reference. Other invalid uses include specifying an aggregate function in the SET clause of an UPDATE statement, or using an aggregate function in a CHECK constraint. |
| Warning 150 | "Database contains no tables to synchronize" |
|---|---|
Constant | NO_TABLES_TO_SYNCHRONIZE |
SAP Sybase Error Number | 3173 |
SQL State | 01W28 |
SQL Code | 150L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | The database has no tables to synchronize. No attempt was made to contact the MobiLink server. |