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 |
|---|---|---|---|---|---|
| QNA01 | Error | 20621 | -1008001L | "The user cannot create indexes on a join virtual table." | Users cannot create indexes on a join virtual table. They are automatically created. Click here for a list of possible parameters and odbc states. |
| QNA02 | Error | 20623 | -1008002L | "There is a join index using table '%1'. The table cannot be dropped until the join index is dropped or altered." | There is at least one join index using this table in a join relationship. The table cannot be dropped until the join index is dropped or it is altered such that it no longer uses this table. Click here for a list of possible parameters and odbc states. |
| QNA03 | Error | 20639 | -1008003L | "Cannot drop join virtual table '%1'." | The user is not allowed to drop a join virtual table. It can be dropped by dropping the join index. Click here for a list of possible parameters and odbc states. |
| QNA04 | Error | 20673 | -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. |
| QNA05 | Error | 20675 | -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. |
| QNA06 | Error | 20676 | -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. |
| QNA07 | Error | 20677 | -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. |
| QNA08 | Error | 20679 | -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. |
| QNA09 | Error | 20680 | -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. |
| QNA10 | Error | 20681 | -1008010L | "A request was made to delete the primary key constraint, but the primary key cannot be found." | The user wanted to delete the primary key constraint on the table but the primary key could not be found. Click here for a list of possible parameters and odbc states. |
| QNA11 | Error | 20685 | -1008011L | "Cannot create the join index because the datatype of the underlying join virtual table column is not equal to the datatype of the corresponding base table column '%1'." | The underlying jvt column and the corresponding base table column must be of the same datatype in order to create a join index. One way to get this error is to create a join index on tables containing FLOAT columns with a client application that uses an open client (isql) or JDBC (Sybase Central) connection. For such connections, the database option FLOAT_AS_DOUBLE defaults to ON thereby creating jvt columns as type DOUBLE for the FLOAT columns in the base tables. To create the join using one of these tools, the user must first set FLOAT_TO_DOUBLE to OFF. See the 'Database Options' chapter in the ASIQ Reference Manual for details on Database Options. Click here for a list of possible parameters and odbc states. |
| QNA12 | Error | 20990 | -1008012L | "This unique index/constraint must be ENFORCED." | This unique index/constraint must be ENFORCED (The UNENFORCED keyword not allowed for this index/constraint). Click here for a list of possible parameters and odbc states. |
| QNA13 | Error | 20991 | -1008013L | "This multi-column unique index/constraint must be UNENFORCED." | This multi-column unique index/constraint must be UNENFORCED (The UNENFORCED keyword is required for this index/constraint). Click here for a list of possible parameters and odbc states. |
| QNA14 | Error | 20992 | -1008014L | "This foreign key must be UNENFORCED." | This foreign key must be UNENFORCED (The UNENFORCED keyword is required for this foreign key). Click here for a list of possible parameters and odbc states. |
| QNA15 | Error | 20993 | -1008015L | "This check constraint must be ENFORCED." | The keyword UNENFORCED is not supported. Click here for a list of possible parameters and odbc states. |
| QNA16 | Error | 20994 | -1008016L | "Cannot ALTER DELETE a column that has a unique or primary key constraint." | Cannot ALTER DELETE a column that has a unique or primary key constraint. This is a duplicate of an SA error code. Click here for a list of possible parameters and odbc states. |
| QNA17 | Error | 20995 | -1008017L | "Cannot ALTER DELETE a column that has multi-column index." | Cannot ALTER DELETE a column that has multi-column index. This is a duplicate of an SA error code. Click here for a list of possible parameters and odbc states. |
| QNA19 | Error | 21041 | -1008019L | "Multiplex is currently inactive." | The user has either requested a multiplex function or has asked for multiplex status. Click here for a list of possible parameters and odbc states. |
| QNA20 | Error | 21042 | -1008020L | "Multiplex command or request is unimplemented." | The user has requested an unimplemented multiplex feature. This would typically be a status request which doesn't exist. Click here for a list of possible parameters and odbc states. |
| QNA21 | Error | 21043 | -1008021L | "The SYSIQFILE table is not configured for this server to run in a multiplex." | SYSIQFILE identifies all files which make up the given stores that the IQ server requires (main, temp, and message). For multiplex, each entry in SYSIQFILE must be associated with a particular multiplex server before that server can access the particular file. This message indicates that some these rows are missing for the active server. Click here for a list of possible parameters and odbc states. |