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 |
|---|---|---|---|---|---|
| QCB87 | Error | 20847 | -1000187L | "Unable to implicitly convert column '%2' to datatype (%3) from datatype (%4). %1" | The attempted implicit conversion is not possible. The conversion must be done explicitly. If implicit conversion is being attempted to or from a NUMERIC and this error results, the datatype displayed in the error for the NUMERIC will be SMALLINT, INT, or INT64 depending on the precision of the NUMERIC. This is because NUMERICs are treated internally as multiple precision signed integers. Click here for a list of possible parameters and odbc states. |
| QCC00 | Error | 22001 | -1013103L | "%2 not implemented %1" | This feature has not been implemented Click here for a list of possible parameters and odbc states. |
| QDA00 | Error | 20660 | -1000000L | "ESCAPES option must be OFF. %1" | Sybase IQ only supports 'LOAD TABLE' commands where the ESCAPES options must be OFF. Click here for a list of possible parameters and odbc states. |
| QDA02 | Error | 20662 | -1000002L | "Cannot get the index id for %2 from the catalog. %1" | This is an internal error. Join processing is not able to find an index in the catalog. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA03 | Error | 20663 | -1000003L | "Cross-database joins are not supported. (%2 and %3) %1" | Cannot join tables from different databases. Click here for a list of possible parameters and odbc states. |
| QDA04 | Error | 20664 | -1000004L | "Index '%2' already exists in the catalog. %1" | This is an internal error. Join processing is trying to create an index id that already exists. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA05 | Error | 20665 | -1000005L | "Join index '%2' already exists and has the same join fields as proposed join index '%3'. %1" | The user is trying to create a join index that already exists and has the same join fields. Click here for a list of possible parameters and odbc states. |
| QDA06 | Error | 20666 | -1000006L | "Only %2 NULL specifications on a column are permitted. %1" | A column specification in a LOAD statement can have a maximum number of NULL clauses. Click here for a list of possible parameters and odbc states. |
| QDA07 | Error | 20667 | -1000007L | "Index '%2' was not closed properly. %1" | This is an internal error. During close join index processing, a join index was not properly closed. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA08 | Error | 20668 | -1000008L | "Unknown error. %1" | An error condition was encountered for which there is no message. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA09 | Error | 20669 | -1000009L | "Cannot DISABLE index '%2'. It is open Read/Write and may have updates pending. %1" | This index cannot be DISABLED. It is open for write access and may have updates pending. Wait until no other users are using the index. Click here for a list of possible parameters and odbc states. |
| QDA10 | Error | 20670 | -1000010L | "Cannot DISABLE index '%2'. The index is in use. %1" | This index cannot be DISABLED. It is in use. Wait until no other users are using the index. Click here for a list of possible parameters and odbc states. |
| QDA11 | Error | 20671 | -1000011L | "Transaction %2 attempted to access '%4' created by transaction %3. %1" | Table Level Versioning doesn't allow access to versions newer than your current transaction ID. Click here for a list of possible parameters and odbc states. |
| QDA12 | Error | 20672 | -1000012L | "Index '%2' cannot be closed because it has %3 users. %1" | This is an internal error. The index cannot be closed because it is in use. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA14 | Error | 20674 | -1000014L | "%2 MB is not sufficient for the load, update, or delete. %1" | The user can control the amount of heap memory a load/delete/update process (LOAD, INSERT VALUE, DELETE, SYNCHRONIZE, UPDATE) can use via the Load_Memory_MB option. If this memory limit isn't sufficient for the load/delete/update to run, then this exception is raised. To proceed, the user must either turnoff the limit (i.e., set Load_Memory_MB to zero) or increase the limit. Click here for a list of possible parameters and odbc states. |
| QDA18 | Error | 20678 | -1000018L | "The object cannot be opened for DROP or ALTER. It is already open. %1" | The object that you have requested to DROP or ALTER cannot be opened for META access. Either the current connection or another connection has a cursor open on the table you are trying to DROP or ALTER or on the table to which the field or index you are trying open for META belongs. In order to proceed, all cursors open on this object must be closed. Click here for a list of possible parameters and odbc states. |
| QDA22 | Error | 20682 | -1000022L | "Index '%2' has an invalid index type: %3. %1" | This is an internal error. The index is of a type that is unknown to ASIQ. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA23 | Error | 20683 | -1000023L | "The proposed join does not form a clearly connected list. (table '%2') %1" | Join Indexes can be entered in one of two ways. Using the order of the tables in the SQL statement or using primary<->foreign keys. When using the order method the order determines the relationships between the tables. The order is from a one to many or one to one. It is possible to ask for a join Index that can not be constructed. This error could be from one of the following: 1) The same table is specified twice. 2) The relationships of one to one/many are not consistent with the indexes defined. 3) A table specified has no relation to the tables previously encountered in the syntax. For example: A FULL OUTER JOIN B FULL OUTER JOIN C FULL OUTER JOIN D In this example C has no relation (fields in common) to A or B. The user intended C to Join with D. Some joins can not be defined using the ANSI syntax which depends on order to determine the one to one/many relationship. It is recommended to use the primary and foreign keys syntax to avoid any join definition problems. Click here for a list of possible parameters and odbc states. |
| QDA24 | Error | 20684 | -1000024L | "For table pair %2, table '%3' has a datatype mismatch for column %4. %1" | Corresponding columns' in the table pairs must be of the same datatype. (For example, INTEGER and INTEGER or CHAR and CHAR.) Matching datatypes such as CHAR and VARCHAR or INT and SMALLINT are not allowed. Click here for a list of possible parameters and odbc states. |
| QDA26 | Error | 20686 | -1000026L | "The join virtual table for table '%2' has duplicate columns in positions %3 and %4. %1" | The join virtual table for table has duplicate columns. Perhaps the join predicate is improperly specified. Click here for a list of possible parameters and odbc states. |