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 |
|---|---|---|---|---|---|
| WJ005 | Error | 2317 | -689L | "Input parameter index out of range" | The range for valid parameters is from 1 up to the number of host variables specified in the prepared/callable statement. Click here for a list of possible parameters and odbc states. |
| WJ006 | Error | 2318 | -690L | "Return value cannot be set" | Setting a value for the return parameter of a callable statement is not allowed. Click here for a list of possible parameters and odbc states. |
| WJ007 | Error | 2321 | -693L | "JDBC feature '%1' not supported" | An attempt was made to use a feature of JDBC that is not supported. Click here for a list of possible parameters and odbc states. |
| WJ008 | Error | 2322 | -694L | "Could not change an opened prepared statement or callable statement" | You attempted to change the SQL statement of an open prepared statement or callable statement. Prepared statements and callable statements must be closed before attempting such changes. Click here for a list of possible parameters and odbc states. |
| WJ009 | Error | 2323 | -695L | "An internal error occurred in a '%1'" | This is an internal JDBC object error. If it can be reproduced, it should be reported to iAnywhere. Click here for a list of possible parameters and odbc states. |
| WJ010 | Error | 2324 | -696L | "Invalid operation on a closed '%1'" | An illegal attempt was made to access a closed JDBC object. Click here for a list of possible parameters and odbc states. |
| WJ011 | Error | 2326 | -701L | "Cannot access instance member through a class" | Non-static fields or methods must be accessed through an object instance. Click here for a list of possible parameters and odbc states. |
| WJ012 | Error | 2327 | -699L | "Cannot update member fields qualified with \"final\" modifier" | An attempt was made to modify a Java member that was qualified with the "final" modifier. Such members are constant and cannot be modified. Click here for a list of possible parameters and odbc states. |
| WJ013 | Error | 2341 | -713L | "An internal error occurred in a '%1'" | This is an internal native Java object error. If it can be reproduced, it should be reported to iAnywhere. Click here for a list of possible parameters and odbc states. |
| WJ014 | Error | 2342 | -714L | "Invalid operation on a closed '%1'" | An illegal attempt was made to access a closed native Java object. Click here for a list of possible parameters and odbc states. |
| WJ015 | Error | 2388 | -742L | "JDBC SAStatement batch execute abandoned" | An error occurred when executing a statement in the batch. The rest of the statements in the batch will be abandoned. Click here for a list of possible parameters and odbc states. |
| WJ016 | Error | 2389 | -743L | "Seek absolute 0 was attempted on a JDBC SAResultSet" | There is no row zero on JDBC resultSets. The valid row numbers are 1, 2, ..., -2, -1. Click here for a list of possible parameters and odbc states. |
| WJ017 | Error | 2393 | -747L | "Invalid JDBC resultset type" | An invalid resultset type was used when creating a JDBC statement. Click here for a list of possible parameters and odbc states. |
| WJ018 | Error | 2394 | -748L | "Invalid JDBC resultset concurrency" | An invalid resultset concurrency was used when creating a JDBC statement. Click here for a list of possible parameters and odbc states. |
| WJ019 | Error | 2398 | -752L | "Cannot call the '%1' function on a JDBC resultset when it is positioned on an insert row" | Some resultset functions such as updateRow and deleteRow are invalid when the cursor of the resultset is positioned at the insert row. Click here for a list of possible parameters and odbc states. |
| WJ020 | Error | 2399 | -753L | "The JDBC resultset must be positioned on an insert row in order to use the '%1' function" | Resultset functions such as insertRow can only be called when the resultset is positioned on the insert row. Click here for a list of possible parameters and odbc states. |
| WJ021 | Error | 2402 | -756L | "Cannot uniquely identify column '%2' of table '%1' in the current JDBC resultset" | Failed to identify a column in a JDBC resultset with the given table name and column name. This can happen if the given names are not found or if they are ambiguous. Click here for a list of possible parameters and odbc states. |
| WJ022 | Error | 2405 | -758L | "The database does not support the Java Virtual Machine" | The Java Virtual Machine could not be started because the database does not have the proper support. It may be that the database was created with an older version of the software, or was created with the Java support disabled. If the database was created with an older version of the software the database should be upgraded to the most recent version. If the database was created with Java support disabled, then the instjava.sql script should be run against the database to enable Java support. Click here for a list of possible parameters and odbc states. |
| WJ023 | Error | 2408 | -762L | "'%1' is not a public Java class, and cannot be referenced from SQL" | Only public Java classes installed into the database are accessible from SQL. Click here for a list of possible parameters and odbc states. |
| WJ024 | Error | 2409 | -763L | "'%1' is not a public Java reference, and cannot be referenced from SQL" | The dotted expression is neither a public Java class nor a Java variable. Click here for a list of possible parameters and odbc states. |