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 |
|---|---|---|---|---|---|
| QDB09 | Error | 21079 | -1000266L | "Table '%2' not found. %1" | The specified table could not be opened. Either the table does not exists or the name format is incorrect The table name must follow the format [OWNER.]TABLE Click here for a list of possible parameters and odbc states. |
| QDB10 | Error | 20770 | -1000110L | "The wrong SIndex has been opened for a fast projection index. %1" | This is an internal error and should not occur. Diagnostic information has been output to the iqmsg file. If the error occurs, it should be reported to Sybase. The operation that caused the error may be tried again. Click here for a list of possible parameters and odbc states. |
| QDB11 | Error | 20771 | -1000111L | "The wrong FP Index has been opened for a field. %1" | This is an internal error and should not occur. Diagnostic information has been output to the iqmsg file. If the error occurs, it should be reported to Sybase. The operation that caused the error may be tried again. Click here for a list of possible parameters and odbc states. |
| QDB12 | Error | 20772 | -1000112L | "The EBM on the field's columnDescriptor does not match the column EBM on the FPIndex. %1" | This is an internal error and should not occur. Diagnostic information has been output to the iqmsg file. If the error occurs, it should be reported to Sybase. The operation that caused the error may be tried again. Click here for a list of possible parameters and odbc states. |
| QDB13 | Error | 20773 | -1000113L | "Field %2 does not have an FP index. %1" | This error should not occur during normal operation. Every field has an FP index which is created automatically when the field is created. If the error occurs, diagnostic information will be output to the iqmsg file and the operation that caused it may be tried again. If the problem persists, the server should be shutdown and restarted. An occurrence of this error should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDB14 | Error | 20774 | -1000114L | "CMP index can only be created on two distinct columns having identical datatypes. %1" | A CMP index is an index that can be only created on two columns. You cannot create a single column CMP index; nor can you create a CMP index on three or more columns. Furthermore, when specifying two columns, the two columns must have identical datatypes. Click here for a list of possible parameters and odbc states. |
| QDB15 | Error | 20775 | -1000115L | "You cannot delete from join index %2 in the 'top' table %3. %1" | This is an internal error. You cannot delete from the top table in a join. If this error occurs, it should be reported to Sybase Click here for a list of possible parameters and odbc states. |
| QDB16 | Error | 20776 | -1000116L | "A temporary table cannot participate in a JOIN INDEX. '%2' is a temporary table. %1" | You cannot create a join index using a temporary table. Click here for a list of possible parameters and odbc states. |
| QDB18 | Error | 20778 | -1000118L | "Join index %2 was not found in the catalog. %1" | This is an internal error. If this error occurs, it should reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDB20 | Error | 20780 | -1000120L | "Join %2 was not found in the catalog. %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. |
| QDB21 | Error | 20781 | -1000121L | "binary data not supported on data longer than 32767 %2, %1" | The user has input a binary string that is too wide Click here for a list of possible parameters and odbc states. |
| QDB23 | Error | 20783 | -1000123L | "Index '%2' cannot be created. Multicolumn indexes must be created using distinct columns. %1" | 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. |
| QDB24 | Error | 20784 | -1000124L | "Function or Operator not supported on data longer than %2 bytes. %1" | The user has entered a binary string that is too wide. Click here for a list of possible parameters and odbc states. |
| QDB25 | Error | 20785 | -1000125L | "Table %2 is not part of join index %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. |
| QDB26 | Error | 20786 | -1000126L | "This database must be upgraded. %1" | This database must be upgraded with the ALTER DATABASE UPGRADE command in order to continue. Click here for a list of possible parameters and odbc states. |
| QDB27 | Error | 20787 | -1000127L | "The LIMIT specified, '%2', is too large. %1" | The LIMIT entered is too large. The LIMIT entered on the command line must be between 0 and 4294967295. However, this limitation is only for the LIMIT clause in the sql command. See the ASIQ Reference Manual for the actual, valid LIMIT size. Click here for a list of possible parameters and odbc states. |
| QDB28 | Error | 20788 | -1000128L | "You must delete from join index %2 before you can delete from table %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. |
| QDB29 | Warning | 20789 | 1000129L | "%1 row(s) deleted from index '%2' in %3 seconds." | This is an informational message displayed after a delete. Click here for a list of possible parameters and odbc states. |
| QDB31 | Error | 20791 | -1000131L | "The DELIMITED BY and LIMIT options are valid for WD indexes only. %1" | The DELIMITED BY and LIMIT options may be used only when creating a WD (WORD) index. Click here for a list of possible parameters and odbc states. |
| QDB32 | Error | 20792 | -1000132L | "In table '%2', the START ROW ID value (%3) must be greater than %4. Data has already been inserted at this location. %1" | You have entered an incorrect START ROW ID and are trying to insert into a column that already contains data. See the Administration and Performance Guide's chapter Moving Data in and out of Databases. The section on partial width inserts contains information regarding the START ROW ID option. Click here for a list of possible parameters and odbc states. |