Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1000155 | "The attempted insert length (%3) for column %2 is longer than the maximum allowed (%4). %1" |
|---|---|
Constant | EMSG_INSRT_TOOLONG |
SAP Sybase Error Number | 20815 |
SQL State | QDB55 |
SQL Code | -1000155L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column name |
Parameter 3 | requested insert length |
Parameter 4 | maximum insert length allowed. |
Probable Cause | The attempted insert length is too long. The maximum length allowed is 65535. |
| Error 1000156 | "Tried to insert into too many (%2) LOW FAST indexes at one time in table '%3'. %1" |
|---|---|
Constant | EMSG_INSRT_TOOMANYINDICES |
SAP Sybase Error Number | 20816 |
SQL State | QDB56 |
SQL Code | -1000156L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | requested number of indexes to insert to |
Parameter 3 | tablename |
Probable Cause | The maximum number allowed is 32727. |
| Error 1000157 | "Columns for the index must be in ascending sort order. %1" |
|---|---|
Constant | EMSG_ASCENDING_SORT_ONLY |
SAP Sybase Error Number | 20817 |
SQL State | QDB57 |
SQL Code | -1000157L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | It is required that ASC (ascending) sort order be used for the columns in the indexes. |
| Error 1000158 | "An Identity size mismatch has occurred. The current transaction will rollback. %1" |
|---|---|
Constant | EMSG_CAT_IDSIZE_MISMATCH |
SAP Sybase Error Number | 20818 |
SQL State | QDB58 |
SQL Code | -1000158L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | IQ has encountered an Identity size mismatch. The current command will be rolled back. If this error occurs, the operation that caused it may be tried again. If the error occurs again, the server should be stopped and restarted. If the problem persists, Sybase should be notified of the error. |
| Warning 1000159 | "\nIn table '%1', the %2 width insert of %3 columns will begin at record %4." |
|---|---|
Constant | EMSG_INSRT_STARTRECID |
SAP Sybase Error Number | 20819 |
SQL State | 00B59 |
SQL Code | 1000159L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | tablename |
Parameter 2 | partial/fixed |
Parameter 3 | number of columns |
Parameter 4 | row number |
Probable Cause | Informational message displayed during insert. |
| Warning 1000160 | "Option %1 has an invalid setting: %2." |
|---|---|
Constant | EMSG_INVALID_OPTION_SETTING |
SAP Sybase Error Number | 20820 |
SQL State | 00B60 |
SQL Code | 1000160L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Name of the option with the invalid setting. |
Parameter 2 | The current value of the option. |
Probable Cause | The named OPTION is set to an invalid value. See the documentation for the valid values for the option. |
| Warning 1000161 | "You have %1 and %2 available, respectively." |
|---|---|
Constant | EMSG_INSRT_MEMNEEDEDWARN |
SAP Sybase Error Number | 20821 |
SQL State | 01B61 |
SQL Code | 1000161L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | amount of memory |
Parameter 2 | amount of memory |
Probable Cause | Informational message displayed with other messages regarding available memory. |
| Error 1000162 | "Unable to create the requested object. %1" |
|---|---|
Constant | EMSG_CAT_CANNOT_CREATE_OBJECT |
SAP Sybase Error Number | 20822 |
SQL State | QDB62 |
SQL Code | -1000162L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | IQ is not able to create the object that was requested. This object may be an FP index that is being created during a CREATE TABLE. This error will occur if IQ finds that the index already exists in the table for which it is being created. This can happen if you FORCE DROP a table and then try to recreate the table that was dropped. If this error occurs after a FORCE DROP, the server needs to be rebooted before continuing. If this error occurs for some other reason, Sybase should be notified. Extra diagnostic information will have output to the iqmsg file. |
| Error 1000163 | "%1 not supported." |
|---|---|
Constant | EMSG_NOT_SUPPORTED |
SAP Sybase Error Number | 20823 |
SQL State | QNA32 |
SQL Code | -1000163L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | operation name |
Probable Cause | The named operation is not supported. |
| Error 1000164 | "Only %1 supported." |
|---|---|
Constant | EMSG_RESTRICT_ONLY |
SAP Sybase Error Number | 20824 |
SQL State | QNA33 |
SQL Code | -1000164L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | type of RESTRICT supported |
Probable Cause | Only UPDATE RESTRICT and DELETE RESTRICT supported |
| Error 1000165 | "Only a single foreign key constraint can be created on the same foreign key column(s) and same candidate key column(s)." |
|---|---|
Constant | EMSG_SINGLE_FKEY_CONSTRAINT |
SAP Sybase Error Number | 20825 |
SQL State | QNA34 |
SQL Code | -1000165L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | For a given set of foreign key columns and candidate key columns, |
| Error 1000166 | "Cannot specify IGNORE CONSTRAINT ALL or DATA VALUE when option CONVERSION_ERROR is on. %1" |
|---|---|
Constant | EMSG_DATAVALUE_CONVERSION_ON |
SAP Sybase Error Number | 20826 |
SQL State | QDB66 |
SQL Code | -1000166L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Probable Cause | When choosing to ignore DATA TYPE or ALL integrity constraint violations on LOAD command, you must also have option CONVERSION_ERROR set to 'off'. |
| Error 1000167 | "Cannot %3 table %2 because of RI concurrency conflict. %1" |
|---|---|
Constant | EMSG_RI_CONCURRENCY_CONFLICT |
SAP Sybase Error Number | 20827 |
SQL State | QDB67 |
SQL Code | -1000167L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | name of table undergoing the given operation |
Parameter 3 | operation being performed on specified table |
Probable Cause | The named table cannot be modified in the manner specified because of an RI concurrency conflict. Such a conflict arises under the following conditions. delete/truncate/update candidate key at the same time its corresponding foreign key is being loaded/inserted/updated |
| Error 1000168 | "Cannot create %1 HG index because one already exists on the given columns." |
|---|---|
Constant | EMSG_CANNOT_CREATE_HG |
SAP Sybase Error Number | 20828 |
SQL State | QNA35 |
SQL Code | -1000168L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | type of HG index to be created (non-unique vs. unique) |
Probable Cause | Only a single HG index of a given type can be created on the same column set. For example, you cannot have two unique HG indexes on the same column set, but you are allowed to have a unique HG and a non-unique HG index on the same set of columns. |
| Error 1000169 | "Cannot create unique HG index because primary key or unique constraint already exists on the given columns." |
|---|---|
Constant | EMSG_CANNOT_CREATE_UNIQUE_HG |
SAP Sybase Error Number | 20829 |
SQL State | QNA36 |
SQL Code | -1000169L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | When you create a primary key or unique constraint, IQ automatically creates a unique HG index as the mechanism for enforcing the 'uniqueness' attribute of a primary key or unique constraint. Consequently, a user cannot create another unique HG on the same columns on which the primary key or unique constraint is defined. |
| Error 1000170 | "Cannot create a duplicate '%1' index '%2'." |
|---|---|
Constant | EMSG_DUPLICATE_INDEX |
SAP Sybase Error Number | 20830 |
SQL State | QNA37 |
SQL Code | -1000170L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | indextype |
Parameter 2 | indexname |
Probable Cause | Cannot create duplicate indexes of the same type on a set of columns. |
| 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. |