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 |
|---|---|---|---|---|---|
| 01W15 | Warning | 2376 | 117L | "Unsupported character set '%1' and unsupported language '%2'; language used is '%3' instead" | The character set that the application requested is not supported by the server to which the application is connecting. The language that the application requested is not supported either. Language strings will be sent in the language specified. Click here for a list of possible parameters and odbc states. |
| 01W16 | Warning | 2381 | 118L | "Illegal user selectivity estimate specified" | You specified a user selectivity estimate that is either not a literal constant or is outside the range 0.0 to 100.0 (estimates are specified as percentages). The estimate has been ignored. Click here for a list of possible parameters and odbc states. |
| 01W17 | Warning | 2384 | 120L | "'%1' is an unknown option" | You attempted to set the value of an option that is not known to the server. Click here for a list of possible parameters and odbc states. |
| 01W18 | Warning | 2529 | 122L | "The result returned is non-deterministic" | FIRST or TOP n are used in a SELECT statement to limit the size of a result. The statement must also have an ORDER BY if the result is to be well-defined. If it does not have an ORDER BY, then the server is free to return any subset of the result that has the requested number of rows. Click here for a list of possible parameters and odbc states. |
| 01W20 | Warning | 2549 | 129L | "Plan may contain virtual indexes" | Virtual indexes are currently enabled in this connection. Any plans that are generated may contain virtual indexes. Click here for a list of possible parameters and odbc states. |
| 01W21 | Warning | 2559 | 130L | "A row was dropped because it could not be converted to the new schema format" | A row that was valid in the old schema is no longer valid. This could be because a column domain changed and the old value can not be cast to the new domain. Rows are also dropped if a uniqueness or foreign key constraint cannot be satisfied. Click here for a list of possible parameters and odbc states. |
| 01W23 | Warning | 2562 | 132L | "Cannot output the histogram for string column '%1'" | You tried to get the histogram for a column containing strings. Histograms on string information cannot be output in a readable format; as a result, no information was retrieved. Consider using the ESTIMATE function to get information on a specific value or range in the column. Click here for a list of possible parameters and odbc states. |
| 01W24 | Warning | 2690 | 137L | "Row was dropped from table %1 to maintain referential integrity" | A delete of a primary row during download forced its foreign row(s) to be deleted as well to maintain referential integrity Click here for a list of possible parameters and odbc states. |
| 01W25 | Warning | 2761 | 138L | "Publication predicates were not evaluated" | Publication predicates were not evaluated because UltraLite was initialized without SQL support. The table will be uploaded as if no publication predicate was specified for the table. Click here for a list of possible parameters and odbc states. |
| 01W26 | Warning | 2770 | 139L | "Option '%1' specified more than once" | A particular option has been specified multiple times. Only the last instance of the option is used; the previous ones are ignored. Click here for a list of possible parameters and odbc states. |
| 01W27 | Warning | 2943 | 145L | "Two rows with the same primary key have been downloaded 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. |
| 01WC1 | Warning | 2538 | 125L | "An invalid multi-byte input character was encountered when converting from %1 to %2" | While the server was performing character set conversion on an input string, an invalid multi-byte character was encountered. The illegal character was directly copied without conversion. Data following the illegal character may be misinterpreted. See on_charset_conversion_failure option. Click here for a list of possible parameters and odbc states. |
| 01WC3 | Warning | 2542 | 127L | "Character substitution occurred when converting from %1 to %2" | While the server was performing character set conversion on an input string, some characters could not be represented in the database character set. Those characters were substituted. See on_charset_conversion_failure option. Click here for a list of possible parameters and odbc states. |
| 01WC4 | Warning | 2788 | 201L | "The ICU collation '%1' has defaulted to another collation" | The specified ICU collation is not available. Another collation was substituted, which may or may not produce suitable results. Due to the structure of ICU, the collation that was used is not known, but was the best alternative to the specified collation. If this database is used on another platform, a different collation may be chosen and the operation may generate different results. Click here for a list of possible parameters and odbc states. |
| 02000 | Warning | 2001 | 100L | "Row not found" | You positioned a cursor beyond the beginning or past the end of the query. There is no row at that position. Click here for a list of possible parameters and odbc states. |
| 04W07 | Error | 2213 | -604L | "A dbspace has reached its maximum file size" | A dbspace has grown to its maximum number of disk pages, which is usually limited by the maximum operating system file size. This is a fatal error. Click here for a list of possible parameters and odbc states. |
| 04W08 | Error | 2214 | -605L | "The server attempted to access a page beyond the end of the maximum allowable dbspace file size" | The database attempted to access a page whose page number is beyond the maximum possible number of disk pages. This is a fatal internal error. Click here for a list of possible parameters and odbc states. |
| 07001 | Error | 2119 | -188L | "Not enough values for host variables" | You have not provided enough host variables for either the number of bind variables, or the statement, or the number of select list items. Click here for a list of possible parameters and odbc states. |
| 07002 | Error | 2114 | -182L | "Not enough fields allocated in SQLDA" | There are not enough fields in the SQLDA to retrieve all of the values requested. Click here for a list of possible parameters and odbc states. |
| 07003 | Error | 2110 | -171L | "Error opening cursor" | You attempted to open a cursor on a statement that is not SELECT, CALL or EXEC. Click here for a list of possible parameters and odbc states. |