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 |
|---|---|---|---|---|---|
| WT031 | Error | 2644 | -1493L | "Could not create a text index with external prefilter library on column \"%1\No message | Text configuration object without external prefilter library is required if any column in the text index is not of binary or string data type. Click here for a list of possible parameters and odbc states. |
| WT032 | Error | 2642 | -1504L | "Error from external library: -%1 : %2" | External library used by the text index has reported the specified error. Click here for a list of possible parameters and odbc states. |
| WT033 | Error | 2596 | -1511L | "Text indexes are not allowed across server types." | Text indexes are not allowed across server types if query is processed in full-passthru mode. Click here for a list of possible parameters and odbc states. |
| WT034 | Error | 2561 | -1512L | "Text index with external prefilter cannot contain both binary and string columns" | One or more but not all of the columns specified for the text index is of type binary, and the text configuration object has a prefilter library specified. Text indexes using a prefilter library are allowed to contain either binary columns or string data type columns, but not both. Click here for a list of possible parameters and odbc states. |
| WW001 | Error | 2215 | -606L | "The pattern is too long" | The pattern for the LIKE operator is too long. All patterns of 126 characters or less are supported. Some patterns as long as 254 characters are supported, depending on their contents. Patterns longer than 254 characters are not supported. Click here for a list of possible parameters and odbc states. |
| WW002 | Error | 2216 | -607L | "Cannot stop the database server" | The server has determined that it cannot be shut down at this time. Normally, this error should not occur. Click here for a list of possible parameters and odbc states. |
| WW003 | Error | 2220 | -617L | "Calling functions outside the database server is not supported" | You attempted to call a stored procedure that, in turn, calls a function in a dynamically loaded module. The operating system on which this stored procedure was called does not support such an action. Click here for a list of possible parameters and odbc states. |
| WW004 | Error | 2221 | -618L | "Mismatch between external function platform specifier and current operating system" | A call to an external entry point in a dynamically loaded module was qualified by an operating system that was not the operating system on which the server is currently executing. Click here for a list of possible parameters and odbc states. |
| WW005 | Error | 2222 | -619L | "Need a dynamic library name" | You must provide a library name specifier in the name of the external function to call. Click here for a list of possible parameters and odbc states. |
| WW006 | Error | 2223 | -620L | "Could not load dynamic library '%1'" | This error is usually caused by a failure to load a dynamic library named in an external function call. Click here for a list of possible parameters and odbc states. |
| WW007 | Error | 2224 | -621L | "Could not find '%1' in dynamic library '%2'" | The external function could not be found in the dynamic library. Click here for a list of possible parameters and odbc states. |
| WW008 | Error | 2225 | -622L | "Could not allocate resources to call external function" | The external function could not be called due to a shortage of operating system resources. If the operating system supports threads, the maximum thread count should be increased. Click here for a list of possible parameters and odbc states. |
| WW009 | Error | 2227 | -624L | "Expression has unsupported data type" | Either an external function or Java method is declared to have a parameter or result data type that is not supported, or a Java field reference with an unsupported result type was attempted. Click here for a list of possible parameters and odbc states. |
| WW010 | Error | 2228 | -625L | "Too many parameters to this external procedure call" | There is a maximum of 256 parameters to an external function call in 32-bit Windows. Click here for a list of possible parameters and odbc states. |
| WW011 | Error | 2229 | -626L | "A thread used internally could not be started" | This is a Windows 95 specific error. An operating system thread could not be started that is required to execute external functions. Click here for a list of possible parameters and odbc states. |
| WW012 | Error | 2234 | -631L | "RAISERROR executed: %1" | A RAISERROR statement has been executed. The string associated with the RAISERROR statement is included in the text of the error message. Click here for a list of possible parameters and odbc states. |
| WW013 | Error | 2273 | -93L | "Class '%1' has no public field '%2'" | An expression referenced a field that either does not exist or is not public. Click here for a list of possible parameters and odbc states. |
| WW014 | Error | 2274 | -94L | "Invalid type for field reference" | An expression attempted to reference a field or a method of a non-Java value. Field references via . and >> are only valid when applied to Java objects. Click here for a list of possible parameters and odbc states. |
| WW015 | Error | 2275 | -649L | "Field '%1' of class '%2' cannot be NULL" | An attempt was made to store a SQL NULL value in a Java object field that has a Java type that cannot be NULL. For example, the Java 'int' type cannot be NULL. Click here for a list of possible parameters and odbc states. |
| WW016 | Error | 2276 | -650L | "Index type specification of '%1' is invalid" | IQ index types can be specified for IQ indexes only. In UltraLite, you cannot specify indexes on LONG column types. Click here for a list of possible parameters and odbc states. |