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 |
|---|---|---|---|---|---|
| QSB48 | Error | 20192 | -1009152L | "Cannot %2 FK %3 row %4 because of RI violation. %1" | No additional information available. Cannot insert/update FK if there does not exist same value in associated CK any associated foreign key which has any all non-null data. Click here for a list of possible parameters and odbc states. |
| QSB49 | Error | 20193 | -1009153L | "Cannot remove row %3 from CK %2 during LOAD cleanup because of RI violation. %1" | No additional information available. If removing self-referential CK during LOAD cleanup phase and there exists a FK of removed value, we roll back the whole operation. Click here for a list of possible parameters and odbc states. |
| QSB50 | Error | 21118 | -1009154L | "Cannot alter dbspace when a backup is in progress" | An alter dbspace operation was attempted while a backup was running. The alter dbspace operation cannot proceed since it may modify internal database structures that are being backed up. Click here for a list of possible parameters and odbc states. |
| QSB51 | Error | 20194 | -1009156L | "Drop disallowed for dbspace %2. One or more of the file(s) are in use by the database. %1" | A segment must contain no user data and no database structures to drop Click here for a list of possible parameters and odbc states. |
| QSB52 | Error | 20195 | -1009157L | "There is insufficient reserve space to add %3 blocks to segment %2. Only %4 blocks or less may be added. %1" | Since a segment must use a contiguous range of block numbers, it can only be resized larger when the blocks following it are not in use by the next segment. Click here for a list of possible parameters and odbc states. |
| QSB53 | Error | 20196 | -1009158L | "Cannot resize segment %2 since the truncated region is in use. %1" | A segment can only be resized smaller when no blocks in the truncated are in use. Click here for a list of possible parameters and odbc states. |
| QSB54 | Error | 20197 | -1009159L | "The status specified for segment %2 is unchanged. %1" | The "alter dbspace status" syntax requires the new status to be different than the original status. Click here for a list of possible parameters and odbc states. |
| QSB55 | Error | 22000 | -1009155L | "Cannot perform requested command as there is an ALTER DBSPACE command in progress. %1" | A CREATE DBSPACE or a DROP DBSPACE command was issued when there was already an ALTER DBSPACE command in progress. Click here for a list of possible parameters and odbc states. |
| QSB56 | Error | 20198 | -1009160L | "There must be at least one readwrite dbspace (%2). %1" | There must at least one readwrite segment Click here for a list of possible parameters and odbc states. |
| QSB57 | Error | 20199 | -1009161L | "Cannot resize segment %2 since it is readonly. %1" | A readonly segment cannot be resized Click here for a list of possible parameters and odbc states. |
| QSB58 | Error | 20200 | -1009162L | "Insufficient space to relocate structures on %2. %1" | Database structures may need to be relocated in order to drop a segment or make it readonly. This space must be available on other segments. Click here for a list of possible parameters and odbc states. |
| QSB59 | Error | 20201 | -1009163L | "Segment %2 cannot be smaller than %3 blocks. %1" | Database structures may need to be relocated in order to drop a segment or make it readonly. This space must be available on other segments. Click here for a list of possible parameters and odbc states. |
| QSB60 | Error | 20202 | -1009164L | "You cannot drop the last dbspace. %1" | You can drop the last dbspace only if it is a temp dbspace Click here for a list of possible parameters and odbc states. |
| QSB61 | Error | 20203 | -1009165L | "Cannot perform requested command as the SYSIQFILE table is locked by another transaction. %1" | A CREATE DBSPACE, ALTER DPSACE or DROP DBSPACE command was issued when there was another command or stored procedure accessing the system table SYSIQFILE. Click here for a list of possible parameters and odbc states. |
| QSB62 | Error | 20204 | -1009166L | "%3 %4 is in use by dropped dbspace %2 on a secondary server. The drop dbspace command has not yet propagated through the multiplex. %1" | Fields for dropped dbspaces cannot be re-used until the drop dbspace commands have propagated through the multiplex Click here for a list of possible parameters and odbc states. |
| QSB63 | Error | 20207 | -1009167L | "dbspace %2 failed to open since it's definition conflicts with dbspace %3. Secondary server may need to be synchronized. %1" | The server has an invalid dbspace configuration. New dbspaces may fail to open or the server may fail to start until this is corrected. Click here for a list of possible parameters and odbc states. |
| QSB64 | Error | 20208 | -1009168L | "The WORD SKIP limit (%2) has been exceeded. %1" | The number of words encountered that are longer than the limit specified when the word index was create has been exceeded for the load. The load will rollback. Click here for a list of possible parameters and odbc states. |
| QSB65 | Error | 20222 | -1009169L | "Cannot write to RO DBSpace %2. %1" | No additional information available.. Click here for a list of possible parameters and odbc states. |
| QSB66 | Error | 20223 | -1009170L | "You have run out of space in %2 DBSpace. %1" | No additional information available.. Click here for a list of possible parameters and odbc states. |
| QSB67 | Error | 20224 | -1009171L | "An IO error was encountered while writing a database page in %2 DBSpace. %1" | No additional information available.. Click here for a list of possible parameters and odbc states. |