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 |
|---|---|---|---|---|---|
| 21039 | Error | QCA49 | -1009140L | "Cannot restore dbspace '%2' to raw partition '%3' because its size is smaller than the size of the original raw partition (%4 vs. %5 blocks). %1" | This error means that the user is attempting to restore an IQ dbspace on a raw partition that is not the same size as the original raw partition on which the IQ dbspace existed at the time of the backup. The user must resize the raw partition and then retry the restore operation. Click here for a list of possible parameters and odbc states. |
| 21041 | Error | QNA19 | -1008019L | "Multiplex is currently inactive." | The user has either requested a multiplex function or has asked for multiplex status. Click here for a list of possible parameters and odbc states. |
| 21042 | Error | QNA20 | -1008020L | "Multiplex command or request is unimplemented." | The user has requested an unimplemented multiplex feature. This would typically be a status request which doesn't exist. Click here for a list of possible parameters and odbc states. |
| 21043 | Error | QNA21 | -1008021L | "The SYSIQFILE table is not configured for this server to run in a multiplex." | SYSIQFILE identifies all files which make up the given stores that the IQ server requires (main, temp, and message). For multiplex, each entry in SYSIQFILE must be associated with a particular multiplex server before that server can access the particular file. This message indicates that some these rows are missing for the active server. Click here for a list of possible parameters and odbc states. |
| 21044 | Error | QNA22 | -1008022L | "Bad commit identity block. The server may be out of synchronization. %1" | Multiplex servers cannot start this database. Start the coordinator in single server mode. Click here for a list of possible parameters and odbc states. |
| 21045 | Error | QNA23 | -1008023L | "Cannot start multiplex secondary server while the coordinator is in single server mode" | Restart the secondary server after the coordinator has restarted in normal mode. Click here for a list of possible parameters and odbc states. |
| 21046 | Error | QNA24 | -1008024L | "Multiplex coordinator must start as server@host: %2, on file: %3; to start with different settings, you must use the override switch. %1" | Only the configured coordinator can start the database. Start with the override switch (-iqmpx_ov 1) to bypass this check. Click here for a list of possible parameters and odbc states. |
| 21047 | Error | QNA25 | -1008025L | "Multiplex secondary server cannot continue while the coordinator is in single server mode. %1" | Resynchronize and restart the secondary server after the coordinator has restarted in normal mode. Click here for a list of possible parameters and odbc states. |
| 21048 | Error | QNA26 | -1008026L | "Multiplex secondary server out of synchronization with the coordinator. %1" | The secondary server's IQ catalog cannot be brought up to date with the coordinator's IQ catalog. This server must be synchronized. Click here for a list of possible parameters and odbc states. |
| 21049 | Error | QSB44 | -1009148L | "Cannot use -iqfrec to start a multiplex secondary server. %1" | A sp_iqcheckdb procedure call was issued on an IQ multiplex secondary server, or it was started in drop-leaks or forced recovery mode. These operations are only allowed on the coordinator Click here for a list of possible parameters and odbc states. |
| 21050 | Error | QCB10 | -1009412L | "The INSERT ... LOCATION statement must use a SELECT statement. %1" | The INSERT ... LOCATION statement must use a SELECT statement. No other SQL statement is supported here. Click here for a list of possible parameters and odbc states. |
| 21051 | Error | QCB11 | -1009413L | "Secondary server cannot maintain catalog sync. %1" | An error has occurred while applying catalog updates from the coordinator. The secondary server must be restarted or synchronized. Click here for a list of possible parameters and odbc states. |
| 21052 | Error | QCB12 | -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. |
| 21053 | Error | QCB13 | -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. |
| 21054 | Error | QCB14 | -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. |
| 21055 | Error | QCB15 | -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. |
| 21056 | Error | QCB16 | -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. |
| 21057 | Error | QNA28 | -1008027L | "Multiplex secondary node shutting down due to a file added to the IQ_SYSTEM_MAIN dbspace.\nThis node must be synchronized and restarted. %1" | The user has added a dbspace file to IQ_SYSTEM_MAIN on the coordinator. This causes secondary nodes to shut down. All secondary nodes must be synchronized and restarted after this operation. Click here for a list of possible parameters and odbc states. |
| 21058 | Warning | QXA14 | 1010014L | "Default cache size is used for command %1." | warning is issued for the command that uses the default cache size Click here for a list of possible parameters and odbc states. |
| 21059 | Error | QNA29 | -1008029L | "Cannot create foreign key to an unenforced primary key or unenforced unique constraint." | Existing unenforced primary keys or unique constraints cannot be used to create an referential integrity relationship to a foreign table. Click here for a list of possible parameters and odbc states. |