Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| -1009082L | Error | 20103 | QSA82 | "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. |
| -1009083L | Error | 20104 | QSA83 | "DBSpace '%2' must be OFFLINE for ALTER PATH. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| -1009084L | Error | 20105 | QSA84 | "Error opening DBSPACE '%2'. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| -1009085L | Error | 20106 | QSA85 | "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. |
| -1009086L | Error | 20107 | QSA86 | "Error opening DBFILE '%2'. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| -1009087L | Error | 20108 | QSA87 | "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. |
| -1009088L | Error | 20109 | QSA88 | "Attempted to add a duplicate key. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| -1009089L | Error | 20110 | QSA89 | "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. |
| -1009090L | Error | 20111 | QSA90 | "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. |
| -1009091L | Error | 20112 | QSA91 | "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. |
| -1009092L | Error | 20113 | QSA92 | "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. |
| -1009093L | Error | 20114 | QSA93 | "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. |
| -1009094L | Error | 20115 | QSA94 | "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. |
| -1009095L | Error | 20116 | QSA95 | "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. |
| -1009096L | Error | 20117 | QSA96 | "%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. |
| -1009097L | Error | 20118 | QSA97 | "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. |
| -1009098L | Error | 20119 | QSA98 | "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. |
| -1009099L | Error | 20120 | QSA99 | "%1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| -1009100L | Error | 20121 | QSB00 | "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. |
| -1009101L | Error | 20122 | QSB01 | "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. |