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 |
|---|---|---|---|---|---|
| 2993 | Error | 0AWD5 | -1305L | "MobiLink communication error; code: %1, parameter: %2, system code %3" | An error was encountered while communicating with a MobiLink server. Click here for a list of possible parameters and odbc states. |
| 2994 | Error | WW238 | -1306L | "IN DBSPACE clause cannot be used for column '%1' since table '%2' is a partitioned table." | Entire column cannot be assigned to a dbspace using the IN DBSPACE clause, if the table is a partitioned table. Click here for a list of possible parameters and odbc states. |
| 20000 | Error | QVA00 | -1011000L | "Vertical Projection Cursor state error %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20001 | Error | QVA01 | -1011001L | "Cannot find index for a given dfe %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20002 | Error | QVA02 | -1011002L | "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. |
| 20003 | Error | QVA03 | -1011003L | "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. |
| 20004 | Error | QNA27 | -1011004L | "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. |
| 20005 | Error | QVA05 | -1011005L | "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. |
| 20006 | Error | QVA06 | -1011006L | "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. |
| 20007 | Error | QVA07 | -1011007L | "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. |
| 20009 | Error | QVA09 | -1011009L | "Group (L)" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20010 | Error | QVA10 | -1011010L | "Group (S)" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20011 | Error | QVA11 | -1011011L | "Aggregate (L)" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20012 | Error | QVA12 | -1011012L | "Aggregate (S)" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20013 | Error | QVA13 | -1011013L | "Projection" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20014 | Error | QXA00 | -1010000L | "The file '%2' already exists. %1" | The named dbspace already exists (and it is a raw partition). To proceed, you must first remove it by hand. Click here for a list of possible parameters and odbc states. |
| 20015 | Error | QXA01 | -1010001L | "Cannot use raw partition for dbspace file '%2'. %1" | The named dbspace cannot exist on a raw partition. Click here for a list of possible parameters and odbc states. |
| 20016 | Error | QXA02 | -1010002L | "File format mismatch; database %2; Sybase IQ: %3. %1" | The file format of the database doesn't match the file format as expected by the IQ DLL. The IQ DLL and the database each have a format version. They must match. Click here for a list of possible parameters and odbc states. |
| 20017 | Error | QXA03 | -1010003L | "Catalog format mismatch: database %2; Sybase IQ: %3. %1" | The catalog format of the database doesn't match the catalog format as expected by the IQ DLL. The IQ DLL and the ASA catalog each have a format version. They must match. Click here for a list of possible parameters and odbc states. |
| 20018 | Error | QXA04 | -1010004L | "Stored procedure format mismatch: database %2; Sybase IQ: %3. %1" | The stored procedure format of the database doesn't match the stored procedure format as expected by the IQ DLL. The IQ DLL and the database each contain a stored procedure format version. They must match. Click here for a list of possible parameters and odbc states. |