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 |
|---|---|---|---|---|---|
| 08WA8 | Error | 3224 | -1582L | "Server name can only be specified when connecting to a cloud database server with NODETYPE=DIRECT" | When connecting to a cloud database server, specifying a server name on the connection string is only allowed for NODETYPE=DIRECT. When using other NODETYPE values to connect to a cloud database server, specifying the server name is not allowed. Typically, for connections to a cloud database server the HOST connection parameter or HOST protocol option is used to specify the address of one or more cloud database servers. Click here for a list of possible parameters and odbc states. |
| 08WA9 | Error | 3226 | -1584L | "Unable to load the dbrsakp shared object" | The server was unable to load the dbrsakp DLL on Windows platforms or the libdbrsakp shared object on Unix platforms. Click here for a list of possible parameters and odbc states. |
| 08WB1 | Error | 3227 | -1585L | "Invalid tool name or admin user for generating security token" | The tool name or admin user supplied is invalid for generating a security token. Click here for a list of possible parameters and odbc states. |
| 08WB2 | Error | 3235 | -1593L | "Unable to copy file %1 to destination %2" | The client database file could not be copied to the requested cloud destination. Click here for a list of possible parameters and odbc states. |
| 08WB4 | Error | 3250 | -1608L | "Unable to delete file %1" | The request to delete a file failed Click here for a list of possible parameters and odbc states. |
| 08WB5 | Error | 3251 | -1609L | "File %1 already exists" | The request to create a file or directory failed because the file or directory already exists Click here for a list of possible parameters and odbc states. |
| 08WB6 | Error | 3252 | -1610L | "Unable to create directory %1" | The request to create a directory failed Click here for a list of possible parameters and odbc states. |
| 08WB7 | Error | 3253 | -1611L | "Unable to copy file %1" | The request to copy a file failed Click here for a list of possible parameters and odbc states. |
| 09W02 | Error | 2118 | -187L | "Illegal cursor operation attempt" | You attempted an illegal cursor operation. For example, you may be attempting to OPEN a cursor for a statement that is neither a SELECT nor a BATCH. Click here for a list of possible parameters and odbc states. |
| 09W03 | Error | 2610 | -946L | "Result set not permitted in '%1'" | You attempted to execute a SELECT statement in a context where a result set is not permitted. Click here for a list of possible parameters and odbc states. |
| 09W04 | Error | 2130 | -199L | "INSERT/DELETE on cursor can modify only one table" | You attempted to insert into a cursor and have specified values for more than one table, or you attempted to delete from a cursor that involves a join. Insert into one table at a time. For DELETE, use the FROM clause to specify the table you want to delete from. Click here for a list of possible parameters and odbc states. |
| 09W05 | Error | 2164 | -295L | "Cannot uniquely identify rows in cursor" | You opened a UNIQUE cursor on a SELECT statement for which a set of columns uniquely identifying each row cannot be generated. One of the tables may not be defined with a primary key or uniqueness constraint, or the SELECT statement may involve a UNION, INTERSECT, EXCEPT, or GROUP BY. Click here for a list of possible parameters and odbc states. |
| 09W06 | Error | 2294 | -668L | "Cursor is restricted to FETCH NEXT operations" | An illegal FETCH operation has been detected for a NO SCROLL cursor. For a forward-only cursor the only permitted FETCH operations are FETCH RELATIVE 0 and FETCH NEXT (FETCH RELATIVE 1). Click here for a list of possible parameters and odbc states. |
| 09W07 | Error | 2300 | -674L | "Statement's size limit is invalid" | FIRST or TOP n are used in a SELECT statement to limit the size of a result. The size limit must be a constant integer greater than 0 and less than 32767. Click here for a list of possible parameters and odbc states. |
| 09W08 | Error | 2379 | -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. |
| 0A000 | Error | 2075 | -134L | "Feature '%1' not implemented" | You attempted to carry out an operation or use a feature that is not implemented in this version of SQL Anywhere. In UltraLite, this error often occurs because you attempted to perform an unsupported operation on a LONG VARCHAR or LONG BINARY column. For example, the SUBSTRING function cannot be used with a LONG VARCHAR column. As well, an index cannot be created on a LONG column. Click here for a list of possible parameters and odbc states. |
| 0A001 | Error | 2762 | -1092L | "The method you attempted to invoke was not enabled for your application" | You attempted to call a method or use a feature that has not been enabled. In UltraLite, features are enabled using ULEnable functions or by using ULInitDatabaseManager instead of ULInitDatabaseManagerNoSQL. Click here for a list of possible parameters and odbc states. |
| 0A002 | Error | 2944 | -1260L | "This server is not licensed to support the '%1' feature" | You attempted to carry out an operation or use a feature that is not licensed in this edition of SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| 0A003 | Error | 2945 | -1261L | "This server is not licensed to support '%1' connections" | You attempted to use a connection protocol or API that is not licensed in this edition of SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| 0A004 | Error | 2946 | -1262L | "This edition of SQL Anywhere is not available on this platform" | This edition of SQL Anywhere is not available on this platform. You must use a different license key to use SQL Anywhere on this platform. Click here for a list of possible parameters and odbc states. |