Messages 20780 through 20799

Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.

Number Msg Type SQL State SQL Code Message Possible Cause
20780 Error QDB20 -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.

20781 Error QDB21 -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.

20782 Warning 00B22 1000122L "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.

20783 Error QDB23 -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.

20784 Error QDB24 -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.

20785 Error QDB25 -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.

20786 Error QDB26 -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.

20787 Error QDB27 -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.

20788 Error QDB28 -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.

20789 Warning QDB29 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.

20790 Warning 01B30 1000130L "%1 row(s) deleted from index '%2' on field '%3', %4 seconds." This is an informational message displayed after a delete.

Click here for a list of possible parameters and odbc states.

20791 Error QDB31 -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.

20792 Error QDB32 -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.

20793 Error QDB33 -1000133L "During the LOAD into table '%2', the LOAD statement's column count (%3) must be between 1 and %4. Check the LOAD statement's 'load-specification'. %1" The number of columns you are trying to insert to is not consistent with the number of columns specified in the LOAD statement's 'load-specification'. You must specify by name each column you are attempting to insert to via the LOAD statement.

Click here for a list of possible parameters and odbc states.

20794 Error QDB34 -1000134L "Column '%2' is being inserted into twice by this INSERT command. %1" The specified column was listed twice in the insert command.

Click here for a list of possible parameters and odbc states.

20795 Error QDB35 -1000135L "Cannot open the existence list for table '%2'. %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.

20796 Error QDB36 -1000136L "A mismatch exists between the existence bitmaps in the insert object. %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.

20797 Error QDB37 -1000137L "While inserting, table '%2' already had a Complete started. %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.

20798 Error QDB38 -1000138L "A data conversion error has occurred while loading record %2. This error should be reported to Sybase. %1" A data conversion error occurred during an insert. The input datatype cannot converted to the datatype of the data's destination field. This error should be reported to Sybase. Diagnostic information has been output to the iqmsg file.

Click here for a list of possible parameters and odbc states.

20799 Error QDB39 -1000139L "You cannot insert into table '%2' past the original end of the table while there are %3 join virtual tables based on it. %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.


Created May 6, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com