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 |
|---|---|---|---|---|---|
| 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. |
| QNA29 | Error | 21059 | -1008029L | "Cannot create foreign key to an unenforced primary key or unenforced unique constraint." | Existing unenforced primary keys or unique constraints cannot be used to create an referential integrity relationship to a foreign table. Click here for a list of possible parameters and odbc states. |
| QNA30 | Error | 21064 | -1008030L | "Only IQ index types can be created on IQ tables within a Parallel IQ block." | Parallel IQ Begin/End blocks allow users to create multiple indexes simultaneously. At this time, only Create Index statements for HG, HNG, LF, LD, DATE, TIME, WD, and CMP index types on IQ tables are allowed within Parallel IQ Begin and End statements. Click here for a list of possible parameters and odbc states. |
| QNA31 | Error | 21065 | -1008031L | "Cannot do Create Index commands on global or local temporary tables or catalog server tables in a Parallel IQ block." | Cannot do Create Index commands on global or local temporary tables in a Parallel IQ block. Click here for a list of possible parameters and odbc states. |
| QNA32 | Error | 20823 | -1000163L | "%1 not supported." | The named operation is not supported. Click here for a list of possible parameters and odbc states. |
| QNA33 | Error | 20824 | -1000164L | "Only %1 supported." | Only UPDATE RESTRICT and DELETE RESTRICT supported Click here for a list of possible parameters and odbc states. |
| QNA34 | Error | 20825 | -1000165L | "Only a single foreign key constraint can be created on the same foreign key column(s) and same candidate key column(s)." | For a given set of foreign key columns and candidate key columns, Click here for a list of possible parameters and odbc states. |
| QNA35 | Error | 20828 | -1000168L | "Cannot create %1 HG index because one already exists on the given columns." | Only a single HG index of a given type can be created on the same column set. For example, you cannot have two unique HG indexes on the same column set, but you are allowed to have a unique HG and a non-unique HG index on the same set of columns. Click here for a list of possible parameters and odbc states. |
| QNA36 | Error | 20829 | -1000169L | "Cannot create unique HG index because primary key or unique constraint already exists on the given columns." | When you create a primary key or unique constraint, IQ automatically creates a unique HG index as the mechanism for enforcing the 'uniqueness' attribute of a primary key or unique constraint. Consequently, a user cannot create another unique HG on the same columns on which the primary key or unique constraint is defined. Click here for a list of possible parameters and odbc states. |
| QNA37 | Error | 20830 | -1000170L | "Cannot create a duplicate '%1' index '%2'." | Cannot create duplicate indexes of the same type on a set of columns. Click here for a list of possible parameters and odbc states. |
| QNA38 | Error | 20833 | -1000173L | "Index '%1' cannot be created. Multicolumn indexes must be created using distinct columns." | Multicolumn indexes must be created using distinct columns. That is, you cannot use the same column more than once when creating a multicolumn index. Click here for a list of possible parameters and odbc states. |
| QNA39 | Error | 20845 | -1000185L | "Cannot drop table %1 because foreign keys still reference it." | The named table cannot be dropped until all foreign keys referencing it have first been dropped. Click here for a list of possible parameters and odbc states. |
| QNA40 | Error | 20846 | -1000186L | "Cannot create foreign key constraint on a candidate key that is also a foreign key." | A candidate key cannot also be a foreign key. Here's an example illustrating what is meant by this exception. (1) A [pk] <----- B [fk] [pk] <-- ADD THIS ONE -- C[fk] (2) A [pk] <-- ADD THIS ONE -- B[fk] [pk] <------- C[fk] In case (1), adding foreign key C[fk] is disallowed. In case (2), adding foreign key B[fk] is disallowed. Click here for a list of possible parameters and odbc states. |
| QNA41 | Error | 20026 | -1008032L | "Foreign keys disallowed on Identity/Autoincrement Columns when set option identity_enforce_uniqueness is on" | An Identity/Autoincrement Column cannot be a foreign key when the set option identity_enforce_uniqueness is on. Either turn the option off, or chose a different column for the foreign key. Click here for a list of possible parameters and odbc states. |
| QNA42 | Error | 20027 | -1008033L | "Identity/Autoincrement Column %1 has Invalid datatype: scale must be 0." | Identity/Autoincrement Columns defined as datatype numeric must have scale 0 Click here for a list of possible parameters and odbc states. |
| QNA43 | Error | 20028 | -1008034L | "Cannot add an Identity/Autoincrement Column to table %1, it participates in a join index." | Adding an Identity/Autoincrement Column to a table that participates in a join index is not allowed, to perform this operation, the join index must be dropped Click here for a list of possible parameters and odbc states. |