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 |
|---|---|---|---|---|---|
| -1000272L | Error | 21085 | QDB63 | "Invalid table name '%2'. %1" | The table name must follow the format [OWNER.]TABLE Click here for a list of possible parameters and odbc states. |
| -1000273L | Error | 21086 | QDB64 | "Invalid index name '%2'. %1" | The index name must follow the format [OWNER.]TABLE.INDEX Click here for a list of possible parameters and odbc states. |
| -1000274L | Error | 21087 | QDB65 | "DBCC: Upgrade options can be used only with CHECK or REPAIR mode. %1" | Upgrade options (such as Convert_HG_To_1242) can be used only with CHECK or REPAIR. They cannot be used with ALLOCATION. Click here for a list of possible parameters and odbc states. |
| -1000275L | Error | 21088 | QDB68 | "Cannot process object '%2' at the current transaction level. %1" | The requested object cannot be opened because it was created by a future transaction. A COMMIT or ROLLBACK must be issued before the object can be opened Click here for a list of possible parameters and odbc states. |
| -1000276L | Error | 21094 | QDB69 | "At least one mode and target must be specified. %1" | DBCC has no default target or mode. The user must explicitly specify both a mode and target. Click here for a list of possible parameters and odbc states. |
| -1000277L | Error | 21095 | QDB70 | "\"dropleaks {database|dbspace dbspace-name}\" is the only command allowed in drop leaks mode. %1" | Modes are restricted to avoid long DBCC sessions during forced recovery Click here for a list of possible parameters and odbc states. |
| -1000278L | Error | 21096 | QDB71 | "\"resetclks\" must be run in single-node mode with \"allocation database\". %1" | resetclks is restricted to allocation mode and single-node mode, and requires checking entire DB Click here for a list of possible parameters and odbc states. |
| -1000279L | Error | 21108 | QDB99 | "Column '%2' must be included in the insert. It is part of a multicolumn index. %1" | All columns of a multicolumn index must be included in an insert. Click here for a list of possible parameters and odbc states. |
| -1000280L | Error | 21109 | QDC64 | "Secondary server version information has not changed" | ev_iqmpxstatus has run the query event but there is nothing for it to do. Click here for a list of possible parameters and odbc states. |
| -1000281L | Error | 21110 | QDC56 | "Column %2 has unsupported data type for index rebuild. %1" | You have tried to rebuild an FP index of unsupported index style. Click here for a list of possible parameters and odbc states. |
| -1000282L | Error | 21116 | QDB72 | "DBCC must be restricted to the MAIN or LOCAL store only. %1" | DBCC is restricted to either the main or the local store only. It may not combine checking of tables in both main and local in the same dbcc run. Click here for a list of possible parameters and odbc states. |
| -1000283L | Error | 20030 | QDC65 | "Identity/Autoincrement Column value range exceeded for column %2. %1" | Data overflow: An Identity/Autoincrement Column has reached its maximum value. To correct this create a new table in which the datatype of the new Identity/Autoincrement Column is larger and copy this table into the new table. Alternatively add a new Identity/Autoincrement Column to the table with a larger datatype and delete the old one. Click here for a list of possible parameters and odbc states. |
| -1000284L | Error | 20032 | QDC66 | "Identity/Autoincrement Column value for column %2 must be positive. %1" | All values in Identity/Autoincrement Columns must be positive. To correct this, only use positive values when manually inserting into Identity/Autoincrement Columns. Click here for a list of possible parameters and odbc states. |
| -1000285L | Error | 20034 | QDC67 | "The value specified for the Identity/Autoincrement Column %2 exceeds the range of its datatype. %1" | The value specified does not fit in the Identity/Autoincrement Column. To correct this, choose a smaller value Click here for a list of possible parameters and odbc states. |
| -1000286L | Error | 20035 | QDC68 | "Invalid table argument %2 to sp_iq_reset_identity, Table has no Identity/Autoincrement Column. %1" | Table's without Identity/Autoincrement Columns cannot be used in calls to stored procedure sp_iq_reset_identity. Click here for a list of possible parameters and odbc states. |
| -1000287L | Error | 20036 | QDC69 | "Invalid table argument %2 to sp_iq_reset_identity, Table cannot be a JVT. %1" | Tables of type JVT are not allowed as arguments to the stored procedure sp_iq_reset_identity Click here for a list of possible parameters and odbc states. |
| -1000288L | Error | 20037 | QDC70 | "Invalid table argument %2 for set option 'identity_insert', Table cannot be a JVT. %1" | Tables of type JVT are not allowed as a value for the set option 'identity_insert' Click here for a list of possible parameters and odbc states. |
| -1000289L | Error | 20038 | QDC71 | "Invalid table argument %2 for set option 'identity_insert', Table must be an IQ table. %1" | Only IQ tables are allowed as an argument value to the set option 'identity_insert' Click here for a list of possible parameters and odbc states. |
| -1000290L | Error | 20039 | QDC72 | "Invalid table argument %2 for stored procedure sp_iq_reset_identity, Table must be an IQ Table. %1" | Only IQ tables are allowed as a table argument to the stored procedure sp_iq_reset_identity Click here for a list of possible parameters and odbc states. |
| -1000291L | Error | 20041 | QDC73 | "You do not have insert permission on table %2. %1" | You cannot set the option 'identity_insert' to a table for which you do not have insert permission Click here for a list of possible parameters and odbc states. |