Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 20101 | Error | QSA80 | -1009080L | "Key doesn't fit on a single database page: %2 (%3, %4). %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20102 | Error | QSA81 | -1009081L | "Data doesn't fit on a single database page: %2 (%3, %4). %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20103 | Error | QSA82 | -1009082L | "Hash object has no data to retrieve, only keys (%2, %3). %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20104 | Error | QSA83 | -1009083L | "DBSpace '%2' must be OFFLINE for ALTER PATH. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20105 | Error | QSA84 | -1009084L | "Error opening DBSPACE '%2'. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20106 | Error | QSA85 | -1009085L | "DBFILE '%2' is not valid. The catalog DBSpaceID is incorrect. DBSpaceID found: %3 DBSpaceID expected: %4. This segment cannot be used. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20107 | Error | QSA86 | -1009086L | "Error opening DBFILE '%2'. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20108 | Error | QSA87 | -1009087L | "The dbfile '%2' must be in READONLY mode for this operation. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20109 | Error | QSA88 | -1009088L | "Attempted to add a duplicate key. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20110 | Error | QSA89 | -1009089L | "The size of the value is more than the maximum allowed for the field. Value: %2 %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20111 | Error | QSA90 | -1009090L | "Page size selected is too small for this datatype. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20112 | Error | QSA91 | -1009091L | "Attempt to create a B-Tree with RecordSize+KeySize too large. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20113 | Error | QSA92 | -1009092L | "Must provide a key comparison routine on object creation. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20114 | Error | QSA93 | -1009093L | "The maximum key size must be between 1 and 5300. Key size: %2 %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20115 | Error | QSA94 | -1009094L | "Cannot use raw partition for MESSAGE LOG or ROW LOG. %1" | The MESSAGE LOG and ROW LOG files for load integrity constraint handling must be regular files. They cannot be raw partitions. Click here for a list of possible parameters and odbc states. |
| 20116 | Error | QSA95 | -1009095L | "MESSAGE LOG and ROW LOG cannot be the same on-disk file. %1" | The MESSAGE LOG and ROW LOG files cannot be the same on-disk files. Click here for a list of possible parameters and odbc states. |
| 20117 | Error | QSA96 | -1009096L | "%3 integrity constraint limit (%2) exceeded. %1" | The number of integrity constraint violations for the given type has been exceeded during the LOAD. The LOAD will rollback. Click here for a list of possible parameters and odbc states. |
| 20118 | Error | QSA97 | -1009097L | "Cumulative total (%2) for all integrity constraint violations exceeded. %1" | The total number of NULL, UNIQUE, DATA VALUE, and FOREIGN KEY integrity constraint violations has exceeded the user specified limit. Click here for a list of possible parameters and odbc states. |
| 20119 | Error | QSA98 | -1009098L | "Invalid MESSAGE LOG or ROW LOG filename. %1" | A bad filename (perhaps zero-length) was specified for either the MESSAGE LOG or ROW LOG files on the LOAD statement. Click here for a list of possible parameters and odbc states. |
| 20120 | Error | QSA99 | -1009099L | "%1" | No additional information available. Click here for a list of possible parameters and odbc states. |