Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| -1000167L | Error | 20827 | QDB67 | "Cannot %3 table %2 because of RI concurrency conflict. %1" | The named table cannot be modified in the manner specified because of an RI concurrency conflict. Such a conflict arises under the following conditions. delete/truncate/update candidate key at the same time its corresponding foreign key is being loaded/inserted/updated Click here for a list of possible parameters and odbc states. |
| -1000168L | Error | 20828 | QNA35 | "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. |
| -1000169L | Error | 20829 | QNA36 | "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. |
| -1000170L | Error | 20830 | QNA37 | "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. |
| 1000171L | Warning | 20831 | 00B71 | "Insert Pass IP2.2 started." | Informational message. Click here for a list of possible parameters and odbc states. |
| 1000172L | Warning | 20832 | 00B72 | "Insert Pass %1 (%2 of %3) started." | This is an informational message. Click here for a list of possible parameters and odbc states. |
| -1000173L | Error | 20833 | QNA38 | "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. |
| 1000174L | Warning | 20834 | 01B74 | "\n\t%1 records were inserted into '%2'.\n" | Informational message displayed after insert. Click here for a list of possible parameters and odbc states. |
| 1000175L | Warning | 20835 | 01B75 | "%1 records were inserted into %2 join virtual tables (%3 sections)\n for '%4'.\n" | This is an informational message displayed at the end of insert. Click here for a list of possible parameters and odbc states. |
| -1000176L | Error | 20836 | QDB76 | "Cannot perform foreign key create/alter operation because one is already in progress. %1" | Concurrent foreign key create/alter operations are not supported. This error means that there is such an operation already in progress. Consequetly, this new operation will be denied. Click here for a list of possible parameters and odbc states. |
| 1000177L | Warning | 20837 | QDB77 | "Only the catalog entry for the '%1' index was created, no data was available to populate the index." | This is an internal error. The new index was to be populated from another, existing index but a source index could not be found. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| -1000178L | Error | 20838 | QDB78 | "The DATA parameter must have a non-NULL value. %1" | This is an internal error. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| -1000179L | Error | 20839 | QDB79 | "The column length (%2) must be [if variable sized, between 0 and] %3. %1" | This is an internal error. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| -1000180L | Error | 20840 | QDB80 | "The maximum column length (%2) must be between 0 and %3. %1" | This is an internal error. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| -1000181L | Error | 20841 | QDB81 | "The maximum column length (%2) is less than the actual length (%3). %1" | This is an internal error. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| -1000182L | Error | 20842 | QDB82 | "Table %2 cannot be opened because it is currently involved in a foreign key create/alter operation. %1" | The named table cannot be opened for read or write access because it is currently undergoing a create/alter foreign operation. Click here for a list of possible parameters and odbc states. |
| -1000183L | Error | 20843 | QDB83 | "Attempt to insert data into column '%2' with a non-insertable datatype (%3) ignored. %1" | This is an internal error. The datatype IQ is inserting to is unknown. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| -1000184L | Error | 20844 | QDB84 | "When inserting into join index '%2', the START ROW ID (%3) must 0 or 1. %1" | The START ROW ID for insert to a join must be 0 or 1. Click here for a list of possible parameters and odbc states. |
| -1000185L | Error | 20845 | QNA39 | "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. |
| -1000186L | Error | 20846 | QNA40 | "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. |