Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| 140L | Warning | 2817 | 01005 | "Encryption has not been enabled." | An encryption key was provided, but encryption has not been enabled, nor is the database encrypted. Click here for a list of possible parameters and odbc states. |
| -141L | Error | 2081 | 42W33 | "Table '%1' not found" | 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 "Employees" instead of "DBA"."Employees". Click here for a list of possible parameters and odbc states. |
| 141L | Warning | 2906 | 01006 | "Passthrough SQL script failed" | A passthrough SQL script has failed. Sync your database to report the error to MobiLink. You may need to contact the server administrator. Click here for a list of possible parameters and odbc states. |
| -142L | Error | 2082 | 52W02 | "Correlation name '%1' not found" | You misspelled a correlation name, or you used a table name instead of the correlation name. Click here for a list of possible parameters and odbc states. |
| 142L | Warning | 2921 | WW114 | "UltraLite database state was restored" | The database state was restored from the temporary file. This includes suspended connections, transactions, and cursors. Click here for a list of possible parameters and odbc states. |
| -143L | Error | 2481 | 52003 | "Column '%1' not found" | You misspelled the name of a column, or the column you are looking for is in a different table. Click here for a list of possible parameters and odbc states. |
| 143L | Warning | 2922 | WW115 | "Retrying read of corrupt page (page '%1')" | 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. Click here for a list of possible parameters and odbc states. |
| -144L | Error | 2084 | 52002 | "Column '%1' found in more than one table -- need a correlation name" | You have not put a correlation name on a column that is found in more than one of the tables referenced in a query. You need to add a correlation name to the reference. Click here for a list of possible parameters and odbc states. |
| 144L | Warning | 2923 | WW116 | "Mirror file requires higher checksum_level" | To effectively protect against media failures, page checksums must be enabled when using the mirror file. Specify the checksum_level database creation option. Click here for a list of possible parameters and odbc states. |
| -145L | Error | 2085 | 52W07 | "Foreign key name '%1' not found" | You misspelled the name of a foreign key, or the foreign key does not exist. Click here for a list of possible parameters and odbc states. |
| 145L | Warning | 2943 | 01W27 | "Two rows with the same primary key have been download for table '%1'" | The synchronization scripts are producing duplicate rows with the same primary key in your download. Generally this indicates a problem with the synchronization scripts. No guarantees are made about which of the downloaded rows will be applied to the database. Click here for a list of possible parameters and odbc states. |
| -146L | Error | 2086 | 53W04 | "There is no way to join '%1' to '%2'" | 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. Click here for a list of possible parameters and odbc states. |
| 146L | Warning | 2947 | WE011 | "Event notification queue '%1' is full, notification discarded" | 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. Click here for a list of possible parameters and odbc states. |
| -147L | Error | 2087 | 52W08 | "There is more than one way to join '%1' to '%2'" | 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. Click here for a list of possible parameters and odbc states. |
| 147L | Warning | 2948 | WE012 | "Event notifications lost on queue '%1'" | Event notifications have been lost on the named queue. This occurs if there are pending notifications when the queue is destroyed. The notifications are discarded. Click here for a list of possible parameters and odbc states. |
| -148L | Error | 2091 | 42W05 | "Unknown function '%1'" | You misspelled the name of a database function (such as MAXIMUM instead of MAX) in a query definition or in a query column name. Click here for a list of possible parameters and odbc states. |
| 148L | Warning | 2949 | WE013 | "Event notification queue '%1' not found warning" | The named event notification queue was not found. The operation will be skipped. Click here for a list of possible parameters and odbc states. |
| -149L | Error | 2092 | 53003 | "Function or column reference to '%1' must also appear in a GROUP BY" | 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. In some cases, you may want to use the MAX function on the column name (or another aggregate function) instead of adding the column to the GROUP BY clause. Click here for a list of possible parameters and odbc states. |
| 149L | Warning | 2972 | WW234 | "Automatic database upgrade applied" | The database is from an older version of the software. Automatic database upgrade occurs during startup. Subsequently the database can no longer be opened with the older version of the software. Click here for a list of possible parameters and odbc states. |
| -150L | Error | 2093 | 42W06 | "Invalid use of an aggregate function" | 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. Click here for a list of possible parameters and odbc states. |