Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
Error 503 | No message |
---|---|
Constant | PREEMPTED |
SAP Sybase Error Number | 2260 |
SQL State | WI006 |
SQL Code | -503L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | No additional information available. |
Error 504 | No message |
---|---|
Constant | RETRY |
SAP Sybase Error Number | 2261 |
SQL State | WI008 |
SQL Code | -504L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | No additional information available. |
Error 601 | "'%1' is not a known file format for loading or unloading tables" |
---|---|
Constant | UNSUPPORTED_LOAD_FORMAT |
SAP Sybase Error Number | 2209 |
SQL State | WL001 |
SQL Code | -601L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The specified format. |
Probable Cause | An unsupported file format was specified for LOAD TABLE or UNLOAD TABLE. |
Error 602 | "Cannot access file '%1' -- %2" |
---|---|
Constant | CANNOT_ACCESS_FILE |
SAP Sybase Error Number | 2210 |
SQL State | WL002 |
SQL Code | -602L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The file name. |
Parameter 2 | The cause of the error. |
Probable Cause | 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. |
Error 604 | "A dbspace has reached its maximum file size" |
---|---|
Constant | DBSPACE_FULL |
SAP Sybase Error Number | 2213 |
SQL State | 04W07 |
SQL Code | -604L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
Error 605 | "The server attempted to access a page beyond the end of the maximum allowable dbspace file size" |
---|---|
Constant | ACCESS_BEYOND_END_OF_MAX_DBSPACE |
SAP Sybase Error Number | 2214 |
SQL State | 04W08 |
SQL Code | -605L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
Error 606 | "The pattern is too long" |
---|---|
Constant | PATTERN_TOO_LONG |
SAP Sybase Error Number | 2215 |
SQL State | WW001 |
SQL Code | -606L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
Error 607 | "Cannot stop the database server" |
---|---|
Constant | CANNOT_STOP_SERVER |
SAP Sybase Error Number | 2216 |
SQL State | WW002 |
SQL Code | -607L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The server has determined that it cannot be shut down at this time. Normally, this error should not occur. |
Error 608 | "Invalid TEXTPTR value used with WRITETEXT or READTEXT" |
---|---|
Constant | INVALID_TEXTPTR_VALUE |
SAP Sybase Error Number | 2217 |
SQL State | 22W03 |
SQL Code | -608L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You supplied an invalid value as the TEXTPTR for a WRITETEXT or READTEXT statement. |
Error 609 | "Invalid data type for column in WRITETEXT or READTEXT" |
---|---|
Constant | INVALID_TEXT_IMAGE_DATATYPE |
SAP Sybase Error Number | 2218 |
SQL State | 53W09 |
SQL Code | -609L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You referenced a column in a WRITETEXT or READTEXT statement that is not defined for storing text or image data. |
Error 610 | "User message %1 already exists" |
---|---|
Constant | MESSAGE_ALREADY_EXISTS |
SAP Sybase Error Number | 2064 |
SQL State | 52W16 |
SQL Code | -610L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Error number of the user message that exists in the database. |
Probable Cause | The message with this error number already exists in the database. |
Error 611 | "Transact-SQL feature not supported" |
---|---|
Constant | TSQL_FEATURE_NOT_SUPPORTED |
SAP Sybase Error Number | 2076 |
SQL State | 0AW02 |
SQL Code | -611L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to use a Transact-SQL feature that is not supported in SQL Anywhere. |
Error 612 | "User message %1 not found" |
---|---|
Constant | MESSAGE_NOT_FOUND |
SAP Sybase Error Number | 2097 |
SQL State | 52W17 |
SQL Code | -612L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Message number. |
Probable Cause | The message with this error number does not exist in the database. |
Error 613 | "User-defined type '%1' not found" |
---|---|
Constant | USER_TYPE_NOT_FOUND |
SAP Sybase Error Number | 2098 |
SQL State | 52W18 |
SQL Code | -613L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the user-defined type. |
Probable Cause | The user-defined type with this name does not exist in the database. |
Error 614 | "Cannot drop a user that owns messages or data types" |
---|---|
Constant | USER_OWNS_MESSAGES_OR_DATATYPES |
SAP Sybase Error Number | 2099 |
SQL State | 55W05 |
SQL Code | -614L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
Error 615 | "Parameter '%1' not found in procedure '%2'" |
---|---|
Constant | INVALID_PARAMETER_NAME |
SAP Sybase Error Number | 2101 |
SQL State | 42W47 |
SQL Code | -615L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the parameter that was not found. |
Parameter 2 | Name of the procedure where the parameter was not found. |
Probable Cause | You supplied a procedure parameter name that does not match a parameter for this procedure. Check the spelling of the parameter name. |
Error 616 | "Too many columns in table" |
---|---|
Constant | TOO_MANY_COLUMNS_IN_TABLE |
SAP Sybase Error Number | 2219 |
SQL State | 52W20 |
SQL Code | -616L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
Error 617 | "Calling functions outside the database server is not supported" |
---|---|
Constant | EXTERNAL_CALLS_NOT_SUPPORTED |
SAP Sybase Error Number | 2220 |
SQL State | WW003 |
SQL Code | -617L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
Error 618 | "Mismatch between external function platform specifier and current operating system" |
---|---|
Constant | EXTERNAL_PLATFORM_FAILURE |
SAP Sybase Error Number | 2221 |
SQL State | WW004 |
SQL Code | -618L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
Error 619 | "Need a dynamic library name" |
---|---|
Constant | REQUIRE_DLL_NAME |
SAP Sybase Error Number | 2222 |
SQL State | WW005 |
SQL Code | -619L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You must provide a library name specifier in the name of the external function to call. |