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 |
|---|---|---|---|---|---|
| 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 was declared with 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. |
| WW017 | Error | 2277 | -651L | "An attempt to delete database '%1' failed" | Your attempt to delete a database file failed. You may have attempted to delete a running database. Some parts of the database may have been deleted before failure. Click here for a list of possible parameters and odbc states. |
| WW018 | Error | 2289 | -663L | "Cannot deserialize Java object" | The persistent Java object cannot be read from the database column. Possibly, the class of the object has been removed or modified. Click here for a list of possible parameters and odbc states. |
| WW019 | Error | 2313 | -684L | "Rollback occurred due to deadlock during prefetch" | One of the cursors that was opened with prefetch enabled was performing fetch operations, and a deadlock occurred during a prefetch. This is a deadlock situation and your transaction has been chosen as the one to rollback. The request that received this error was not executed, unless the request was to close the cursor, in which case the cursor was closed. Click here for a list of possible parameters and odbc states. |
| WW020 | Error | 2667 | -999L | "Invalid request log format on line %1" | The request log file format is invalid. The request log may have been created with an older version of the software. Click here for a list of possible parameters and odbc states. |
| WW022 | Error | 2332 | -704L | "Cannot create an index on Java class '%1'" | An operation requiring an index was attempted in which an attempt was made to create an index on a Java class type. Click here for a list of possible parameters and odbc states. |
| WW023 | Error | 2331 | -703L | "Cannot insert or update computed column '%1'" | Computed column values cannot be modified explicitly. Their value is determined implicitly from the computed expression value. Click here for a list of possible parameters and odbc states. |