Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| 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. |
| Error 1000285 | "The value specified for the Identity/Autoincrement Column %2 exceeds the range of its datatype. %1" |
|---|---|
Constant | EMSG_VALUE_TOO_LARGE |
SAP Sybase Error Number | 20034 |
SQL State | QDC67 |
SQL Code | -1000285L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column name |
Probable Cause | The value specified does not fit in the Identity/Autoincrement Column. To correct this, choose a smaller value |
| Error 1000286 | "Invalid table argument %2 to sp_iq_reset_identity, Table has no Identity/Autoincrement Column. %1" |
|---|---|
Constant | EMSG_TABLE_HAS_NO_IDENTITY |
SAP Sybase Error Number | 20035 |
SQL State | QDC68 |
SQL Code | -1000286L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | name of table |
Probable Cause | Table's without Identity/Autoincrement Columns cannot be used in calls to stored procedure sp_iq_reset_identity. |
| Error 1000287 | "Invalid table argument %2 to sp_iq_reset_identity, Table cannot be a JVT. %1" |
|---|---|
Constant | EMSG_NO_JVT_RESET_IDENTITY |
SAP Sybase Error Number | 20036 |
SQL State | QDC69 |
SQL Code | -1000287L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | table name |
Probable Cause | Tables of type JVT are not allowed as arguments to the stored procedure sp_iq_reset_identity |
| Error 1000288 | "Invalid table argument %2 for set option 'identity_insert', Table cannot be a JVT. %1" |
|---|---|
Constant | EMSG_TABLE_CANNOT_BE_JVT |
SAP Sybase Error Number | 20037 |
SQL State | QDC70 |
SQL Code | -1000288L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | table name |
Probable Cause | Tables of type JVT are not allowed as a value for the set option 'identity_insert' |
| Error 1000289 | "Invalid table argument %2 for set option 'identity_insert', Table must be an IQ table. %1" |
|---|---|
Constant | EMSG_TABLE_MUST_BE_IQ_IDENTITY_INSERT |
SAP Sybase Error Number | 20038 |
SQL State | QDC71 |
SQL Code | -1000289L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | table name |
Probable Cause | Only IQ tables are allowed as an argument value to the set option 'identity_insert' |
| Error 1000290 | "Invalid table argument %2 for stored procedure sp_iq_reset_identity, Table must be an IQ Table. %1" |
|---|---|
Constant | EMSG_TABLE_MUST_BE_IQ_RESET_IDENTITY |
SAP Sybase Error Number | 20039 |
SQL State | QDC72 |
SQL Code | -1000290L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | table name |
Probable Cause | Only IQ tables are allowed as a table argument to the stored procedure sp_iq_reset_identity |
| Error 1000291 | "You do not have insert permission on table %2. %1" |
|---|---|
Constant | EMSG_NO_PERM_IDENTITY_INSERT |
SAP Sybase Error Number | 20041 |
SQL State | QDC73 |
SQL Code | -1000291L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | table name |
Probable Cause | You cannot set the option 'identity_insert' to a table for which you do not have insert permission |
| Error 1000292 | "Invalid use of set option 'identity insert'. Table %2 does not have an Identity/Autoincrement Column. %1" |
|---|---|
Constant | EMSG_PARAM_TABLE_HAS_NO_IDENTITY |
SAP Sybase Error Number | 20474 |
SQL State | QDC74 |
SQL Code | -1000292L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | table name |
Probable Cause | the set option 'identity insert' cannot be used on a table without an Identity/Autoincrement Column. |
| Error 1000293 | "Cannot insert or update Column %2: set option 'identity_insert' to the specific table name containing the identity column to be modified. %1" |
|---|---|
Constant | EMSG_IDENTITY_INSERT_IS_OFF |
SAP Sybase Error Number | 20644 |
SQL State | QDC75 |
SQL Code | -1000293L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | column name |
Probable Cause | set option 'identity_insert' must be set to the specific table for which you want to insert or update an Identity column. To turn it on use set identity_insert <table_name> |
| Error 1000294 | "Cannot set 'identity_insert', it is already on for a different table. %1" |
|---|---|
Constant | EMSG_IDENTITY_INSERT_ON_FOR_OTHER |
SAP Sybase Error Number | 20645 |
SQL State | QDC76 |
SQL Code | -1000294L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Probable Cause | the set option 'identity_insert' can only be set for one table at a time. To set it for a different table, first turn it off using 'set identity_insert '' ' then set it to the desired table. |
| Error 1000295 | "Invalid table name %2 specified for option 'identity_insert'. %1" |
|---|---|
Constant | EMSG_INVALID_TAB_NAME |
SAP Sybase Error Number | 20646 |
SQL State | QDC77 |
SQL Code | -1000295L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | table name |
Probable Cause | The table associated with the table name specified for the 'identity_insert' option could not be found. |
| Error 1000296 | " Invalid load specification for LOAD ... FORMAT BCP. %1" |
|---|---|
Constant | EMSG_INVALIDLOADSPECFORBCPLOAD |
SAP Sybase Error Number | 21124 |
SQL State | QDC78 |
SQL Code | -1000296L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Probable Cause | The user specified a load specification that is not supported with FORMAT BCP option. |
| Warning 1000297 | "%1. Message logging stopped." |
|---|---|
Constant | EMSG_SQL_IQMSG_MANAGEMENT_ERROR |
SAP Sybase Error Number | 21149 |
SQL State | QCB17 |
SQL Code | 1000297L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Reason behind stopping of message logging. Can be either due to disk error, or due to message log management error. |
Probable Cause | Message log management operation failed due to error in file renaming / deletion / creation. Or log could not be written in the IQMSG file because some DISK IO error occurred. |
| Warning 1000298 | " Message logging resumed." |
|---|---|
Constant | EMSG_MESSAGE_LOGGING_RESUMED |
SAP Sybase Error Number | 21150 |
SQL State | QCB18 |
SQL Code | 1000298L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | Engine has detected that reason behind message log management / message logging failure has been resolved. Message logging is resumed now. |
| Error 1000299 | " Partition key of %2 is unsupported. %1" |
|---|---|
Constant | EMSG_CAT_UNSUPPORTED_PARTITION_KEY |
SAP Sybase Error Number | 21152 |
SQL State | QDC79 |
SQL Code | -1000299L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | datatype |
Parameter 2 | location of exception |
Probable Cause | Partiiton key of LOB/CLOB/char/varchar/binary/varbinary over 255 is not supported. |
| Error 1000302 | " Exceed maximum number of partitions. %1" |
|---|---|
Constant | EMSG_CAT_EXCEED_MAX_NUM_PARTITIONS |
SAP Sybase Error Number | 21155 |
SQL State | QDC82 |
SQL Code | -1000302L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Probable Cause | Exceed maximum number of partitions. |
| Error 1000303 | " Object %2 not usable in current context. %1" |
|---|---|
Constant | EMSG_CAT_OBJECT_NOT_USABLE |
SAP Sybase Error Number | 21156 |
SQL State | QDC83 |
SQL Code | -1000303L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | object name |
Probable Cause | Table of TBLTYP_PARTITION type cannot be used. |