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 |
|---|---|---|---|---|---|
| QDB76 | Error | 20836 | -1000176L | "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. |
| QDB77 | Warning | 20837 | 1000177L | "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. |
| QDB78 | Error | 20838 | -1000178L | "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. |
| QDB79 | Error | 20839 | -1000179L | "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. |
| QDB80 | Error | 20840 | -1000180L | "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. |
| QDB81 | Error | 20841 | -1000181L | "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. |
| QDB82 | Error | 20842 | -1000182L | "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. |
| QDB83 | Error | 20843 | -1000183L | "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. |
| QDB84 | Error | 20844 | -1000184L | "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. |
| QDB85 | Error | 22006 | -1000321L | "dropleaks is not allowed in multiplex mode. %1" | Dropleaks require server to be started in simplex configuration Click here for a list of possible parameters and odbc states. |
| QDB86 | Error | 22007 | -1000322L | "Use CREATE DBSPACE USING FILE syntax for creating IQ dbspaces. %1" | In Atomic IQ dbspaces can be created using the FILE Syntax for create dbspace. Old pre-atomic syntax can be used to create catalog store dbspaces only. Click here for a list of possible parameters and odbc states. |
| QDB88 | Error | 20848 | -1000188L | "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. |
| QDB89 | Error | 20849 | -1000189L | "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. |
| QDB90 | Error | 20850 | -1000190L | "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. |
| QDB91 | Error | 20851 | -1000191L | "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. |
| QDB92 | Error | 20852 | -1000192L | "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. |
| QDB93 | Error | 20853 | -1000193L | "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. |
| QDB94 | Error | 20854 | -1000194L | "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. |
| QDB95 | Error | 20855 | -1000195L | "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. |
| QDB96 | Error | 20856 | -1000196L | "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. |