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 |
|---|---|---|---|---|---|
| 20620 | Error | QCA50 | -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. |
| 20621 | Error | QNA01 | -1008001L | "The user cannot create indexes on a join virtual table." | Users cannot create indexes on a join virtual table. They are automatically created. Click here for a list of possible parameters and odbc states. |
| 20622 | Error | QCA52 | -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. |
| 20623 | Error | QNA02 | -1008002L | "There is a join index using table '%1'. The table cannot be dropped until the join index is dropped or altered." | There is at least one join index using this table in a join relationship. The table cannot be dropped until the join index is dropped or it is altered such that it no longer uses this table. Click here for a list of possible parameters and odbc states. |
| 20624 | Error | QCA54 | -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. |
| 20625 | Error | QCA55 | -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. |
| 20626 | Error | QCA56 | -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. |
| 20627 | Error | QCA57 | -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. |
| 20628 | Error | QCA58 | -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. |
| 20629 | Error | QCA59 | -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. |
| 20630 | Error | QCA60 | -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. |
| 20631 | Error | QCA61 | -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. |
| 20632 | Error | QCA62 | -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. |
| 20633 | Error | QCA63 | -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. |
| 20634 | Error | QCA64 | -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. |
| 20635 | Error | QCA65 | -1013065L | "Row delimiter '%2' and column delimiter '%3' cannot be substrings of each other. %1" | Row and column delimiters cannot be substrings of each other. Click here for a list of possible parameters and odbc states. |
| 20636 | Error | QCA66 | -1013066L | "The %2 load option can be specified only once. %1" | The named load option can be specified only once per LOAD statement. Click here for a list of possible parameters and odbc states. |
| 20637 | Error | QCA67 | -1013067L | "Option CONVERSION ERROR must be OFF when IGNORE CONSTRAINT DATA VALUE or ALL is specified. %1" | When IGNORE CONSTRAINT DATA VALUE or ALL is given on a load statement, the database option CONVERSION ERROR must be off. Click here for a list of possible parameters and odbc states. |
| 20638 | Error | QCA68 | -1013068L | "Constraint '%2' violated: Invalid value for column '%3' in table '%4'. %1" | The Data being inserted or updated is invalid due to a column check constraint violation. Click here for a list of possible parameters and odbc states. |
| 20639 | Error | QNA03 | -1008003L | "Cannot drop join virtual table '%1'." | The user is not allowed to drop a join virtual table. It can be dropped by dropping the join index. Click here for a list of possible parameters and odbc states. |