Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| -1297L | Error | 2986 | WW125 | "No of servers in multiplex setup has reached to the maximum limit." | No of servers in multiplex setup has reached to the maximum limit. User cannot add any more secondary servers. Click here for a list of possible parameters and odbc states. |
| -1298L | Error | 2987 | WW126 | "Cannot alter multiplex failover node and other multiplex server properties in the same statement." | Users are not allowed to alter the multiplex failover node status and other multiplex server properties in the same statement. Click here for a list of possible parameters and odbc states. |
| -1299L | Error | 2988 | WW127 | "Drop multiplex server is allowed only in a multiplex setup." | Drop multiplex server is allowed only in a multiplex setup. Click here for a list of possible parameters and odbc states. |
| -1300L | Error | 2989 | WW128 | "Cannot add first multiplex server with excluded status." | Users are not allowed to add the first multiplex server with status excluded. Click here for a list of possible parameters and odbc states. |
| -1301L | Error | 2990 | WW129 | "Cannot create multiplex server with role coordinator." | Users are not allowed to create a multiplex server with role as coordinator. Click here for a list of possible parameters and odbc states. |
| -1302L | Error | 2982 | WW121 | "Host Port specification (%1) is invalid." | Host port specification is invalid. Click here for a list of possible parameters and odbc states. |
| -1306L | Error | 2994 | WW238 | "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. |
| -1000000L | Error | 20660 | QDA00 | "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. |
| -1000002L | Error | 20662 | QDA02 | "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. |
| -1000003L | Error | 20663 | QDA03 | "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. |
| -1000004L | Error | 20664 | QDA04 | "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. |
| -1000005L | Error | 20665 | QDA05 | "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. |
| -1000006L | Error | 20666 | QDA06 | "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. |
| -1000007L | Error | 20667 | QDA07 | "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. |
| -1000008L | Error | 20668 | QDA08 | "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. |
| -1000009L | Error | 20669 | QDA09 | "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. |
| -1000010L | Error | 20670 | QDA10 | "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. |
| -1000011L | Error | 20671 | QDA11 | "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. |
| -1000012L | Error | 20672 | QDA12 | "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. |
| -1000014L | Error | 20674 | QDA14 | "%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. |