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 |
|---|---|---|---|---|---|
| 1000109L | Warning | 20769 | 00B09 | "For table %1, join index %2 was modified. %3 rows were deleted." | Informational message regarding rows deleted from a table. Click here for a list of possible parameters and odbc states. |
| -1000110L | Error | 20770 | QDB10 | "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. |
| -1000111L | Error | 20771 | QDB11 | "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. |
| -1000112L | Error | 20772 | QDB12 | "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. |
| -1000113L | Error | 20773 | QDB13 | "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. |
| -1000114L | Error | 20774 | QDB14 | "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. |
| -1000115L | Error | 20775 | QDB15 | "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. |
| -1000116L | Error | 20776 | QDB16 | "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. |
| 1000117L | Warning | 20777 | 00B17 | "The data to be inserted into table '%2', column '%1' cannot be converted to the datatype of the column. NULL will be inserted if the column allows NULLs." | The database option CONVERSION_ERROR has been set to 'OFF' for this INSERT. The data to be inserted to the named column cannot be converted to the datatype of that column. If the column allows NULL, then NULL will be inserted instead. Click here for a list of possible parameters and odbc states. |
| -1000118L | Error | 20778 | QDB18 | "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. |
| 1000119L | Warning | 20779 | 00B19 | "The data to be inserted into table '%2', column `%1' from row %3 of the select results cannot be converted to the datatype of the destination column. NULL will be inserted if the column allows NULLs." | The database option CONVERSION_ERROR has been set to 'OFF' for this INSERT...SELECT. During INSERT...SELECT, the data to be inserted to one of the columns cannot be converted to the datatype of that column. If the column allows NULL, then NULL will be inserted instead. Click here for a list of possible parameters and odbc states. |
| -1000120L | Error | 20780 | QDB20 | "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. |
| -1000121L | Error | 20781 | QDB21 | "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. |
| 1000122L | Warning | 20782 | 00B22 | "The data to update table '%2', column `%1' cannot be converted to the datatype of the destination column for update number %3 to the table. NULL will be inserted if the column allows NULLs." | The database option CONVERSION_ERROR has been set to 'OFF' for this UPDATE. During UPDATE, the data to update one of the columns cannot be converted to the datatype of the column. The update number represents the number of updates made to the table which is not necessarily the row number of the table being updated. The column will be updated with NULL if the column definition allows NULLs. Click here for a list of possible parameters and odbc states. |
| -1000123L | Error | 20783 | QDB23 | "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. |
| -1000124L | Error | 20784 | QDB24 | "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. |
| -1000125L | Error | 20785 | QDB25 | "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. |
| -1000126L | Error | 20786 | QDB26 | "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. |
| -1000127L | Error | 20787 | QDB27 | "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. |
| -1000128L | Error | 20788 | QDB28 | "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. |