Messages QCA33 through QCA52

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
QCA33 Error 20603 -1013033L "An error occurred while calling a method on db_sql_*_identifier. Object does not have an IJoinIndex handle. %1" This is an internal error. If this error occurs, it should be reported to Sybase.

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

QCA34 Error 20604 -1013034L "Cannot create an index with no columns. %1" You cannot create an index with no columns.

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

QCA35 Error 20605 -1013035L "The number of insert VALUES does not match the column list. %1" The number of columns in the INSERT does not match the number of of VALUES provided.

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

QCA36 Error 20606 -1013036L "The keyword 'FILLER' is not valid in this context. %1" You cannot use the 'FILLER' keyword here. No column can be of type 'FILLER' for a VALUES insert.

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

QCA37 Error 20607 -1013037L "The datatype of column '%2' is not valid. %1" The named column has an invalid datatype. If subsequent examination of the column definition reveals a datatype that is valid, then this error should be reported to Sybase.

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

QCA38 Error 20608 -1013038L "The number of columns given does not match. %1" The number of columns to be inserted does not match the number of columns in the insert. If this error persists, it should be reported to Sybase.

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

QCA39 Error 20609 -1013039L "An internal error occurred while constructing a db_sql_*_identifier. The IColumn handle does not belong to the ITable. %1" This error should not occur during normal operation. It is an internal error. If this error occurs, it should be reported to Sybase.

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

QCA40 Error 20610 -1013040L "Column '%2' in the INSERT list has no matching column in the SELECT list. %1" The named column in the INSERT list does not have a matching column in the SELECT list.

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

QCA41 Error 20611 -1013041L "Column '%2' in the SELECT list has no matching column in the INSERT list. %1" The named column in the SELECT list does not have a matching column in the INSERT list.

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

QCA42 Error 20612 -1013042L "An internal error occurred while constructing a db_sql_*_identifier. The IIndex handle does not belong to the ITable. %1" This error should not occur during normal operation. It is an internal error. If this error occurs it should be reported to Sybase.

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

QCA43 Error 20613 -1013043L "Unable to convert column '%2' to the requested datatype (%3) from datatype (%4). %1" This column cannot be converted to the requested datatype.

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

QCA44 Error 20614 -1013044L "An internal error occurred. An invalid table type was encountered. %1" This is an internal programming error. The table type was not correctly set to BASE, VIEW, JVT, TMP, LOCAL TMP for its context. If this error occurs it should be reported to Sybase.

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

QCA45 Error 20615 -1013045L "An invalid file name ('%2') was specified for a LOAD TABLE. The file name has zero length. %1" A file name of zero length was specified for LOAD TABLE.

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

QCA46 Error 20616 -1013046L "An internal error occurred. An invalid index type was encountered. %1" This error should not occur during normal operation. It is an internal error and should be reported to Sybase.

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

QCA47 Error 20617 -1013047L "Cannot alter index '%2'. Only indexes in base tables or global temporary tables can be altered. %1" Only indexes in base tables and global temporary tables listed in SYS.SYSINDEX can be altered.

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

QCA48 Error 21037 -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.

QCA49 Error 21039 -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.

QCA50 Error 20620 -1013050L "The Temp_Extract_Name1 option is set. The current operation will be rolled back. %1" Certain operations will not be allowed whenever the Temp_Extract_Name1 option is set. They are: INSERT...VALUES, LOAD, DELETE, and INSERT...LOCATION if the table being inserted, SYNCHRONIZE join index. (Which also may be executed as part of CREATE JOIN INDEX.) loaded or deleted from is the top table in a join. INSERT...SELECT. For example, 'insert t1 select * from t2'.

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

QCA51 Error 21061 -1009141L "Table '%2' cannot be found in the IQ store. %1" The stored procedure sp_iqtablesize cannot find the table. This stored procedure is for IQ tables only. It cannot be run against system tables or ASA tables.

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

QCA52 Error 20622 -1013052L "The BLOCK FACTOR for LOAD cannot be zero. %1" The BLOCK FACTOR for LOAD cannot be zero.

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


Created April 27, 2010. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com