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 |
---|---|---|---|---|---|
QNA44 | Error | 20029 | -1008035L | "Invalid datatype for Identity/Autoincrement Column %1." | The datatype used is not supported by Identity/Autoincrement column. Valid datatypes are bigint, unsigned bigint, integer, unsigned integer, smallint, tinyint, numeric scale 0 and decimal scale 0 Click here for a list of possible parameters and odbc states. |
QNA45 | Error | 20642 | -1008036L | "Table %1 already has an Identity/Autoincrement Column. " | An Identity/Autoincrement Column cannot be added to this table because it already has one. Click here for a list of possible parameters and odbc states. |
QNA46 | Error | 20643 | -1008037L | "Cannot drop %1 %2: set option 'identity_insert' must be off. " | option 'identity insert' must not be set to any table name to drop an Identity Column. To turn it off use 'set identity_insert '' ' Click here for a list of possible parameters and odbc states. |
QNA47 | Error | 21123 | -1008038L | "create schema command not allowed on an active multiplex server. " | the create schema command is not allowed on an active multiplex server Click here for a list of possible parameters and odbc states. |
QNA48 | Error | 22005 | -1008039L | "Permission denied: The current multiplex server is not a writer server" | The global command is not permitted on current multiplex node Click here for a list of possible parameters and odbc states. |
QNA49 | Error | 22016 | -1013113L | "The multiplex server '%2' is not included in the multiplex. %1" | This multiplex server has been excluded Click here for a list of possible parameters and odbc states. |
QNA50 | Error | 22017 | -1013114L | "To start a Secondary node in single-node mode (-iqmpx_sn 1) the override switch (-iqmpx_ov 1) should be used %1" | Secondary servers are not allowed to start with -iqmpx_sn 1. As the use of -iqmpx_sn 1 makes the server the owner of the IQ database it should not be used unless coordinator restore and failover operations have failed. If it becomes necessary to re-establish ownership of the database by a secondary server you can start the secondary server with -iqmpx_sn 1 only with override (-iqmpx_ov 1) Click here for a list of possible parameters and odbc states. |
QSA00 | Error | 20021 | -1009000L | "Bit %2 is unexpectedly on in bitmap. If the error persists, you may have a damaged index; please run sp_iqcheckdb. %1" | This is either an internal calling error (some component called bitmap SET with a duplicate bit), a corrupt bitmap (and dbcc needs be run), or a bitmap operator that has gone awry and mis-computed a result. Click here for a list of possible parameters and odbc states. |
QSA01 | Error | 20022 | -1009001L | "Bit %2 is unexpectedly off in bitmap. If the error persists, you may have a damaged index; please run sp_iqcheckdb. %1" | This is either an internal calling error (some component called bitmap CLEAR with a duplicate bit), a corrupt bitmap (and dbcc needs be run), or a bitmap operator that has gone awry and mis-computed a result. Click here for a list of possible parameters and odbc states. |
QSA04 | Error | 20025 | -1009004L | "Statistics context = %2 %3\n %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QSA12 | Error | 20033 | -1009012L | "Cannot create %2 index on a column having a datatype %3. %1" | A named index type index cannot be created on named datatype Click here for a list of possible parameters and odbc states. |
QSA19 | Error | 20040 | -1009019L | "An internal server component, a bitmap, was given invalid input. %1" | Some non-bitmap component has called a bitmap with an illegal argument. This is an internal programming error and not the (direct) result of customer error. Click here for a list of possible parameters and odbc states. |
QSA21 | Error | 20042 | -1009021L | "This server must first be started in Multiplex single-node mode (-iqmpx_sn 1) %1" | The tlv log has an incorrect format Click here for a list of possible parameters and odbc states. |
QSA22 | Error | 20043 | -1009022L | "Cannot create a WD index on a column narrower than 3 bytes. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QSA23 | Error | 20044 | -1009023L | "Cannot create a WD index on a column wider than 32767 bytes. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QSA24 | Error | 20045 | -1009024L | "Cannot create a WD index with a max permitted word size less than 1 byte. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QSA25 | Error | 20046 | -1009025L | "Cannot create a WD index with a max permitted word size greater than 255 bytes. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QSA26 | Error | 20047 | -1009026L | "Cannot create a WD index with a separator string this long. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QSA27 | Error | 20048 | -1009027L | "Cannot create a WD index with a separator string containing a character fragment. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QSA28 | Error | 20049 | -1009028L | "Cannot create a WD index with more than 256 separators. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |