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 |
|---|---|---|---|---|---|
| WP003 | Error | 2278 | -652L | "Could not decompress class '%1' from JAR" | The Java runtime library must be installed to extract class files from ZIP or JAR files. Click here for a list of possible parameters and odbc states. |
| WP004 | Error | 2279 | -653L | "Cannot remove class '%1': member of JAR" | You attempted to remove a class file that is still part of a JAR. (It must be removed with the JAR.) Click here for a list of possible parameters and odbc states. |
| WP005 | Error | 2296 | -670L | "Invalid class byte code" | A binary expression passed to the INSTALL JAVA statement was not a valid Java class. Click here for a list of possible parameters and odbc states. |
| WP006 | Error | 2301 | -675L | "External environment could not be started, '%1' could not be found" | A problem was encountered starting the External Environment. A component that is needed to run the environment could not be found. Click here for a list of possible parameters and odbc states. |
| WP007 | Error | 2310 | -164L | "Namespace heap exhausted at internal function: %1" | The amount of space allocated for the Java Namespace is insufficient to continue loading Java classes. Increase the size by using: SET OPTION PUBLIC.java_namespace_size = nnnnnnnn. Click here for a list of possible parameters and odbc states. |
| WP008 | Error | 2311 | -165L | "Java VM heap exhausted at internal function: %1" | The amount of space allocated for the Java VM is insufficient to continue allocating new objects. Increase the size by using: SET OPTION PUBLIC.java_heap_size = nnnnnnnn. Click here for a list of possible parameters and odbc states. |
| WP009 | Error | 2314 | -685L | "Resource governor for '%1' exceeded" | The resource governor for the stated resource has determined that the usage of the resource has exceeded its limit. Click here for a list of possible parameters and odbc states. |
| WP010 | Error | 2374 | -730L | "Invalid JAR file" | A file passed to the INSTALL JAVA statement was not a valid JAR file. Click here for a list of possible parameters and odbc states. |
| WP011 | Error | 2472 | -825L | "Previous error lost before RESIGNAL" | A RESIGNAL statement in an exception handler of a stored procedure was executed but the context of the previous error was unavailable. A possible cause of this error is a SELECT statement that returns a result set in the exception handler. Click here for a list of possible parameters and odbc states. |
| WP012 | Error | 2516 | -866L | "%1 returned a result set with a different schema than expected" | When calling a procedure in the FROM clause of a SELECT statement, the expected schema of the result is taken from the WITH clause. If no WITH clause is given, the expected schema is taken from the system catalog. The result set returned from the call must match the expected schema or it must be possible to convert every column so that it matches. Click here for a list of possible parameters and odbc states. |
| WP013 | Error | 2523 | -873L | "%1 returned multiple result sets" | A procedure called in the FROM clause of a SELECT statement cannot return multiple result sets. Click here for a list of possible parameters and odbc states. |
| WP014 | Error | 2522 | -872L | "%1 does not return a result set" | A procedure called in the FROM clause of a SELECT statement must return a result set. Click here for a list of possible parameters and odbc states. |
| WP015 | Error | 2524 | -686L | "Insufficient cache to start Java VM" | Insufficient cache was available to start the Java VM. Restart the database server with a larger cache size. Click here for a list of possible parameters and odbc states. |
| WP016 | Error | 2662 | -995L | "Warning detected when optimizing SELECT INTO is treated as an error" | The SELECT...INTO #TEMPTABLE statement cannot proceed if a warning is detected while optimizing the query. To fix the problem, test the query by removing the INTO clause, and resolve the reported warning. Click here for a list of possible parameters and odbc states. |
| WP017 | Error | 3200 | -1556L | "External environment failed to start and establish a connection within the %1 second timeout" | The External Environment took too long to start up and establish a connection with the server. The problem may be due to the system being over stressed or incorrectly configured. Click here for a list of possible parameters and odbc states. |
| WP018 | Error | 3201 | -1557L | "External environment cannot be started during database startup" | An external environment cannot be started while a database is starting up. Wait for the database startup to complete before attempting to start an external environment. Click here for a list of possible parameters and odbc states. |
| WP019 | Error | 3211 | -1567L | "External environment cannot be started, external process terminated on start up" | The request to start an external environment could not be completed due to the fact that the external process terminated on start up. This problem is usually due to a client configuration issue. Click here for a list of possible parameters and odbc states. |
| WP020 | Error | 3246 | -1605L | "Table Parameterized Functions and V4 TableUDFs are not supported for this database." | The current database does not have catalog support for table parameterized functions. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |
| WP021 | Error | 3247 | -1606L | "Multiple table parameters are not supported." | Table parameterized functions are limited to only having at most a single table parameter. Click here for a list of possible parameters and odbc states. |
| WP022 | Error | 3249 | -1607L | "Outer references are not allowed for TPF input tables." | Outer references in the select list for a TPF input table are not allowed. Click here for a list of possible parameters and odbc states. |