Messages 1010052 through 1011009

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
-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.

-1010059L Error 22023 QXA58 "Unable to open the multiplex database. The database can only be opened by starting the Coordinator server using single node mode switch '-iqmpx_sn 1'. %1" An older version of multiplex database can only be opened bystarting the server in single node mode. If you upgraded the database when server was started using '-iqro 1', then database still needs to be opened by booting the coordinator server in single node mode but without '-iqro 1'. This is because internal IQ on-disk structures could not be upgraded earlier. To complete the upgrade, open the database by starting the coordinator server using single node mode switch '-iqmpx_sn 1', but without '-iqro 1'. After a clean shutdown, the database can then be started normally.

Click here for a list of possible parameters and odbc states.

-1010060L Error 21212 QXA60 "Server option -iqmpx_nowr only allowed when there are no writers in multiplex %1" Please restart coordinator without -iqmpx_nowr switch to add a writer

Click here for a list of possible parameters and odbc states.

-1010061L Error 21213 QXA61 "Server switch -iqmpx_nowr only allowed on coordinator node %1" Please restart the server without -iqmpx_nowr switch

Click here for a list of possible parameters and odbc states.

-1010062L Error 22029 QXA62 "Unable to open the database. Start the coordinator server first, without server option -iqro, to complete the Database Upgrade. %1" As IQ store was opened in RO mode when you upgraded the database, some of its internal meta-data information could not be upgraded to new format. Please start the coordinator server first, without server option -iqro, to complete the IQ side upgrade and continue.

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.

-1011007L Error 20007 QVA07 "the escape argument in a like predicate must be a one byte character." No additional information available.

Click here for a list of possible parameters and odbc states.

-1011009L Error 20009 QVA09 "Group (L)" No additional information available.

Click here for a list of possible parameters and odbc states.


Created May 6, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com