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 |
|---|---|---|---|---|---|
| QCB12 | Error | 21052 | -1009414L | "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. |
| QCB13 | Error | 21053 | -1009415L | "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. |
| QCB14 | Error | 21054 | -1009416L | "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. |
| QCB15 | Error | 21055 | -1009417L | "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. |
| QCB16 | Error | 21056 | -1009418L | "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. |
| QCB17 | Warning | 21149 | 1000297L | "%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. |
| QCB18 | Warning | 21150 | 1000298L | " 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. |
| QCB19 | Error | 21159 | -1009419 | "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. |
| QCB20 | Error | 21160 | -1009420L | "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. |
| QCB87 | Error | 20847 | -1000187L | "Unable to implicitly convert column '%2' to datatype (%3) from datatype (%4). %1" | The attempted implicit conversion is not possible. The conversion must be done explicitly. If implicit conversion is being attempted to or from a NUMERIC and this error results, the datatype displayed in the error for the NUMERIC will be SMALLINT, INT, or INT64 depending on the precision of the NUMERIC. This is because NUMERICs are treated internally as multiple precision signed integers. Click here for a list of possible parameters and odbc states. |
| QCC00 | Error | 22001 | -1013103L | "%2 not implemented %1" | This feature has not been implemented Click here for a list of possible parameters and odbc states. |
| QDA00 | Error | 20660 | -1000000L | "ESCAPES option must be OFF. %1" | Sybase IQ only supports 'LOAD TABLE' commands where the ESCAPES options must be OFF. Click here for a list of possible parameters and odbc states. |
| QDA02 | Error | 20662 | -1000002L | "Cannot get the index id for %2 from the catalog. %1" | This is an internal error. Join processing is not able to find an index in the catalog. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA03 | Error | 20663 | -1000003L | "Cross-database joins are not supported. (%2 and %3) %1" | Cannot join tables from different databases. Click here for a list of possible parameters and odbc states. |
| QDA04 | Error | 20664 | -1000004L | "Index '%2' already exists in the catalog. %1" | This is an internal error. Join processing is trying to create an index id that already exists. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA05 | Error | 20665 | -1000005L | "Join index '%2' already exists and has the same join fields as proposed join index '%3'. %1" | The user is trying to create a join index that already exists and has the same join fields. Click here for a list of possible parameters and odbc states. |
| QDA06 | Error | 20666 | -1000006L | "Only %2 NULL specifications on a column are permitted. %1" | A column specification in a LOAD statement can have a maximum number of NULL clauses. Click here for a list of possible parameters and odbc states. |
| QDA07 | Error | 20667 | -1000007L | "Index '%2' was not closed properly. %1" | This is an internal error. During close join index processing, a join index was not properly closed. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA08 | Error | 20668 | -1000008L | "Unknown error. %1" | An error condition was encountered for which there is no message. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA09 | Error | 20669 | -1000009L | "Cannot DISABLE index '%2'. It is open Read/Write and may have updates pending. %1" | This index cannot be DISABLED. It is open for write access and may have updates pending. Wait until no other users are using the index. Click here for a list of possible parameters and odbc states. |