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 |
|---|---|---|---|---|---|
| -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. |
| -1000187L | Error | 20847 | QCB87 | "Unable to implicitly convert column '%2' to datatype (%3) from datatype (%4). %1" | The attempted implicit conversion is not possible. The conversion must be done explicitly. If implicit conversion is being attempted to or from a NUMERIC and this error results, the datatype displayed in the error for the NUMERIC will be SMALLINT, INT, or INT64 depending on the precision of the NUMERIC. This is because NUMERICs are treated internally as multiple precision signed integers. Click here for a list of possible parameters and odbc states. |
| -1000188L | Error | 20848 | QDB88 | "Only ASCII, BCP and BINARY are supported LOAD formats. %1" | The user specified a LOAD format that is not supported. Click here for a list of possible parameters and odbc states. |
| -1000189L | Error | 20849 | QDB89 | "DDL statements cannot proceed while the %2 is in an out of space condition. %1" | The DDL statement cannot proceed until the named db store is no longer in an out of space condtion. The out of space condition had been previously reported. The only course of action available is to stop and restart the server. The database is in an out-of-space condition. Space needs to be added to the database. Click here for a list of possible parameters and odbc states. |
| -1000190L | Error | 20850 | QDB90 | "The index '%2' cannot be opened in the current transaction (%3). %1" | The procedure cannot open the named index. It is likely that the index was created by a transaction that began after the one that is trying to open it. In order to proceed, COMMIT the current transaction and try again. Click here for a list of possible parameters and odbc states. |
| -1000191L | Error | 20851 | QDB91 | "Proxy, remote, or non-IQ tables are not allowed in joins. Tablename is '%2'. %1" | Proxy tables, remote objects, or non_IQ tables are not allowed to participate in a join index. Click here for a list of possible parameters and odbc states. |
| -1000192L | Error | 20852 | QDB92 | "The cursor for table '%2' has no data to fetch. %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. |
| -1000193L | Error | 20853 | QDB93 | "The table '%2' is either not part of the join virtual table or has had its data loaded through linked indices. %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. |
| -1000194L | Error | 20854 | QDB94 | "You must supply either a cursor count (%2) and a cursor array, or neither. %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. |
| -1000195L | Error | 20855 | QDB95 | "Load specification '%2' only valid for column(s) having datatype '%3'. %1" | The named load specification is only valid for columns that have the given datatype. Click here for a list of possible parameters and odbc states. |
| -1000196L | Error | 20856 | QDB96 | "You must supply a join index name. %1" | An indexname was not provided as a parameter. 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. |
| -1000197L | Error | 20857 | QDB97 | "Table '%2' has no columns in the cursor that don't already have data, \nor the join field(s) are not part of the cursor. %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. |
| -1000198L | Error | 20858 | QDB98 | "Cannot create join index with table(s) having column(s) of datatype %2. %1" | The 'join index' functionality is supported on most datatypes. However, there are a few (e.g., long binary) for which this functionality is not supported. Click here for a list of possible parameters and odbc states. |
| 1000199L | Warning | 20859 | 01B99 | "Table '%1' has no data." | This is a warning that there is no data in a base table. Click here for a list of possible parameters and odbc states. |
| -1000200L | Error | 20860 | QDC00 | "Table '%2' has no data with which to join the other tables. %1" | There is no data in a table which participates in a join. Click here for a list of possible parameters and odbc states. |
| -1000201L | Error | 20861 | QDC01 | "JOIN cannot be created or updated because the thread's stack space has been exceeded. %1" | Creation or update of this JOIN has exceeded the thread's stack space. Create or update the JOIN after restarting the engine with a larger value for the -iqtss startup parameter. See the ASIQ Reference Manual for information on setting iqtss. Click here for a list of possible parameters and odbc states. |