Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| QSA90 | Error | 20111 | -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. |
| QSA91 | Error | 20112 | -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. |
| QSA92 | Error | 20113 | -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. |
| QSA93 | Error | 20114 | -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. |
| QSA94 | Error | 20115 | -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. |
| QSA95 | Error | 20116 | -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. |
| QSA96 | Error | 20117 | -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. |
| QSA97 | Error | 20118 | -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. |
| QSA98 | Error | 20119 | -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. |
| QSA99 | Error | 20120 | -1009099L | "%1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSB00 | Error | 20121 | -1009100L | "Database segment '%2' is not valid. It is of type '%3'. Type BTYPE_DBEXT was expected. This segment cannot be used. %1" | 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. Click here for a list of possible parameters and odbc states. |
| QSB01 | Error | 20122 | -1009101L | "Database segment '%2' is not valid. PhysicalNBlocks Found: %3 PhysicalNBlocks Expected: 1. This segment cannot be used. %1" | The number of physical blocks read from the segment header is incorrect. You will need to restore your database from backup. Click here for a list of possible parameters and odbc states. |
| QSB02 | Error | 20123 | -1009102L | "Incorrect HG Index Version (%2): Index must be dropped by previous version of Sybase IQ and recreated. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSB03 | Error | 20124 | -1009103L | "Number of unique values exceeded for index. %2 %3 %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSB04 | Error | 20125 | -1009104L | "Bad args, both values must be >= 1 (%2 %3). %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSB05 | Error | 20126 | -1009105L | "Could not find block: %2. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSB06 | Error | 20127 | -1009106L | "DBFILE '%2' is not valid. The catalog file id is incorrect. FileID found: %3 FileID expected: %4. This segment cannot be used. %1" | The FileID information stored on the disk segment's header is not correct. The disk segment cannot be used. Click here for a list of possible parameters and odbc states. |
| QSB07 | Error | 20128 | -1009107L | "Duplicate entry for block: %2, record %3. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSB08 | Error | 20129 | -1009108L | "Database segment '%2' is not valid. Startblock found in the header: %3 Startblock expected: %4. This segment cannot be used. %1" | The start block of the disk segment that was found in the disk segment header is not the same as what was expected. The disk segment cannot be used. Click here for a list of possible parameters and odbc states. |
| QSB09 | Error | 20130 | -1009109L | "Key size %2 is more than the maximum %3. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |