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 |
|---|---|---|---|---|---|
| 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. |
| WW024 | Error | 2385 | -740L | "The communications environment could not be created" | The communications environment could not be created. Either there are insufficient resources to create the environment or the language resource file cannot be found. Click here for a list of possible parameters and odbc states. |
| WW025 | Error | 2455 | -808L | "An internal error was generated by the test harness" | An internal error was generated by the test harness. Click here for a list of possible parameters and odbc states. |
| WW026 | Error | 2465 | -818L | "Version 'V%1' interface used by external function call '%2' is not supported for execution in the current context." | You attempted to call an external function. The attempt to load the associated library failed because of incompatibility with the server. Incompatibility may arise because the dynamic library is using an external function API that is either not supported by the server or is newer than the one supported by the server. It may also arise if the external API is not compatible with the data in the current context. Click here for a list of possible parameters and odbc states. |
| WW027 | Error | 2475 | -828L | "A conflict with the dbmlsync download phase was detected" | Dbmlsync uses this error to detect download phase conflicts with rows modified by other connections. Click here for a list of possible parameters and odbc states. |
| WW028 | Error | 2509 | -860L | "At least one of the specified dbspaces was not calibrated" | You attempted to calibrate a dbspace that was not open or was too small. Click here for a list of possible parameters and odbc states. |
| WW029 | Error | 2606 | -942L | "A workload capture (%1) is already in progress" | You have tried to initiate a workload capture when one is already in progress. You need to wait for the other capture to complete. Click here for a list of possible parameters and odbc states. |
| WW030 | Error | 2607 | -943L | "No workload capture currently exists" | You have tried to stop, pause, resume, or get the status of a workload capture, but no workload captures exist. Click here for a list of possible parameters and odbc states. |
| WW031 | Error | 2615 | -951L | "Cannot access schema file '%1'" | UltraLite requires a schema file to perform the current operation. Either no schema file was specified or the one specified was not accessible or was corrupt. Click here for a list of possible parameters and odbc states. |
| WW032 | Error | 2616 | -952L | "The status of the last synchronization upload is unknown" | The status of the last synchronization upload is unknown. The current operation cannot proceed until a successful upload is synchronized. Click here for a list of possible parameters and odbc states. |
| WW033 | Error | 2617 | -953L | "A schema upgrade is not currently allowed" | A schema upgrade cannot proceed because of concurrent use of the database. For example, all cursors must be closed before a schema upgrade can occur. Click here for a list of possible parameters and odbc states. |