Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1000265 | "Index '%2' not found. %1" |
|---|---|
Constant | EMSG_INDEX_NOTFOUND |
SAP Sybase Error Number | 21078 |
SQL State | QDB05 |
SQL Code | -1000265L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of user specified index |
Probable Cause | The specified index could not be opened. Either the index does not exists or the name format is incorrect The index name must follow the format [OWNER.]TABLE.INDEX |
| Error 1000266 | "Table '%2' not found. %1" |
|---|---|
Constant | EMSG_TABLE_NOTFOUND |
SAP Sybase Error Number | 21079 |
SQL State | QDB09 |
SQL Code | -1000266L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of user specified table |
Probable Cause | The specified table could not be opened. Either the table does not exists or the name format is incorrect The table name must follow the format [OWNER.]TABLE |
| Error 1000267 | "Cannot convert '%2' to an integer percent. %1" |
|---|---|
Constant | EMSG_RESOURCE_CONVERROR |
SAP Sybase Error Number | 21080 |
SQL State | QDB07 |
SQL Code | -1000267L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Percent specified for RESOURCES |
Probable Cause | The percent must be an integer value |
| Error 1000268 | "The target '%2' overlaps an earlier target. %1" |
|---|---|
Constant | EMSG_TARGETS_OVERLAP |
SAP Sybase Error Number | 21081 |
SQL State | QDB08 |
SQL Code | -1000268L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of table or index |
Probable Cause | The user cannot specify an index or table multiple times. This also applies to an index that was already included by specifying its table. |
| Error 1000269 | "DBCC: Multiple modes specified with a write mode. %1" |
|---|---|
Constant | EMSG_DBCC_MULTI_WRITE_MODES |
SAP Sybase Error Number | 21082 |
SQL State | QDB59 |
SQL Code | -1000269L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The user can only specify one mode if a mode that updates the database is present. Update modes are dbcc command REPAIR, server switch -iqdrplks, database options Convert_HG_To_1242 and Convert_Varchar_To_1242 |
| Error 1000270 | "DBCC: FP Recreate failed for index '%2'. %1" |
|---|---|
Constant | EMSG_DBCC_FP_RECREATE_FAILED |
SAP Sybase Error Number | 21083 |
SQL State | QDB60 |
SQL Code | -1000270L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of index |
Probable Cause | If an FP re-create fails, the command must rollback |
| Error 1000271 | "Table '%2' is a temporary table, a view, or not an IQ table. %1" |
|---|---|
Constant | EMSG_NOT_IQ_TABLE |
SAP Sybase Error Number | 21084 |
SQL State | QDB61 |
SQL Code | -1000271L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of user specified table |
Probable Cause | The specified table was opened, but it was a non-IQ or temporary table or a view. Only non-temporary IQ tables can be processed. |
| Error 1000272 | "Invalid table name '%2'. %1" |
|---|---|
Constant | EMSG_INVALID_TABLE_NAME |
SAP Sybase Error Number | 21085 |
SQL State | QDB63 |
SQL Code | -1000272L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of user specified table |
Probable Cause | The table name must follow the format [OWNER.]TABLE |
| Error 1000273 | "Invalid index name '%2'. %1" |
|---|---|
Constant | EMSG_INVALID_INDEX_NAME |
SAP Sybase Error Number | 21086 |
SQL State | QDB64 |
SQL Code | -1000273L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of user specified index |
Probable Cause | The index name must follow the format [OWNER.]TABLE.INDEX |
| Error 1000274 | "DBCC: Upgrade options can be used only with CHECK or REPAIR mode. %1" |
|---|---|
Constant | EMSG_DBCC_UPGRADE_OPTIONS |
SAP Sybase Error Number | 21087 |
SQL State | QDB65 |
SQL Code | -1000274L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | Upgrade options (such as Convert_HG_To_1242) can be used only with CHECK or REPAIR. They cannot be used with ALLOCATION. |
| Error 1000275 | "Cannot process object '%2' at the current transaction level. %1" |
|---|---|
Constant | EMSG_FUTUREVERSION |
SAP Sybase Error Number | 21088 |
SQL State | QDB68 |
SQL Code | -1000275L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | Name of the object that cannot be processed. |
Probable Cause | The requested object cannot be opened because it was created by a future transaction. A COMMIT or ROLLBACK must be issued before the object can be opened |
| Error 1000276 | "At least one mode and target must be specified. %1" |
|---|---|
Constant | EMSG_NOTHING_TO_DO |
SAP Sybase Error Number | 21094 |
SQL State | QDB69 |
SQL Code | -1000276L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | DBCC has no default target or mode. The user must explicitly specify both a mode and target. |
| Error 1000277 | "\"dropleaks {database|dbspace dbspace-name}\" is the only command allowed in drop leaks mode. %1" |
|---|---|
Constant | EMSG_DBCC_DROPLEAKS_COMMAND |
SAP Sybase Error Number | 21095 |
SQL State | QDB70 |
SQL Code | -1000277L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | Modes are restricted to avoid long DBCC sessions during forced recovery |
| Error 1000278 | "\"resetclks\" must be run in single-node mode with \"allocation database\". %1" |
|---|---|
Constant | EMSG_DBCC_RESETCLKS_COMMAND |
SAP Sybase Error Number | 21096 |
SQL State | QDB71 |
SQL Code | -1000278L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | resetclks is restricted to allocation mode and single-node mode, and requires checking entire DB |
| Error 1000279 | "Column '%2' must be included in the insert. It is part of a multicolumn index. %1" |
|---|---|
Constant | EMSG_INSRT_MISSING_COLUMN_ON_INSERT |
SAP Sybase Error Number | 21108 |
SQL State | QDB99 |
SQL Code | -1000279L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | The name of the column missing in the insert. |
Probable Cause | All columns of a multicolumn index must be included in an insert. |
| Error 1000280 | "Secondary server version information has not changed" |
|---|---|
Constant | EMSG_IQ_QUERY_NOTCHANGED |
SAP Sybase Error Number | 21109 |
SQL State | QDC64 |
SQL Code | -1000280L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | ev_iqmpxstatus has run the query event but there is nothing for it to do. |
| Error 1000281 | "Column %2 has unsupported data type for index rebuild. %1" |
|---|---|
Constant | EMSG_FPSTYLE_UNSUPPORTED |
SAP Sybase Error Number | 21110 |
SQL State | QDC56 |
SQL Code | -1000281L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Index name |
Probable Cause | You have tried to rebuild an FP index of unsupported index style. |
| Error 1000282 | "DBCC must be restricted to the MAIN or LOCAL store only. %1" |
|---|---|
Constant | EMSG_DBCC_ONEMPXSTORE |
SAP Sybase Error Number | 21116 |
SQL State | QDB72 |
SQL Code | -1000282L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | DBCC is restricted to either the main or the local store only. It may not combine checking of tables in both main and local in the same dbcc run. |
| Error 1000283 | "Identity/Autoincrement Column value range exceeded for column %2. %1" |
|---|---|
Constant | EMSG_IDENTITY_EXCEEDS_RANGE |
SAP Sybase Error Number | 20030 |
SQL State | QDC65 |
SQL Code | -1000283L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column name |
Probable Cause | Data overflow: An Identity/Autoincrement Column has reached its maximum value. To correct this create a new table in which the datatype of the new Identity/Autoincrement Column is larger and copy this table into the new table. Alternatively add a new Identity/Autoincrement Column to the table with a larger datatype and delete the old one. |
| Error 1000284 | "Identity/Autoincrement Column value for column %2 must be positive. %1" |
|---|---|
Constant | EMSG_IDENTITY_VALUE_MUST_BE_POSITIVE |
SAP Sybase Error Number | 20032 |
SQL State | QDC66 |
SQL Code | -1000284L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column name |
Probable Cause | All values in Identity/Autoincrement Columns must be positive. To correct this, only use positive values when manually inserting into Identity/Autoincrement Columns. |