Messages 21021 through 21041

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
21021 Error QCB01 -1013101L "You do not have permission to drop this join index. %1" You do not have permission to drop this join index.

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

21022 Error QCB02 -1013102L "User name '%2' does not exist. %1" The specified user does not exist.

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

21023 Error QSB34 -1009134L "Insufficient buffers for '%2'. %1" No additional information available.

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

21024 Warning 00A13 1010013L "IQ cannot support the %1 connections requested by the server.\nRestart the server with -gm %2 on the command line." Inform the DBA about the number of connection

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

21025 Error QXA13 -1010013L "Raw partition %2 is already in use. %1" User attempted to create dbspace on a raw partition which is currently in use by the database.

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

21026 Warning QCB03 1013103L "JI MATCH E=%1;S=%2;TID=%3;NRows=%4;JID=%5;NTab=%6;Miss=%7;Data=%8" During a SELECT the Join Indexs are searched for a good match to increase the speed of the query. This message relays the scoring given to each table/join index matched.

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

21027 Warning QCB04 1013104L "JI NOMATCH - Entry=%1, Table=%2, Join=%3" During a SELECT the Join Indexs are searched for a good match to increase the speed of the query. This message relays that this join has not been selected.

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

21028 Warning QCB05 1013105L "JI MATCH COMPARING - E=%1, MP=%2, JID=%3, Name=%4" During a SELECT the Join Indexs are searched for a good match to increase the speed of the query. This message relays that this join is being compared to the others.

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

21029 Warning QCB06 1013106L "JI MATCH SELECTED - MP=%1, JID=%2, Name=%3" During a SELECT the Join Indexs are searched for a good match to increase the speed of the query. This message relays that this join has been selected.

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

21030 Warning QCB07 1013107L "JI MATCH EXACT - This join exactly matches the requested tree" During a SELECT the Join Indexs are searched for a good match to increase the speed of the query. This message relays that this join completely replaces the requested tree.

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

21031 Warning QCB08 1013108L "JI MATCH - Building Match List for Table ID=%1, Name=%2" During a SELECT the Join Indexs are searched for a good match to increase the speed of the query. This message relays that this table will be queried for joins that it participates.

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

21032 Warning QCB09 1013109L "JI MATCH - Join Index ID=%1, Name=%2, TopTableID=%3" During a SELECT the Join Indexs are searched for a good match to increase the speed of the query. This message relays that this join will attempt to be matched during the match-up process.

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

21033 Warning QSB35 1013110L "IQ had insufficient memory to create the buffer cache with the size specified with the Main_Cache_Memory_MB or Temp_Cache_Memory_MB options. Instead, the cache will be created using the default size." If we catch an OUTOFMEMORY exception when creating the MAIN or the TEMP buffer cache, we report this warning of our failure and retry to create the cache with the default settings (and NOT the settings in the hos_paramset). This will allow the DBA to re-open a database even if the Main_Cache_Memory_MB or Temp_Cache_Memory_MB options are set so high as to otherwise prevent the re-opening of the database. (QTS 183253.)

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

21034 Error QSB36 -1009135L "Cannot perform requested command as there is a CREATE DBSPACE command in progress. %1" A CREATE DBSPACE or a DROP DBSPACE command was issued when there was already a DROP DBSPACE command in progress.

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

21035 Error QSB37 -1009136L "Cannot perform requested command as there is a DROP DBSPACE command in progress. %1" A CREATE DBSPACE or a DROP DBSPACE command was issued when there was already an ALTER DBSPACE command in progress.

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

21036 Error QDC55 -1009137L "Cannot perform DDL command now on table %2 as a DDL command is already in progress on that table. %1" There is already a DDL command in progress at the moment on the table specified and you must wait until it is finished before starting another DDL command on that table.

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

21037 Error QCA48 -1009138L "Join index '%2' is in use. %1" Cannot drop a join index that is in use.

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

21038 Error QSB38 -1009139L "Cannot perform requested command as there is a CHECKPOINT command in progress. %1" A CREATE DBSPACE or a DROP DBSPACE command was issued when there was already a CHECKPOINT command in progress.

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

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.


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