Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 42WCC | Error | 2956 | -1269L | "Service statement definition is invalid or unsupported" | Either the statement provided is invalid or it is unsupported within the context of a service. Click here for a list of possible parameters and odbc states. |
| 42WCD | Error | 2974 | -1286L | "Immediate materialized view definition cannot contain a SUM function over a nullable expression." | You attempted to change the refresh type to immediate for a materialized view whose definition contains a SUM function over a nullable expression. Click here for a list of possible parameters and odbc states. |
| 42WD0 | Error | 2939 | -1256L | "Event of %1 type already exists" | An attempt was made to define a new event of the type that already exists. Click here for a list of possible parameters and odbc states. |
| 42WD1 | Error | 2940 | -1257L | "Multiple event conditions can not be specified with this event type" | An attempt was made to specify more than one condition for an event type. Click here for a list of possible parameters and odbc states. |
| 42WD2 | Error | 2941 | -1258L | "'<' or '<=' operator can only be used in the event condition with this event type" | Event of this type can be defined with a condition having < or <= operator only. Click here for a list of possible parameters and odbc states. |
| 42WD3 | Error | 2957 | -1270L | "Must own table '%1' in order to make an immediate view reference it" | You have attempted to change the refresh type of a materialized view to immediate and the view references a table that is not owned by you. In order to perform this operation, you must either own all the tables referenced by the materialized view or have DBA privileges. Click here for a list of possible parameters and odbc states. |
| 42Z00 | Error | 2755 | -1086L | "Write access was denied" | A write attempt to an UltraLite database in read-only mode was denied. Note that UltraLite databases cannot be modified while sending an upload to MobiLink. Click here for a list of possible parameters and odbc states. |
| 44000 | Error | 2235 | -632L | "WITH CHECK OPTION violated for insert/update on base table '%1'" | You attempted an insert or update operation on the indicated base table through a view (possibly nested). However, one or more values in the modified row(s) triggered a WITH CHECK OPTION violation. This violation occurs when a modified value causes one or more rows to fall outside the range of the view by making the view's WHERE clause evaluate to FALSE or UNKNOWN for that row. Click here for a list of possible parameters and odbc states. |
| 52002 | Error | 2084 | -144L | "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. |
| 52003 | Error | 2481 | -143L | "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. |
| 52004 | Error | 2302 | -163L | "Derived table '%1' has no name for column %2" | The specified column of the derived table has no column name. Use a select list alias in the query specification or use a derived columns specifier. Click here for a list of possible parameters and odbc states. |
| 52005 | Error | 2083 | -834L | "Column '%1' not found in table '%2'" | 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. |
| 52009 | Error | 2056 | -119L | "Primary key column '%1' already defined" | You listed the same column name twice in the definition of a primary key. Click here for a list of possible parameters and odbc states. |
| 52010 | Error | 2047 | -110L | "Item '%1' already exists" | You attempted to create a file, table, view, column, constraint, foreign key, or publication with the same name as an existing one. Click here for a list of possible parameters and odbc states. |
| 52012 | Error | 2079 | -139L | "More than one table is identified as '%1'" | You identified two tables in the same FROM clause with the same correlation name. Click here for a list of possible parameters and odbc states. |
| 52W02 | Error | 2082 | -142L | "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. |
| 52W03 | Error | 2063 | -183L | "Cannot find index named '%1'" | You attempted to perform an operation using an index that does not exist. Check for spelling errors. Check whether the index name must be qualified with a user ID. Click here for a list of possible parameters and odbc states. |
| 52W04 | Error | 2048 | -111L | "Index name '%1' not unique" | You attempted to create an index with the same name as an existing index. Click here for a list of possible parameters and odbc states. |
| 52W05 | Error | 2058 | -126L | "Table cannot have two primary keys" | You specified the primary key twice in a CREATE TABLE statement. Click here for a list of possible parameters and odbc states. |
| 52W06 | Error | 2062 | -251L | "Foreign key '%1' for table '%2' duplicates an existing foreign key" | You attempted to define a foreign key that already exists. Click here for a list of possible parameters and odbc states. |