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 |
|---|---|---|---|---|---|
| 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. |
| QNA22 | Error | 21044 | -1008022L | "Bad commit identity block. The server may be out of synchronization. %1" | Multiplex servers cannot start this database. Start the coordinator in single server mode. Click here for a list of possible parameters and odbc states. |
| QNA23 | Error | 21045 | -1008023L | "Cannot start multiplex secondary server while the coordinator is in single server mode" | Restart the secondary server after the coordinator has restarted in normal mode. Click here for a list of possible parameters and odbc states. |
| QNA24 | Error | 21046 | -1008024L | "Multiplex coordinator must start as server@host: %2, on file: %3; to start with different settings, you must use the override switch. %1" | Only the configured coordinator can start the database. Start with the override switch (-iqmpx_ov 1) to bypass this check. Click here for a list of possible parameters and odbc states. |
| QNA25 | Error | 21047 | -1008025L | "Multiplex secondary server cannot continue while the coordinator is in single server mode. %1" | Resynchronize and restart the secondary server after the coordinator has restarted in normal mode. Click here for a list of possible parameters and odbc states. |
| QNA26 | Error | 21048 | -1008026L | "Multiplex secondary server out of synchronization with the coordinator. %1" | The secondary server's IQ catalog cannot be brought up to date with the coordinator's IQ catalog. This server must be synchronized. Click here for a list of possible parameters and odbc states. |
| QNA27 | Error | 20004 | -1011004L | "Cannot drop primary key or unique constraint because a foreign key still references it." | A primary key or unique constraint involved in a referential integrity relationship cannot be dropped until its corresponding foreign key is first dropped. Click here for a list of possible parameters and odbc states. |
| QNA28 | Error | 21057 | -1008027L | "Multiplex secondary node shutting down due to a file added to the IQ_SYSTEM_MAIN dbspace.\nThis node must be synchronized and restarted. %1" | The user has added a dbspace file to IQ_SYSTEM_MAIN on the coordinator. This causes secondary nodes to shut down. All secondary nodes must be synchronized and restarted after this operation. Click here for a list of possible parameters and odbc states. |