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 |
|---|---|---|---|---|---|
| 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. |
| WJ025 | Error | 2489 | -842L | "JDK '%1' is not a supported JDK" | Either the JDK version specified in the CREATE DATABASE statement is unsupported or the version in the manifest file of the JDK JAR file is unsupported. Click here for a list of possible parameters and odbc states. |
| WJ026 | Error | 2488 | -841L | "The JDK version in '%1' does not match '%2'" | The JDK version specified in the CREATE DATABASE statement does not match the JDK version in the JDK JAR file. Click here for a list of possible parameters and odbc states. |
| WJ027 | Error | 2494 | -847L | "Java SecurityManager class not found: %1" | The class specified is either not a SecurityManager subclass or cannot be found. Click here for a list of possible parameters and odbc states. |
| WJ028 | Error | 2495 | -848L | "Exception occurred while loading Java SecurityManager" | A Java exception occurred while loading the Java SecurityManager for this connection. Click here for a list of possible parameters and odbc states. |
| WJ029 | Error | 2521 | -871L | "The database needs to be restarted for this Java related command" | Java support in the database requires a database restart after some Java related commands are performed, for example, some Java commands like ALTER DATABASE UPGRADE JAVA ON require a restart before one performs any Java related commands that load a Java class into the database. Click here for a list of possible parameters and odbc states. |
| WJ030 | Error | 2882 | -1205L | "External environment '%1' could not be found" | You attempted to define an object for an external environment that has not been added. Click here for a list of possible parameters and odbc states. |
| WJ031 | Error | 2891 | -1213L | "External environment does not support result sets" | You attempted to define dynamic result sets for an external environment that does not support result sets. Click here for a list of possible parameters and odbc states. |
| WL001 | Error | 2209 | -601L | "'%1' is not a known file format for loading or unloading tables" | An unsupported file format was specified for LOAD TABLE or UNLOAD TABLE. Click here for a list of possible parameters and odbc states. |
| WL002 | Error | 2210 | -602L | "Cannot access file '%1' -- %2" | A file cannot be accessed. For example, a file referenced by LOAD TABLE does not exist or cannot be read. The message will contain the reason for the error. Click here for a list of possible parameters and odbc states. |
| WL004 | Error | 2212 | -643L | "UNLOAD TABLE cannot be used to unload a view" | UNLOAD TABLE was specified with the name of a view. UNLOAD TABLE may only be used to unload tables. Click here for a list of possible parameters and odbc states. |
| WL005 | Error | 2450 | -803L | "Unable to enlist transaction; DTC may be down" | You tried to enlist a transaction but DTC does not seem to be available at this time. Click here for a list of possible parameters and odbc states. |
| WL006 | Error | 2451 | -804L | "Unable to reenlist transaction; DTC may be down" | You tried to recover a transaction but DTC does not seem to be available at this time. Click here for a list of possible parameters and odbc states. |
| WL007 | Error | 2660 | -993L | "LOAD TABLE not allowed on temporary table with ON COMMIT DELETE ROWS" | The LOAD TABLE statement automatically commits at completion. If a temporary table being loaded was declared with ON COMMIT DELETE ROWS, the rows are discarded at completion. Click here for a list of possible parameters and odbc states. |
| WL008 | Error | 2704 | -1035L | "LOAD TABLE not permitted on mirrored database" | LOAD TABLE statements are not permitted when a database is being mirrored, since the file being loaded might not be accessible by the other server. Click here for a list of possible parameters and odbc states. |
| WL009 | Error | 2820 | -1146L | "LOAD TABLE not allowed on temporary table which has foreign key references from another table" | The LOAD TABLE statement removes all rows in a temporary table upon failure. If a temporary table being loaded caused an error then the foreign rows would be orphaned. Click here for a list of possible parameters and odbc states. |
| WL010 | Error | 2827 | -1151L | "The logging type ( '%1' ) specified is invalid, not supported or incompatible" | The logging type specified for LOAD TABLE is not supported for the version of the database being used, is incompatible with other specifications of the statement or is not supported for the specific table being loaded into. Click here for a list of possible parameters and odbc states. |