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 |
|---|---|---|---|---|---|
| 2362 | Error | WI010 | -727L | "The optimizer was unable to construct a valid access plan" | The database server was unable to construct a valid access plan for the given request. This is a SQL Anywhere internal error. If it can be reproduced, it should be reported to iAnywhere. You may be able to work around this problem by modifying the query statement. Click here for a list of possible parameters and odbc states. |
| 2363 | Error | WW166 | -1597L | "The transaction may not be committed because the primary server lost quorum" | You attempted to commit a transaction on a primary server that just lost quorum with the partner and arbiter servers. The transaction may or may not have been committed. The partner servers will attempt to determine which server will become the new primary server. Click here for a list of possible parameters and odbc states. |
| 2364 | Error | WQ020 | -1575L | "Database upgrade not possible; the name or ID of new IQ_SHARED_TEMP dbspace is already in use." | An attempt to upgrade a database failed. Retry upgrade of the database when no existing dbspace is using the name or ID of the IQ_SHARED_TEMP dbspace. Click here for a list of possible parameters and odbc states. |
| 2365 | Error | WQ019 | -1568L | "Unable to generate a logical server ID." | Last generated logical server ID reached maximum limit. The database catalog needs to be rebuilt. Click here for a list of possible parameters and odbc states. |
| 2366 | Error | WO021 | -732L | "Creating remote tables with computed columns is not supported" | Computed columns are not supported in CREATE TABLE statements that specify a remote location. Click here for a list of possible parameters and odbc states. |
| 2367 | Error | WO022 | -736L | "The data type of column or variable '%1' is not supported" | The column is defined with a data type that is not supported for remote tables or the variable is defined with a datatype that is not supported for using and location clauses. Click here for a list of possible parameters and odbc states. |
| 2368 | Error | WQ018 | -1550L | "Overriding ROOT login policy options for logical servers is not allowed." | A user cannot override login policy options of ROOT login policy for logical servers. Click here for a list of possible parameters and odbc states. |
| 2369 | Error | WQ017 | -1549L | "Cannot set the '%1' option as Login Policy option '%2' is set to off." | If an option of the login policy is set to off then user cannot set the temporary option which is directly depending on it. For example, if the login policy option DQP_ENABLED is set to Off, then the temporary option DQP_ENABLED cannot be set to On. Click here for a list of possible parameters and odbc states. |
| 2370 | Error | WQ016 | -1548L | "Cannot drop Multiplex server '%1'. This is not the last secondary server. Remove the \"WITH DROP LOGICAL SERVER\" clause." | WITH DROP LOGICAL SERVER clause should be used ONLY when dropping the last secondary Server. Click here for a list of possible parameters and odbc states. |
| 2371 | Error | WQ015 | -1547L | "Cannot drop Multiplex server '%1' without dropping all the logical servers as it will convert the Multiplex to Simplex. Use the \"WITH DROP LOGICAL SERVER\" clause." | If dropping the secondary server will result in conversion from MPX to SPX then all the user created logical servers should be dropped. Click here for a list of possible parameters and odbc states. |
| 2372 | Error | 42W35 | -728L | "Update operation attempted on non-updatable remote query" | You attempted an update or delete operation on a remote table that is currently not supported. Examples of such operations include positioned updates or deletes and updates or deletes that involve a join between local and proxy tables. Updates or deletes that involve a join between proxy tables on different remote servers will also give this error. Click here for a list of possible parameters and odbc states. |
| 2373 | Error | 23507 | -729L | "The specified foreign key (%1) cannot be enforced" | You attempted to create a foreign key that cannot be enforced. To be enforceable, the primary and foreign table for the specified key must exist on the same server. You can use the UNENFORCED keyword to create a foreign key specification that is not to be enforced. Click here for a list of possible parameters and odbc states. |
| 2374 | Error | WP010 | -730L | "Invalid JAR file" | A file passed to the INSTALL JAVA statement was not a valid JAR file. Click here for a list of possible parameters and odbc states. |
| 2375 | Warning | 01W14 | 116L | "Language '%1' is not supported, '%2' will be used" | The language that the application requested is not supported by the server to which the application is connecting. Instead, the server will send message strings in the language stated. Click here for a list of possible parameters and odbc states. |
| 2376 | Warning | 01W15 | 117L | "Unsupported character set '%1' and unsupported language '%2'; language used is '%3' instead" | The character set that the application requested is not supported by the server to which the application is connecting. The language that the application requested is not supported either. Language strings will be sent in the language specified. Click here for a list of possible parameters and odbc states. |
| 2377 | Error | 55W06 | -731L | "Cannot drop a user that owns objects involved in replication" | You attempted to drop a user that is the creator of a database object involved in replication. For example, the user may own a table that is part of a publication. Click here for a list of possible parameters and odbc states. |
| 2378 | Error | 23504 | -733L | "Number of columns allowing NULLs exceeds limit" | You attempted to create or modify a table definition such that the number of columns that allow NULLS is now more than the limit on such columns. The limit is a function of database page size and is approximately 8*(page-size - 30). Click here for a list of possible parameters and odbc states. |
| 2379 | Error | 09W08 | -734L | "Cannot update or delete an all-NULL row from table '%1'" | You attempted to modify or delete a row in the specified table, which is part of the NULL-supplying side of an outer join. However, the cursor is currently positioned on a derived row that contains an all-NULL row for this table, which is the result of the failure of one or more ON conditions to evaluate to TRUE. Verify that the UPDATE or DELETE statement is correct. Click here for a list of possible parameters and odbc states. |
| 2380 | Error | 08W49 | -95L | "Parse error: %1" | An error occurred while parsing a connection string. Click here for a list of possible parameters and odbc states. |
| 2381 | Warning | 01W16 | 118L | "Illegal user selectivity estimate specified" | You specified a user selectivity estimate that is either not a literal constant or is outside the range 0.0 to 100.0 (estimates are specified as percentages). The estimate has been ignored. Click here for a list of possible parameters and odbc states. |