Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Warning 1000171 | "Insert Pass IP2.2 started." |
|---|---|
Constant | EMSG_INSRT_SORTPASS22_STARTED |
SAP Sybase Error Number | 20831 |
SQL State | 00B71 |
SQL Code | 1000171L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | Informational message. |
| Warning 1000172 | "Insert Pass %1 (%2 of %3) started." |
|---|---|
Constant | EMSG_INSRT_SORTPASS234_STARTED |
SAP Sybase Error Number | 20832 |
SQL State | 00B72 |
SQL Code | 1000172L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | pass number |
Parameter 2 | pass number |
Parameter 3 | number |
Probable Cause | This is an informational message. |
| Error 1000173 | "Index '%1' cannot be created. Multicolumn indexes must be created using distinct columns." |
|---|---|
Constant | EMSG_NEED_DISTINCT_COLUMNS |
SAP Sybase Error Number | 20833 |
SQL State | QNA38 |
SQL Code | -1000173L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the index being created. |
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. |
| Warning 1000174 | "\n\t%1 records were inserted into '%2'.\n" |
|---|---|
Constant | EMSG_INSRT_COMPLETE |
SAP Sybase Error Number | 20834 |
SQL State | 01B74 |
SQL Code | 1000174L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | number of insertions |
Parameter 2 | tablename |
Probable Cause | Informational message displayed after insert. |
| Warning 1000175 | "%1 records were inserted into %2 join virtual tables (%3 sections)\n for '%4'.\n" |
|---|---|
Constant | EMSG_INSRT_COMPLETEJOINS |
SAP Sybase Error Number | 20835 |
SQL State | 01B75 |
SQL Code | 1000175L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | number of records |
Parameter 2 | number of join virtual tables |
Parameter 3 | number of join sorts |
Parameter 4 | join virtual table name |
Probable Cause | This is an informational message displayed at the end of insert. |
| Error 1000176 | "Cannot perform foreign key create/alter operation because one is already in progress. %1" |
|---|---|
Constant | EMSG_FK_INPROGRESS |
SAP Sybase Error Number | 20836 |
SQL State | QDB76 |
SQL Code | -1000176L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Probable Cause | 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. |
| Warning 1000177 | "Only the catalog entry for the '%1' index was created, no data was available to populate the index." |
|---|---|
Constant | EMSG_APICREATEINDEXNODATA |
SAP Sybase Error Number | 20837 |
SQL State | QDB77 |
SQL Code | 1000177L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The index name |
Probable Cause | 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. |
| Error 1000178 | "The DATA parameter must have a non-NULL value. %1" |
|---|---|
Constant | EMSG_APIDATAMUSTHAVEVALUE |
SAP Sybase Error Number | 20838 |
SQL State | QDB78 |
SQL Code | -1000178L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | This is an internal error. If this error occurs, it should be reported to Sybase. |
| Error 1000179 | "The column length (%2) must be [if variable sized, between 0 and] %3. %1" |
|---|---|
Constant | EMSG_APISETACTUALFIELDLENGTH |
SAP Sybase Error Number | 20839 |
SQL State | QDB79 |
SQL Code | -1000179L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column length |
Parameter 3 | column length |
Probable Cause | This is an internal error. If this error occurs, it should be reported to Sybase. |
| Error 1000180 | "The maximum column length (%2) must be between 0 and %3. %1" |
|---|---|
Constant | EMSG_APISETMAXFIELDLENGTH |
SAP Sybase Error Number | 20840 |
SQL State | QDB80 |
SQL Code | -1000180L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column length |
Parameter 3 | column length |
Probable Cause | This is an internal error. If this error occurs, it should be reported to Sybase. |
| Error 1000181 | "The maximum column length (%2) is less than the actual length (%3). %1" |
|---|---|
Constant | EMSG_APIMAXACTUALFLEN |
SAP Sybase Error Number | 20841 |
SQL State | QDB81 |
SQL Code | -1000181L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column length |
Parameter 3 | column length |
Probable Cause | This is an internal error. If this error occurs, it should be reported to Sybase. |
| Error 1000182 | "Table %2 cannot be opened because it is currently involved in a foreign key create/alter operation. %1" |
|---|---|
Constant | EMSG_CANNOT_OPEN_FK_INPROGRESS |
SAP Sybase Error Number | 20842 |
SQL State | QDB82 |
SQL Code | -1000182L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | The name of the table being opened. |
Probable Cause | The named table cannot be opened for read or write access because it is currently undergoing a create/alter foreign operation. |
| Error 1000183 | "Attempt to insert data into column '%2' with a non-insertable datatype (%3) ignored. %1" |
|---|---|
Constant | EMSG_APIINSERTDATATYPEIGNORED |
SAP Sybase Error Number | 20843 |
SQL State | QDB83 |
SQL Code | -1000183L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | explanation for %2 |
Parameter 3 | explanation for %3 |
Probable Cause | This is an internal error. The datatype IQ is inserting to is unknown. If this error occurs, it should be reported to Sybase. |
| Error 1000185 | "Cannot drop table %1 because foreign keys still reference it." |
|---|---|
Constant | EMSG_FKEY_STILL_EXISTS_TO_TABLE |
SAP Sybase Error Number | 20845 |
SQL State | QNA39 |
SQL Code | -1000185L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | name of the table |
Probable Cause | The named table cannot be dropped until all foreign keys referencing it have first been dropped. |
| Error 1000186 | "Cannot create foreign key constraint on a candidate key that is also a foreign key." |
|---|---|
Constant | EMSG_CKEY_IS_ALSO_FKEY |
SAP Sybase Error Number | 20846 |
SQL State | QNA40 |
SQL Code | -1000186L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A candidate key cannot also be a foreign key. Here's an example illustrating what is meant by this exception. (1) A [pk] <----- B [fk] [pk] <-- ADD THIS ONE -- C[fk] (2) A [pk] <-- ADD THIS ONE -- B[fk] [pk] <------- C[fk] In case (1), adding foreign key C[fk] is disallowed. In case (2), adding foreign key B[fk] is disallowed. |
| Error 1000187 | "Unable to implicitly convert column '%2' to datatype (%3) from datatype (%4). %1" |
|---|---|
Constant | EMSG_SQL_IMPLICITCONVERSION |
SAP Sybase Error Number | 20847 |
SQL State | QCB87 |
SQL Code | -1000187L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column converting |
Parameter 3 | datatype being converted to |
Parameter 4 | datatype being converted from |
Probable Cause | The attempted implicit conversion is not possible. The conversion must be done explicitly. If implicit conversion is being attempted to or from a NUMERIC and this error results, the datatype displayed in the error for the NUMERIC will be SMALLINT, INT, or INT64 depending on the precision of the NUMERIC. This is because NUMERICs are treated internally as multiple precision signed integers. |
| Error 1000188 | "Only ASCII, BCP and BINARY are supported LOAD formats. %1" |
|---|---|
Constant | EMSG_LOAD_FORMAT_NOT_SUPPORTED |
SAP Sybase Error Number | 20848 |
SQL State | QDB88 |
SQL Code | -1000188L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The user specified a LOAD format that is not supported. |
| Error 1000189 | "DDL statements cannot proceed while the %2 is in an out of space condition. %1" |
|---|---|
Constant | EMSG_CAT_NODDL_WHILE_OUTOFSPACE |
SAP Sybase Error Number | 20849 |
SQL State | QDB89 |
SQL Code | -1000189L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The store that is out of space. |
Parameter 2 | Location of the exception. |
Probable Cause | 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. |
| Error 1000190 | "The index '%2' cannot be opened in the current transaction (%3). %1" |
|---|---|
Constant | EMSG_CANNOTFINDINDEX |
SAP Sybase Error Number | 20850 |
SQL State | QDB90 |
SQL Code | -1000190L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | Name of the index. |
Parameter 3 | The current transaction. |
Probable Cause | 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. |
| Error 1000192 | "The cursor for table '%2' has no data to fetch. %1" |
|---|---|
Constant | EMSG_JOIN_CURSORNOFETCH |
SAP Sybase Error Number | 20852 |
SQL State | QDB92 |
SQL Code | -1000192L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | tablename |
Probable Cause | This is an internal error. If this error occurs, it should be reported to Sybase. |