Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Warning 1000104 | "in join virtual table '%1'%2" |
|---|---|
Constant | EMSG_DELETE_CBTNAMEJOIN |
SAP Sybase Error Number | 20764 |
SQL State | 01B04 |
SQL Code | 1000104L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Parameter 1 description |
Parameter 2 | Parameter 2 description |
Probable Cause | This is an informational message displayed in context with other messages. |
| Warning 1000105 | "%1" |
|---|---|
Constant | EMSG_DELETE_CBTNAME1TABLE |
SAP Sybase Error Number | 20765 |
SQL State | 01B05 |
SQL Code | 1000105L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Parameter 1 description |
Probable Cause | This is an informational message displayed in context with other messages. |
| Error 1000106 | "Local temporary table, %2, must be committed in order to create an index. %1" |
|---|---|
Constant | EMSG_CAT_CANNOT_CREATEIDX_ONLTT |
SAP Sybase Error Number | 20766 |
SQL State | QDB06 |
SQL Code | -1000106L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception. |
Parameter 2 | Tablename |
Probable Cause | To be able to create an index for a local temporary table, the table must be in a committed state. If this message occurs, the user has tried to execute a CREATE INDEX on a local temporary table that has had data inserted, deleted, or updated that has not yet been committed. |
| Warning 1000107 | "For table '%1' in join virtual table '%2', \n%3 left outer rows with %4 columns will be moved (inserted/deleted).\n" |
|---|---|
Constant | EMSG_DELETE_CBTLOUTERROWSMOVED |
SAP Sybase Error Number | 20767 |
SQL State | 01B07 |
SQL Code | 1000107L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | tablename |
Parameter 2 | join virtual table |
Parameter 3 | number of rows moved |
Parameter 4 | number of columns |
Probable Cause | This is an informational message displayed in context with other messages. The message displays the number of rows moved during an insert to or delete from a join. |
| Warning 1000108 | "The DELETE where clause yielded %1 rows, but table '%2' has no data." |
|---|---|
Constant | EMSG_DELETE_TABLENODATA |
SAP Sybase Error Number | 20768 |
SQL State | 01B08 |
SQL Code | 1000108L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | number of rows |
Parameter 2 | tablename |
Probable Cause | This is an internal error. This warning should not occur during normal use. If this error occurs, it should be reported to Sybase. |
| Error 1000110 | "The wrong SIndex has been opened for a fast projection index. %1" |
|---|---|
Constant | EMSG_CAT_WRONGSINDEX |
SAP Sybase Error Number | 20770 |
SQL State | QDB10 |
SQL Code | -1000110L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | 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. |
| Error 1000111 | "The wrong FP Index has been opened for a field. %1" |
|---|---|
Constant | EMSG_CAT_WRONGFPOPENED |
SAP Sybase Error Number | 20771 |
SQL State | QDB11 |
SQL Code | -1000111L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | 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. |
| Error 1000112 | "The EBM on the field's columnDescriptor does not match the column EBM on the FPIndex. %1" |
|---|---|
Constant | EMSG_CAT_EBMSDONTMATCH |
SAP Sybase Error Number | 20772 |
SQL State | QDB12 |
SQL Code | -1000112L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | 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. |
| Error 1000113 | "Field %2 does not have an FP index. %1" |
|---|---|
Constant | EMSG_CAT_FIELD_HAS_NOFPINDEX |
SAP Sybase Error Number | 20773 |
SQL State | QDB13 |
SQL Code | -1000113L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | Field name. |
Probable Cause | 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. |
| Error 1000114 | "CMP index can only be created on two distinct columns having identical datatypes. %1" |
|---|---|
Constant | EMSG_CMP_NOT_ON_TWOCOLUMNS |
SAP Sybase Error Number | 20774 |
SQL State | QDB14 |
SQL Code | -1000114L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | 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. |
| Warning 1000117 | "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." |
|---|---|
Constant | EMSG_CANNOT_CONVERT_FOR_INSERT |
SAP Sybase Error Number | 20777 |
SQL State | 00B17 |
SQL Code | 1000117L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The table that is being inserted to. |
Parameter 2 | The column that is being inserted to. |
Probable Cause | 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. |
| Warning 1000119 | "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." |
|---|---|
Constant | EMSG_CANNOT_CONVERT_FOR_INSERT_SELECT |
SAP Sybase Error Number | 20779 |
SQL State | 00B19 |
SQL Code | 1000119L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The table being inserted to. |
Parameter 2 | The column being inserted to. |
Parameter 3 | The row number in the SELECT results that contains the data that cannot be converted. |
Probable Cause | 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. |
| Error 1000120 | "Join %2 was not found in the catalog. %1" |
|---|---|
Constant | EMSG_DELETE_NOJOINTABLE |
SAP Sybase Error Number | 20780 |
SQL State | QDB20 |
SQL Code | -1000120L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | join virtual table name |
Probable Cause | This is an internal error. If this error occurs, it should be reported to Sybase. |
| Error 1000121 | "binary data not supported on data longer than 32767 %2, %1" |
|---|---|
Constant | EMSG_BINARYINPUTTOOLARGE |
SAP Sybase Error Number | 20781 |
SQL State | QDB21 |
SQL Code | -1000121L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | SA parse source code line |
Probable Cause | The user has input a binary string that is too wide |
| Warning 1000122 | "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." |
|---|---|
Constant | EMSG_CANNOT_CONVERT_FOR_UPDATE |
SAP Sybase Error Number | 20782 |
SQL State | 00B22 |
SQL Code | 1000122L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The table being updated. |
Parameter 2 | The column being updated. |
Parameter 3 | The n'th update to the table. |
Probable Cause | 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. |
| Error 1000123 | "Index '%2' cannot be created. Multicolumn indexes must be created using distinct columns. %1" |
|---|---|
Constant | EMSG_MCINDEX_NEEDS_DISTINCT_COLS |
SAP Sybase Error Number | 20783 |
SQL State | QDB23 |
SQL Code | -1000123L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the index being created. |
Parameter 2 | Location of the exception. |
Probable Cause | Multicolumn indexes must be created using distinct columns. That is, you cannot use the same column more than once when creating a multicolumn index. |
| Error 1000124 | "Function or Operator not supported on data longer than %2 bytes. %1" |
|---|---|
Constant | EMSG_BINARYINPUTFIELDTOOLARGE |
SAP Sybase Error Number | 20784 |
SQL State | QDB24 |
SQL Code | -1000124L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | number of bytes |
Probable Cause | The user has entered a binary string that is too wide. |
| Error 1000126 | "This database must be upgraded. %1" |
|---|---|
Constant | EMSG_VERSION_2OLD |
SAP Sybase Error Number | 20786 |
SQL State | QDB26 |
SQL Code | -1000126L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | This database must be upgraded with the ALTER DATABASE UPGRADE command in order to continue. |
| Error 1000127 | "The LIMIT specified, '%2', is too large. %1" |
|---|---|
Constant | EMSG_SQL_LIMIT_INVALIDSIZE |
SAP Sybase Error Number | 20787 |
SQL State | QDB27 |
SQL Code | -1000127L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | The LIMIT that was entered. |
Probable Cause | 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. |
| Warning 1000129 | "%1 row(s) deleted from index '%2' in %3 seconds." |
|---|---|
Constant | EMSG_DELETE_1INDEX_A |
SAP Sybase Error Number | 20789 |
SQL State | QDB29 |
SQL Code | 1000129L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Number of rows |
Parameter 2 | index name |
Parameter 3 | number of seconds to complete the operation |
Probable Cause | This is an informational message displayed after a delete. |