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 |
|---|---|---|---|---|---|
| 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. |
| QCA54 | Error | 20624 | -1013054L | "Delimiter '%2' must be 1 to %3 characters in length. %1" | The row or column delimiter in a LOAD statement must be 1-4 characters. Click here for a list of possible parameters and odbc states. |
| QCA55 | Error | 20625 | -1013055L | "ON_ERROR = 'CONTINUE' is valid only for a full-width INSERT. %1" | ON_ERROR = 'CONTINUE' is valid only for a full width insert. Click here for a list of possible parameters and odbc states. |
| QCA56 | Error | 20626 | -1013056L | "FILLER width must be greater than zero. %1" | FILLER width must be greater than zero. Click here for a list of possible parameters and odbc states. |
| QCA57 | Error | 20627 | -1013057L | "ASCII input column width must be greater than zero. %1" | ASCII input column width must be greater than zero. Click here for a list of possible parameters and odbc states. |
| QCA58 | Error | 20628 | -1013058L | "The row delimiter must be distinct from all column delimiters. %1" | The row delimiter cannot be the same as any column delimiter. Click here for a list of possible parameters and odbc states. |
| QCA59 | Error | 20629 | -1013059L | "The BLOCK SIZE option is not valid for a fixed-width input insert. %1" | You cannot specify BLOCK SIZE for a fixed-width input insert. Click here for a list of possible parameters and odbc states. |
| QCA60 | Error | 20630 | -1013060L | "The BLOCK FACTOR option is not valid for a variable width input insert. %1" | You cannot specify BLOCK FACTOR for a variable width input insert. Click here for a list of possible parameters and odbc states. |
| QCA61 | Error | 20631 | -1013061L | "Missing row delimiter detected during a row delimited insert. %1" | The input data is missing a row delimiter. Click here for a list of possible parameters and odbc states. |
| QCA62 | Error | 20632 | -1013062L | "Expected '%2' delimited column type on input, but encountered a row delimiter instead. Probable cause is a mismatch between the specified column delimiter and the column delimiter used in the input file. %1" | A row delimiter, rather than a column, was encountered during a LOAD. Probable cause is a mismatch between the specified column delimiter and the column delimiter used in the input file. Click here for a list of possible parameters and odbc states. |
| QCA63 | Error | 20633 | -1013063L | "Expected raw-data column type '%2' on input, but no input data exists. %1" | No data was found during a scan of an input file during insert. Click here for a list of possible parameters and odbc states. |
| QCA64 | Error | 20634 | -1013064L | "Row delimiter not seen during scan of input file. At least one of the input rows is missing a terminator. %1" | A row delimiter has been omitted from an input file. Click here for a list of possible parameters and odbc states. |