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 |
|---|---|---|---|---|---|
| WI010 | Error | 2362 | -727L | "The optimizer was unable to construct a valid access plan" | The database server was unable to construct a valid access plan for the given request. This is a SQL Anywhere internal error. If it can be reproduced, it should be reported to iAnywhere. You may be able to work around this problem by modifying the query statement. Click here for a list of possible parameters and odbc states. |
| WI011 | Error | 2633 | -969L | "Required operators excluded" | The database server was unable to construct a valid access plan for the given request because required data flow operators were excluded by the exclude_operators option. Re-enable the required operators to execute the statement. Click here for a list of possible parameters and odbc states. |
| WI111 | Error | 2905 | -1227L | "Internal error. Contact Sybase IQ support. %1." | The multiplex DDL statement (CREATE/ALTER/DROP) failed with internal error due to specified reason. Click here for a list of possible parameters and odbc states. |
| WJ001 | Error | 2295 | -669L | "Method '%1' cannot be called at this time" | The method cannot be called at this time. Check that the method is not being called out of order. Click here for a list of possible parameters and odbc states. |
| WJ003 | Error | 2303 | -676L | "The specified transaction isolation is invalid" | The specified transaction isolation is invalid. Click here for a list of possible parameters and odbc states. |
| WJ004 | Error | 2312 | -683L | "The cursor name '%1' already exists" | You attempted to declare a cursor with a name that already exists. Cursor names must be unique within a connection. Click here for a list of possible parameters and odbc states. |
| 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. |
| 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 re-enlist 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. |
| WL011 | Error | 2831 | -1155L | "Unable to close the cursor on table \"%1\". LOAD TABLE cannot be executed." | You cannot perform LOAD TABLE on a temporary table that has an open cursor on it. An attempt to close the cursor failed. A failed LOAD TABLE would cause all of the rows in the temporary table to be deleted thereby invalidating the cursor. Click here for a list of possible parameters and odbc states. |
| WL012 | Error | 2864 | -1187L | "Cannot append when using compression or encryption" | The UNLOAD statement cannot append to a file when using compression or encryption. Either the compressed or encrypted keywords were specified, or the file being appended to is compressed or encrypted. Click here for a list of possible parameters and odbc states. |