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 |
|---|---|---|---|---|---|
| -503L | Error | 2260 | WI006 | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| -504L | Error | 2261 | WI008 | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| -601L | Error | 2209 | WL001 | "'%1' is not a known file format for loading or unloading tables" | An unsupported file format was specified for LOAD TABLE or UNLOAD TABLE. Click here for a list of possible parameters and odbc states. |
| -602L | Error | 2210 | WL002 | "Cannot access file '%1' -- %2" | A file cannot be accessed. For example, a file referenced by LOAD TABLE does not exist or cannot be read. The message will contain the reason for the error. Click here for a list of possible parameters and odbc states. |
| -604L | Error | 2213 | 04W07 | "A dbspace has reached its maximum file size" | A dbspace has grown to its maximum number of disk pages, which is usually limited by the maximum operating system file size. This is a fatal error. Click here for a list of possible parameters and odbc states. |
| -605L | Error | 2214 | 04W08 | "The server attempted to access a page beyond the end of the maximum allowable dbspace file size" | The database attempted to access a page whose page number is beyond the maximum possible number of disk pages. This is a fatal internal error. Click here for a list of possible parameters and odbc states. |
| -606L | Error | 2215 | WW001 | "The pattern is too long" | The pattern for the LIKE operator is too long. All patterns of 126 characters or less are supported. Some patterns as long as 254 characters are supported, depending on their contents. Patterns longer than 254 characters are not supported. Click here for a list of possible parameters and odbc states. |
| -607L | Error | 2216 | WW002 | "Cannot stop the database server" | The server has determined that it cannot be shut down at this time. Normally, this error should not occur. Click here for a list of possible parameters and odbc states. |
| -608L | Error | 2217 | 22W03 | "Invalid TEXTPTR value used with WRITETEXT or READTEXT" | You supplied an invalid value as the TEXTPTR for a WRITETEXT or READTEXT statement. Click here for a list of possible parameters and odbc states. |
| -609L | Error | 2218 | 53W09 | "Invalid data type for column in WRITETEXT or READTEXT" | You referenced a column in a WRITETEXT or READTEXT statement that is not defined for storing text or image data. Click here for a list of possible parameters and odbc states. |
| -610L | Error | 2064 | 52W16 | "User message %1 already exists" | The message with this error number already exists in the database. Click here for a list of possible parameters and odbc states. |
| -611L | Error | 2076 | 0AW02 | "Transact-SQL feature not supported" | You attempted to use a Transact-SQL feature that is not supported in SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| -612L | Error | 2097 | 52W17 | "User message %1 not found" | The message with this error number does not exist in the database. Click here for a list of possible parameters and odbc states. |
| -613L | Error | 2098 | 52W18 | "User-defined type '%1' not found" | The user-defined type with this name does not exist in the database. Click here for a list of possible parameters and odbc states. |
| -614L | Error | 2099 | 55W05 | "Cannot drop a user that owns messages or data types" | You attempted to drop a user that is the creator of a message or user-defined data type. The message or user-defined data type must be dropped first. Click here for a list of possible parameters and odbc states. |
| -615L | Error | 2101 | 42W47 | "Parameter '%1' not found in procedure '%2'" | You supplied a procedure parameter name that does not match a parameter for this procedure. Check the spelling of the parameter name. Click here for a list of possible parameters and odbc states. |
| -616L | Error | 2219 | 52W20 | "Too many columns in table" | You executed a CREATE TABLE or ALTER TABLE statement that attempted to add a column to a table. The resulting number of columns in the table would exceed the limit for the current database page size. Click here for a list of possible parameters and odbc states. |
| -617L | Error | 2220 | WW003 | "Calling functions outside the database server is not supported" | You attempted to call a stored procedure that, in turn, calls a function in a dynamically loaded module. The operating system on which this stored procedure was called does not support such an action. Click here for a list of possible parameters and odbc states. |
| -618L | Error | 2221 | WW004 | "Mismatch between external function platform specifier and current operating system" | A call to an external entry point in a dynamically loaded module was qualified by an operating system that was not the operating system on which the server is currently executing. Click here for a list of possible parameters and odbc states. |
| -619L | Error | 2222 | WW005 | "Need a dynamic library name" | You must provide a library name specifier in the name of the external function to call. Click here for a list of possible parameters and odbc states. |