Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
Error 1009082 | "Hash object has no data to retrieve, only keys (%2, %3). %1" |
---|---|
Constant | EMSG_PHASH_NO_DATA |
SAP Sybase Error Number | 20103 |
SQL State | QSA82 |
SQL Code | -1009082L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 3 | 3) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009083 | "DBSpace '%2' must be OFFLINE for ALTER PATH. %1" |
---|---|
Constant | EMSG_ALTER_PATH_REQUIRES_OFFLINE_DBSPACE |
SAP Sybase Error Number | 20104 |
SQL State | QSA83 |
SQL Code | -1009083L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | dbspace name |
Probable Cause | No additional information available. |
Error 1009084 | "Error opening DBSPACE '%2'. %1" |
---|---|
Constant | EMSG_DBSPACE_OPEN_ERROR |
SAP Sybase Error Number | 20105 |
SQL State | QSA84 |
SQL Code | -1009084L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | dbspace name |
Probable Cause | No additional information available. |
Error 1009085 | "DBFILE '%2' is not valid. The catalog DBSpaceID is incorrect. DBSpaceID found: %3 DBSpaceID expected: %4. This segment cannot be used. %1" |
---|---|
Constant | EMSG_BAD_CAT_DBSPACEID |
SAP Sybase Error Number | 20106 |
SQL State | QSA85 |
SQL Code | -1009085L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | file path |
Parameter 3 | dbspace_id found |
Parameter 4 | dbspace_id expected |
Probable Cause | No additional information available. |
Error 1009086 | "Error opening DBFILE '%2'. %1" |
---|---|
Constant | EMSG_DBFILE_OPEN_ERROR |
SAP Sybase Error Number | 20107 |
SQL State | QSA86 |
SQL Code | -1009086L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | file path |
Probable Cause | No additional information available. |
Error 1009087 | "The dbfile '%2' must be in READONLY mode for this operation. %1" |
---|---|
Constant | EMSG_DBFILE_MUST_BE_RO |
SAP Sybase Error Number | 20108 |
SQL State | QSA87 |
SQL Code | -1009087L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | file path |
Probable Cause | No additional information available. |
Error 1009088 | "Attempted to add a duplicate key. %1" |
---|---|
Constant | EMSG_BT_DUPLICATE |
SAP Sybase Error Number | 20109 |
SQL State | QSA88 |
SQL Code | -1009088L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1009089 | "The size of the value is more than the maximum allowed for the field. Value: %2 %1" |
---|---|
Constant | EMSG_BT_KEYTOOBIG |
SAP Sybase Error Number | 20110 |
SQL State | QSA89 |
SQL Code | -1009089L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Key value. |
Probable Cause | No additional information available. |
Error 1009090 | "Page size selected is too small for this datatype. %1" |
---|---|
Constant | EMSG_BT_LARGERPAGE |
SAP Sybase Error Number | 20111 |
SQL State | QSA90 |
SQL Code | -1009090L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Parameter 1 description |
Probable Cause | No additional information available. |
Error 1009091 | "Attempt to create a B-Tree with RecordSize+KeySize too large. %1" |
---|---|
Constant | EMSG_BT_SIZEERROR |
SAP Sybase Error Number | 20112 |
SQL State | QSA91 |
SQL Code | -1009091L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1009092 | "Must provide a key comparison routine on object creation. %1" |
---|---|
Constant | EMSG_BT_NOKEYCOMPARE |
SAP Sybase Error Number | 20113 |
SQL State | QSA92 |
SQL Code | -1009092L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1009093 | "The maximum key size must be between 1 and 5300. Key size: %2 %1" |
---|---|
Constant | EMSG_BT_MAXKEYSIZEWRONG |
SAP Sybase Error Number | 20114 |
SQL State | QSA93 |
SQL Code | -1009093L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Key Size in error. |
Probable Cause | No additional information available. |
Error 1009094 | "Cannot use raw partition for MESSAGE LOG or ROW LOG. %1" |
---|---|
Constant | EMSG_SVIOLATION_LOG_ON_RAW |
SAP Sybase Error Number | 20115 |
SQL State | QSA94 |
SQL Code | -1009094L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The MESSAGE LOG and ROW LOG files for load integrity constraint handling must be regular files. They cannot be raw partitions. |
Error 1009095 | "MESSAGE LOG and ROW LOG cannot be the same on-disk file. %1" |
---|---|
Constant | EMSG_SVIOLATION_LOGS_SAMEFILE |
SAP Sybase Error Number | 20116 |
SQL State | QSA95 |
SQL Code | -1009095L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The MESSAGE LOG and ROW LOG files cannot be the same on-disk files. |
Error 1009096 | "%3 integrity constraint limit (%2) exceeded. %1" |
---|---|
Constant | EMSG_SVIOLATION_IGNORE_LIMIT_EXCEEDED |
SAP Sybase Error Number | 20117 |
SQL State | QSA96 |
SQL Code | -1009096L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | user specified integrity constraint limit |
Parameter 3 | type of integrity constraint violation specified by the user |
Probable Cause | The number of integrity constraint violations for the given type has been exceeded during the LOAD. The LOAD will rollback. |
Error 1009097 | "Cumulative total (%2) for all integrity constraint violations exceeded. %1" |
---|---|
Constant | EMSG_SVIOLATION_ALL_LIMIT_EXCEEDED |
SAP Sybase Error Number | 20118 |
SQL State | QSA97 |
SQL Code | -1009097L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | maximum number of constraint violations to ignore |
Probable Cause | The total number of NULL, UNIQUE, DATA VALUE, and FOREIGN KEY integrity constraint violations has exceeded the user specified limit. |
Error 1009098 | "Invalid MESSAGE LOG or ROW LOG filename. %1" |
---|---|
Constant | EMSG_SVIOLATION_INVALID_FILENAME |
SAP Sybase Error Number | 20119 |
SQL State | QSA98 |
SQL Code | -1009098L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Probable Cause | A bad filename (perhaps zero-length) was specified for either the MESSAGE LOG or ROW LOG files on the LOAD statement. |
Error 1009099 | "%1" |
---|---|
Constant | EMSG_RFU_QSA99 |
SAP Sybase Error Number | 20120 |
SQL State | QSA99 |
SQL Code | -1009099L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1009100 | "Database segment '%2' is not valid. It is of type '%3'. Type BTYPE_DBEXT was expected. This segment cannot be used. %1" |
---|---|
Constant | EMSG_SDBEXT_BAD_BTYPE |
SAP Sybase Error Number | 20121 |
SQL State | QSB00 |
SQL Code | -1009100L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | Name of the segment. |
Parameter 3 | Internal segment type found. |
Probable Cause | The segment type written to the segment header was found not to be of the expected type. You will need to restore your database from backup. |
Error 1009101 | "Database segment '%2' is not valid. PhysicalNBlocks Found: %3 PhysicalNBlocks Expected: 1. This segment cannot be used. %1" |
---|---|
Constant | EMSG_SDBEXT_BAD_NUMPHYSBLOCKS |
SAP Sybase Error Number | 20122 |
SQL State | QSB01 |
SQL Code | -1009101L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | Name of the segment. |
Parameter 3 | Number of Physical Blocks found. |
Probable Cause | The number of physical blocks read from the segment header is incorrect. You will need to restore your database from backup. |