Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 20014 | Error | QXA00 | -1010000L | "The file '%2' already exists. %1" | The named dbspace already exists (and it is a raw partition). To proceed, you must first remove it by hand. Click here for a list of possible parameters and odbc states. |
| 20015 | Error | QXA01 | -1010001L | "Cannot use raw partition for dbspace file '%2'. %1" | The named dbspace cannot exist on a raw partition. Click here for a list of possible parameters and odbc states. |
| 20016 | Error | QXA02 | -1010002L | "File format mismatch; database %2; Sybase IQ: %3. %1" | The file format of the database doesn't match the file format as expected by the IQ DLL. The IQ DLL and the database each have a format version. They must match. Click here for a list of possible parameters and odbc states. |
| 20017 | Error | QXA03 | -1010003L | "Catalog format mismatch: database %2; Sybase IQ: %3. %1" | The catalog format of the database doesn't match the catalog format as expected by the IQ DLL. The IQ DLL and the ASA catalog each have a format version. They must match. Click here for a list of possible parameters and odbc states. |
| 20018 | Error | QXA04 | -1010004L | "Stored procedure format mismatch: database %2; Sybase IQ: %3. %1" | The stored procedure format of the database doesn't match the stored procedure format as expected by the IQ DLL. The IQ DLL and the database each contain a stored procedure format version. They must match. Click here for a list of possible parameters and odbc states. |
| 20019 | Error | QXA05 | -1010005L | "File format date mismatch: database %2; Sybase IQ: %3. %1" | The file format date of the database doesn't match the file format date as expected by the IQ DLL. Click here for a list of possible parameters and odbc states. |
| 20020 | Error | QXA06 | -1010006L | "Maximum blocks for dbspace '%2' is %3 blocks. %4 blocks were specified. (Database blocksize is %5.) %1" | Given a database's BLOCK SIZE and the number of blocks specified by the user for the dbspace, the dbspace size (in bytes) would exceed the OS's limit of bytes per file. Click here for a list of possible parameters and odbc states. |
| 20021 | Error | QSA00 | -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. |
| 20022 | Error | QSA01 | -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. |
| 20023 | Warning | 00002 | 1009002L | " Index %2: Starting Insert Pass 2. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20024 | Warning | 00003 | 1009003L | " Index %1: Thread %2 Inserting %3 Recs, %4 Secs." | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20025 | Error | QSA04 | -1009004L | "Statistics context = %2 %3\n %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20026 | Error | QNA41 | -1008032L | "Foreign keys disallowed on Identity/Autoincrement Columns when set option identity_enforce_uniqueness is on" | An Identity/Autoincrement Column cannot be a foreign key when the set option identity_enforce_uniqueness is on. Either turn the option off, or chose a different column for the foreign key. Click here for a list of possible parameters and odbc states. |
| 20027 | Error | QNA42 | -1008033L | "Identity/Autoincrement Column %1 has Invalid datatype: scale must be 0." | Identity/Autoincrement Columns defined as datatype numeric must have scale 0 Click here for a list of possible parameters and odbc states. |
| 20028 | Error | QNA43 | -1008034L | "Cannot add an Identity/Autoincrement Column to table %1, it participates in a join index." | Adding an Identity/Autoincrement Column to a table that participates in a join index is not allowed, to perform this operation, the join index must be dropped Click here for a list of possible parameters and odbc states. |
| 20029 | Error | QNA44 | -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. |
| 20030 | Error | QDC65 | -1000283L | "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. |
| 20032 | Error | QDC66 | -1000284L | "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. |
| 20033 | Error | QSA12 | -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. |
| 20034 | Error | QDC67 | -1000285L | "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. |