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 |
|---|---|---|---|---|---|
| 42WC6 | Error | 2876 | -1199L | "The materialized view cannot be changed to immediate because COUNT(*) is required to be part of the SELECT list." | You attempted to change the refresh type to immediate for a materialized view whose definition does not include COUNT(*) in the SELECT list. Click here for a list of possible parameters and odbc states. |
| 42WC7 | Error | 2896 | -1218L | "The materialized view cannot be changed to immediate because it does not have a unique index on non-aggregate non-nullable columns" | You attempted to change the refresh type to immediate for a materialized view which does not have a unique index on non-aggregate non-nullable columns. Create a unique index on the materialized view before changing the refresh type. Click here for a list of possible parameters and odbc states. |
| 42WC8 | Error | 2897 | -1219L | "Maintenance of dependent immediate materialized view(s) failed" | Maintenance of immediate materialized view(s) dependent on the base table failed. Click here for a list of possible parameters and odbc states. |
| 42WC9 | Error | 2911 | -1232L | "Attempt to start a second snapshot in a transaction" | A transaction tried to start a snapshot (e.g., see BEGIN SNAPSHOT statement) while another snapshot was already active. Click here for a list of possible parameters and odbc states. |
| 42WCA | Error | 2912 | -1233L | "The materialized view %1 cannot be changed to immediate because it does not have a unique index on non-nullable columns." | You attempted to change the refresh type to immediate for a materialized view which does not have a unique index on non-nullable columns. Create a unique index on the materialized view before changing the refresh type. Click here for a list of possible parameters and odbc states. |
| 42WCB | Error | 2955 | -1268L | "The materialized view cannot be changed to immediate because its definition contains an illegal construct." | You attempted to change the refresh type to immediate for a materialized view whose definition contains an illegal construct. Click here for a list of possible parameters and odbc states. |
| 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. |
| 42WE0 | Error | 2823 | -1330L | "The function '%1' does not allow use of the '%2' clause" | You have attempted to use the specified SQL clause within the context of a function that does not permit such use. Note that the function may have been used directly in the query or indirectly within a named window. Click here for a list of possible parameters and odbc states. |
| 42WE1 | Error | 2807 | -1331L | "The function '%1' requires the use of the '%2' clause" | You have attempted to invoke the specified function without the use of a mandatory SQL clause within the context of the function. Note that the function may have been used directly in the query or indirectly within a named window. Click here for a list of possible parameters and odbc states. |
| 42WE5 | Error | 2681 | -1398L | "VERIFY and RENAME cannot be used together in a RESTORE statement" | Since VERIFY will never write to any dbspaces, renaming dbspaces cannot be done during restore verification. 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. |