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 |
|---|---|---|---|---|---|
| 2194 | Error | 40001 | -306L | "Deadlock detected" | You attempted to read or write a row and it is locked by another user. Also, the other user is blocked directly or indirectly on your own transaction. This is a deadlock situation and your transaction has been chosen as the one to rollback. Click here for a list of possible parameters and odbc states. |
| 2195 | Error | 40W06 | -307L | "All threads are blocked" | You attempted to read or write a row and it is locked by another user. Also, all other threads (see the -gn server option) are blocked waiting for a lock to be released. This is a deadlock situation and your transaction has been chosen as the one to rollback. Click here for a list of possible parameters and odbc states. |
| 2196 | Error | 40W07 | -308L | "Connection was terminated" | Your database connection has been terminated and your transaction has been rolled back. The connection may have been terminated because a DBA executed a DROP CONNECTION statement, or because the database server was shut down, or because your network connection to the database server was interrupted. Click here for a list of possible parameters and odbc states. |
| 2208 | Error | WI004 | -311L | "Internal rollback log corrupted" | While processing a COMMIT or ROLLBACK, corruption was found in the internal rollback log. This is a fatal internal error. Click here for a list of possible parameters and odbc states. |
| 2209 | Error | WL001 | -601L | "'%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. |
| 2210 | Error | WL002 | -602L | "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. |
| 2212 | Error | WL004 | -643L | "UNLOAD TABLE cannot be used to unload a view" | UNLOAD TABLE was specified with the name of a view. UNLOAD TABLE may only be used to unload tables. Click here for a list of possible parameters and odbc states. |
| 2213 | Error | 04W07 | -604L | "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. |
| 2214 | Error | 04W08 | -605L | "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. |
| 2215 | Error | WW001 | -606L | "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. |
| 2216 | Error | WW002 | -607L | "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. |
| 2217 | Error | 22W03 | -608L | "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. |
| 2218 | Error | 53W09 | -609L | "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. |
| 2219 | Error | 52W20 | -616L | "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. |
| 2220 | Error | WW003 | -617L | "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. |
| 2221 | Error | WW004 | -618L | "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. |
| 2222 | Error | WW005 | -619L | "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. |
| 2223 | Error | WW006 | -620L | "Could not load dynamic library '%1'" | This error is usually caused by a failure to load a dynamic library named in an external function call. Click here for a list of possible parameters and odbc states. |
| 2224 | Error | WW007 | -621L | "Could not find '%1' in dynamic library '%2'" | The external function could not be found in the dynamic library. Click here for a list of possible parameters and odbc states. |
| 2225 | Error | WW008 | -622L | "Could not allocate resources to call external function" | The external function could not be called due to a shortage of operating system resources. If the operating system supports threads, the maximum thread count should be increased. Click here for a list of possible parameters and odbc states. |