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 |
|---|---|---|---|---|---|
| -1010046L | Error | 21148 | QXA45 | "Plan not available. The database option QUERY_PLAN_TEXT_ACCESS is off." | "The plan can be accessed on the client by the user only when DBA sets option QUERY_PLAN_TEXT_ACCESS to ON for the user." Click here for a list of possible parameters and odbc states. |
| -1010047L | Error | 21176 | QXA46 | "%1 is not designated as failover server" | Failover process is started on a server which is not designated as failover server Click here for a list of possible parameters and odbc states. |
| -1010048L | Error | 21177 | QXA47 | "iqmpx_failover and iqmpx_sn switches cannot be enabled simultaneously" | While starting an IQ server, both iqmpx_failover and iqmpx_sn command line server switches are ON. Click here for a list of possible parameters and odbc states. |
| -1010049L | Error | 21178 | QXA48 | "Transaction log recovery not allowed during failover. Please restart the server without the failover switch, do a clean shutdown, restart failover" | The failover process should be started only after clean shutdown of the server. If recovery process is initiated during failover then the server was not shut down cleanly and failover should be restarted after the server is restarted and shut down without the failover switch. Click here for a list of possible parameters and odbc states. |
| -1010050L | Error | 21179 | QXA49 | "Recovery required to complete the last failover process. Please restart the server with failover switch" | A previous failover attempt did not finish cleanly. The failover changes must be recovered and to do that restart the server with failover switch. Click here for a list of possible parameters and odbc states. |
| -1010051L | Error | 21180 | QXA50 | "Failover node catalog is not in sync with TLV log. Please restart server without failover switch, run BEGIN TRANSACTION, do a clean shutdown, then restart failover " | The failover process can be started only if the failover node's catalog is up to date with the TLV log. To fix this, restart the server without the failover switch, run BEGIN TRANSACTION, do a clean shutdown, then restart the server with the failover switch. Click here for a list of possible parameters and odbc states. |
| -1010052L | Error | 21183 | QXA51 | "Only one dbspace file may be added at a time for multiplex servers" | When using ALTER DBSPACE to add a file to a multiplex server, only one file may be added at a time. Specifying a list of files to add is not supported. Click here for a list of possible parameters and odbc states. |
| -1010053L | Error | 21184 | QXA52 | "DBSPACE command extended syntax not permitted" | When using ALTER DBSPACE command, extended syntax is not allowed on a user connection Click here for a list of possible parameters and odbc states. |
| -1010054L | Error | 21186 | QXA53 | "Server option '-iqmpx_ov' only valid when used with '-iqmpx_sn' or '-iqmpx_failover'. %1" | Server option '-iqmpx_ov' is permitted on an Multiplex coordinator node or in combination with either '-iqmpx_sn' or '-iqmpx_failover' on any other Multiplex node type. Click here for a list of possible parameters and odbc states. |
| -1010055L | Error | 21187 | QXA54 | "iqmpx_reclaimwriterfreelist server switch can not be used in Simplex or Secondary nodes" | iqmpx_reclaimwriterfreelist server switch can only be used on a Coordinator node. Click here for a list of possible parameters and odbc states. |
| -1010056L | Error | 21188 | QXA55 | "Recovery switch '-iqfrec' is allowed on a multiplex server only in single-node operating mode. %1" | Recovery switch '-iqfrec' is allowed on a multiplex server only in single-node operating mode. Click here for a list of possible parameters and odbc states. |
| -1010057L | Error | 21201 | QXA56 | "'%2' command is not allowed on temp store files, when server started with -iqnotemp switch. %1" | When the server is running with -iqnotemp switch, certain alter dbspace operations are not allowed. For e.g. alter dbspace add file. Click here for a list of possible parameters and odbc states. |
| -1010058L | Error | 21202 | QXA57 | "Unable to perform forced recovery when database is in read only mode. %1" | Recovery switch '-iqfrec' is allowed on read/write databases only Click here for a list of possible parameters and odbc states. |
| -1011000L | Error | 20000 | QVA00 | "Vertical Projection Cursor state error %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| -1011001L | Error | 20001 | QVA01 | "Cannot find index for a given dfe %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| -1011002L | Error | 20002 | QVA02 | "The number of existing indexes exceeds the current maximum number of indexes. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| -1011003L | Error | 20003 | QVA03 | "Vertical Projection Cursor does not support AD-HOC joins. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| -1011004L | Error | 20004 | QNA27 | "Cannot drop primary key or unique constraint because a foreign key still references it." | A primary key or unique constraint involved in a referential integrity relationship cannot be dropped until its corresponding foreign key is first dropped. Click here for a list of possible parameters and odbc states. |
| -1011005L | Error | 20005 | QVA05 | "Force_Drop of a Join Index is not allowed on a multiplex coordinator. %1" | A join index cannot be dropped on a multiplex coordinator when the Force_Drop option is set to 'ON'. If it is necessary to force drop a join index on a multiplex coordinator, the server will first need to be brought up in simplex mode. Click here for a list of possible parameters and odbc states. |
| -1011006L | Error | 20006 | QVA06 | "the pattern argument in a like predicate must have string datatype." | No additional information available. Click here for a list of possible parameters and odbc states. |