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 |
|---|---|---|---|---|---|
| WQ021 | Error | 3225 | -1583L | "Cannot upgrade the database. The database can be upgraded only after starting the coordinator in single node mode." | In order to run ALTER DATABASE UPGRADE on the database, the coordinator must be started in single node mode using the '-iqmpx_sn 1' server startup option. Click here for a list of possible parameters and odbc states. |
| WT001 | Error | 2832 | -1156L | "Argument \"%1\" must be a column reference." | The CONTAINS argument must be a column reference. Click here for a list of possible parameters and odbc states. |
| WT002 | Error | 2833 | -1157L | "All column reference arguments must refer to the same table." | All column references in a CONTAINS query must refer to the same table. Click here for a list of possible parameters and odbc states. |
| WT003 | Error | 2834 | -1158L | "No matching text index." | A single text index must exist on all columns referenced in a CONTAINS query. Click here for a list of possible parameters and odbc states. |
| WT004 | Error | 2835 | -1159L | "Non-constant or unknown text query string." | The query string argument to a CONTAINS query must be a constant, or a non-null value in a variable. Click here for a list of possible parameters and odbc states. |
| WT005 | Error | 2836 | -1160L | "Text configuration \"%1\".\"%2\" not found." | The specified text configuration does not exist. Click here for a list of possible parameters and odbc states. |
| WT006 | Error | 2837 | -1161L | "Text configuration \"%1\" already exists." | The specified text configuration name already exists. Click here for a list of possible parameters and odbc states. |
| WT007 | Error | 2838 | -1162L | "Term length outside allowed range." | The minimum and maximum term lengths must both be greater than 0 and less than or equal to 60 characters. Click here for a list of possible parameters and odbc states. |
| WT008 | Error | 2839 | -1163L | "Invalid collation: \"%1\"." | The collation was not found, or the tailoring options were invalid. Click here for a list of possible parameters and odbc states. |
| WT009 | Error | 2840 | -1164L | "Text query parser error: %1" | The text query could not be parsed. Click here for a list of possible parameters and odbc states. |
| WT010 | Error | 2841 | -1165L | "Error creating text index \"%1\" on table \"%2\No message | There was an internal error creating a text index. Click here for a list of possible parameters and odbc states. |
| WT011 | Error | 2842 | -1166L | "Text indexes are not supported for this database." | The current database does not have catalog support for text indexes. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |
| WT012 | Error | 2844 | -1168L | "Cannot alter or drop a text configuration referenced by a text index." | It is not possible to alter or drop a text configuration referenced by a populated text index or currently being used by a text procedure. Either copy the configuration and alter the copy, or close all cursors on text procedures and truncate all indexes that use the configuration. Click here for a list of possible parameters and odbc states. |
| WT013 | Error | 2846 | -1169L | "Cannot access a table that is part of a text index." | It is not possible to directly manipulate tables created as part of a text index. Click here for a list of possible parameters and odbc states. |
| WT014 | Error | 2851 | -1174L | "Cannot create text configuration '%1' because option '%2' has an inappropriate setting" | You attempted an operation that needs to create or alter the database options settings for a text configuration, but one of the options is currently set to a value not permitted for a text configuration. Click here for a list of possible parameters and odbc states. |
| WT015 | Error | 2859 | -1182L | "Statement not allowed on IMMEDIATE REFRESH text index" | You cannot use REFRESH TEXT INDEX or TRUNCATE TEXT INDEX on an index that is created with immediate refresh. You cannot alter a text index to use or stop using immediate refresh. Click here for a list of possible parameters and odbc states. |
| WT016 | Error | 2884 | -1207L | "Invalid use of NEAR operator in text query." | Only terms, prefixes, or other NEAR operators are allowed as arguments to a NEAR operator. Click here for a list of possible parameters and odbc states. |
| WT017 | Error | 2894 | -1216L | "The arguments to this procedure must be literal strings." | This procedure only accepts literal strings as arguments. Click here for a list of possible parameters and odbc states. |
| WT018 | Error | 2920 | -1240L | "The provided stoplist is too long." | A text configuration stop list must be less than 8000 bytes. Click here for a list of possible parameters and odbc states. |
| WT019 | Error | 2936 | -1253L | "The text index %1 needs to be refreshed" | There is a text index that matches the query, but it needs to be refreshed before it is used. Click here for a list of possible parameters and odbc states. |