Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 20660 | Error | QDA00 | -1000000L | "ESCAPES option must be OFF. %1" | Sybase IQ only supports 'LOAD TABLE' commands where the ESCAPES options must be OFF. Click here for a list of possible parameters and odbc states. |
| 20662 | Error | QDA02 | -1000002L | "Cannot get the index id for %2 from the catalog. %1" | This is an internal error. Join processing is not able to find an index in the catalog. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| 20663 | Error | QDA03 | -1000003L | "Cross-database joins are not supported. (%2 and %3) %1" | Cannot join tables from different databases. Click here for a list of possible parameters and odbc states. |
| 20664 | Error | QDA04 | -1000004L | "Index '%2' already exists in the catalog. %1" | This is an internal error. Join processing is trying to create an index id that already exists. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| 20665 | Error | QDA05 | -1000005L | "Join index '%2' already exists and has the same join fields as proposed join index '%3'. %1" | The user is trying to create a join index that already exists and has the same join fields. Click here for a list of possible parameters and odbc states. |
| 20666 | Error | QDA06 | -1000006L | "Only %2 NULL specifications on a column are permitted. %1" | A column specification in a LOAD statement can have a maximum number of NULL clauses. Click here for a list of possible parameters and odbc states. |
| 20667 | Error | QDA07 | -1000007L | "Index '%2' was not closed properly. %1" | This is an internal error. During close join index processing, a join index was not properly closed. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| 20668 | Error | QDA08 | -1000008L | "Unknown error. %1" | An error condition was encountered for which there is no message. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| 20669 | Error | QDA09 | -1000009L | "Cannot DISABLE index '%2'. It is open Read/Write and may have updates pending. %1" | This index cannot be DISABLED. It is open for write access and may have updates pending. Wait until no other users are using the index. Click here for a list of possible parameters and odbc states. |
| 20670 | Error | QDA10 | -1000010L | "Cannot DISABLE index '%2'. The index is in use. %1" | This index cannot be DISABLED. It is in use. Wait until no other users are using the index. Click here for a list of possible parameters and odbc states. |
| 20671 | Error | QDA11 | -1000011L | "Transaction %2 attempted to access '%4' created by transaction %3. %1" | Table Level Versioning doesn't allow access to versions newer than your current transaction ID. Click here for a list of possible parameters and odbc states. |
| 20672 | Error | QDA12 | -1000012L | "Index '%2' cannot be closed because it has %3 users. %1" | This is an internal error. The index cannot be closed because it is in use. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| 20673 | Error | QNA04 | -1008004L | "Cannot DROP index '%1'." | Users cannot drop internally created indexes except by dropping the table, join index, or alter-dropping the table or join index. Fast Projection indexes are internally created indexes. Click here for a list of possible parameters and odbc states. |
| 20674 | Error | QDA14 | -1000014L | "%2 MB is not sufficient for the load, update, or delete. %1" | The user can control the amount of heap memory a load/delete/update process (LOAD, INSERT VALUE, DELETE, SYNCHRONIZE, UPDATE) can use via the Load_Memory_MB option. If this memory limit isn't sufficient for the load/delete/update to run, then this exception is raised. To proceed, the user must either turnoff the limit (i.e., set Load_Memory_MB to zero) or increase the limit. Click here for a list of possible parameters and odbc states. |
| 20675 | Error | QNA05 | -1008005L | "Cannot ALTER join virtual table '%1'." | The user cannot alter a join virtual table. Click here for a list of possible parameters and odbc states. |
| 20676 | Error | QNA06 | -1008006L | "You cannot specify a DEFAULT value for a column." | The user cannot specify a DEFAULT value for a column during CREATE TABLE or ALTER TABLE ADD COLUMN. Click here for a list of possible parameters and odbc states. |
| 20677 | Error | QNA07 | -1008007L | "The ALTER TABLE option '%2' is not supported by Sybase IQ. %1" | The user entered an option that is not supported by Sybase IQ but is supported by ASA (like REPLICATION ON). Click here for a list of possible parameters and odbc states. |
| 20678 | Error | QDA18 | -1000018L | "The object cannot be opened for DROP or ALTER. It is already open. %1" | The object that you have requested to DROP or ALTER cannot be opened for META access. Either the current connection or another connection has a cursor open on the table you are trying to DROP or ALTER or on the table to which the field or index you are trying open for META belongs. In order to proceed, all cursors open on this object must be closed. Click here for a list of possible parameters and odbc states. |
| 20679 | Error | QNA08 | -1008008L | "You cannot TRUNCATE a join virtual table." | The user is not allowed to TRUNCATE a join virtual table. Click here for a list of possible parameters and odbc states. |
| 20680 | Error | QNA09 | -1008009L | "This statement is not supported by Sybase IQ." | The statement entered is supported by Adaptive Server Anywhere, but not by Sybase IQ. Click here for a list of possible parameters and odbc states. |