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 |
|---|---|---|---|---|---|
| -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. |
| -1000292L | Error | 20474 | QDC74 | "Invalid use of set option 'identity insert'. Table %2 does not have an Identity/Autoincrement Column. %1" | the set option 'identity insert' cannot be used on a table without an Identity/Autoincrement Column. Click here for a list of possible parameters and odbc states. |
| -1000293L | Error | 20644 | QDC75 | "Cannot insert or update Column %2: set option 'identity_insert' to the specific table name containing the identity column to be modified. %1" | set option 'identity_insert' must be set to the specific table for which you want to insert or update an Identity column. To turn it on use set identity_insert <table_name> Click here for a list of possible parameters and odbc states. |
| -1000294L | Error | 20645 | QDC76 | "Cannot set 'identity_insert', it is already on for a different table. %1" | the set option 'identity_insert' can only be set for one table at a time. To set it for a different table, first turn it off using 'set identity_insert '' ' then set it to the desired table. Click here for a list of possible parameters and odbc states. |
| -1000295L | Error | 20646 | QDC77 | "Invalid table name %2 specified for option 'identity_insert'. %1" | The table associated with the table name specified for the 'identity_insert' option could not be found. Click here for a list of possible parameters and odbc states. |
| -1000296L | Error | 21124 | QDC78 | " Invalid load specification for LOAD ... FORMAT BCP. %1" | The user specified a load specification that is not supported with FORMAT BCP option. Click here for a list of possible parameters and odbc states. |
| 1000297L | Warning | 21149 | QCB17 | "%1. Message logging stopped." | Message log management operation failed due to error in file renaming / deletion / creation. Or log could not be written in the IQMSG file because some DISK IO error occurred. Click here for a list of possible parameters and odbc states. |
| 1000298L | Warning | 21150 | QCB18 | " Message logging resumed." | Engine has detected that reason behind message log management / message logging failure has been resolved. Message logging is resumed now. Click here for a list of possible parameters and odbc states. |
| -1000299L | Error | 21152 | QDC79 | " Partition key of %2 is unsupported. %1" | Partiiton key of LOB/CLOB/char/varchar/binary/varbinary over 255 is not supported. Click here for a list of possible parameters and odbc states. |
| -1000300L | Error | 21153 | QDC80 | " Table that participates in a join index cannot be partitioned. %1" | A partitioned table cannot participate in join. Click here for a list of possible parameters and odbc states. |
| -1000301L | Error | 21154 | QDC81 | " Join index cannot be created on a partitioned table. %1" | Join index cannot be created on a partitioned table. Click here for a list of possible parameters and odbc states. |
| -1000302L | Error | 21155 | QDC82 | " Exceed maximum number of partitions. %1" | Exceed maximum number of partitions. Click here for a list of possible parameters and odbc states. |
| -1000303L | Error | 21156 | QDC83 | " Object %2 not usable in current context. %1" | Table of TBLTYP_PARTITION type cannot be used. Click here for a list of possible parameters and odbc states. |
| -1000304L | Error | 21157 | QDC84 | " Cannot drop a partition key column. %1" | Can not drop a partition key column. Click here for a list of possible parameters and odbc states. |