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 |
|---|---|---|---|---|---|
| -1009414L | Error | 21052 | QCB12 | "Secondary server cannot recover catalog during post-synchronization. %1" | An error has occurred while reconstituting catalog entries for the IQ Local store. Manual repair is required. Click here for a list of possible parameters and odbc states. |
| -1009415L | Error | 21053 | QCB13 | "CREATE TABLE cannot use IN clause for IQ Local store. %1" | You may not specify the IN clause to create tables in IQ Local store. Without an IN clause, the secondary server create tables in Local store by default. Click here for a list of possible parameters and odbc states. |
| -1009416L | Error | 21054 | QCB14 | "Option '%2' not allowed on a partitioned table. %1" | Certain 'load table' options are not supported on a partitioned table. Click here for a list of possible parameters and odbc states. |
| -1009417L | Error | 21055 | QCB15 | "Updating partition key column on a partitioned table is not allowed. %1" | A partition key column cannot be updated. Click here for a list of possible parameters and odbc states. |
| -1009418L | Error | 21056 | QCB16 | "Operation not allowed - partition key column %2 not specified. %1" | A partial width insert on a partitioned table is not permitted when at least one of the table's partition key columns is omitted. Click here for a list of possible parameters and odbc states. |
| -1009419 | Error | 21159 | QCB19 | "The width of one or more columns are too large to fit into database's page." | The LOAD Engine cannot fit a column into the page. Click here for a list of possible parameters and odbc states. |
| -1009420L | Error | 21160 | QCB20 | "Value of row's partition-key columns do not fit into any of the table's partitions." | The value for the partition key columns for a specific row do not fit within any of the table's partitions. Click here for a list of possible parameters and odbc states. |
| -1010000L | Error | 20014 | QXA00 | "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. |
| -1010001L | Error | 20015 | QXA01 | "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. |
| -1010002L | Error | 20016 | QXA02 | "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. |
| -1010003L | Error | 20017 | QXA03 | "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. |
| -1010004L | Error | 20018 | QXA04 | "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. |
| -1010005L | Error | 20019 | QXA05 | "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. |
| -1010006L | Error | 20020 | QXA06 | "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. |
| -1010007L | Error | 20980 | QXA07 | "The number of blocks (%3) for dbspace '%2' must be less than or equal to the number of blocks in the raw partition (%4). %1" | When creating a dbspace on a raw partition, if the user specifies the dbspace's size, then it must exactly match the size of the raw partition. Click here for a list of possible parameters and odbc states. |
| -1010008L | Error | 20981 | QXA08 | "For an IQ PAGE SIZE of %2, the dbspace '%3' must have at least %4 MB. %1" | The named dbspace must have the stated minimum size in megabytes. Click here for a list of possible parameters and odbc states. |
| -1010009L | Error | 21005 | QXA09 | "Improper use of cursor - programmer error %1" | The programmer has misused the internal cursor class(es) Click here for a list of possible parameters and odbc states. |
| -1010010L | Error | 21006 | QXA10 | "An invalid attribute flag was passed to the cursor" | A state violation was detected in the cursor Click here for a list of possible parameters and odbc states. |
| -1010011L | Error | 21007 | QXA11 | "Not enough server threads available for this query." | No thread could be allocated to allow this query to be executed Click here for a list of possible parameters and odbc states. |
| -1010012L | Error | 21008 | QXA12 | "The cursor is in an invalid state %1" | A state violation was detected in the cursor Click here for a list of possible parameters and odbc states. |