Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 620 | "Could not load dynamic library '%1'" |
|---|---|
Constant | COULD_NOT_LOAD_LIBRARY |
SAP Sybase Error Number | 2223 |
SQL State | WW006 |
SQL Code | -620L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the dynamic library that could not be loaded. |
Probable Cause | This error is usually caused by a failure to load a dynamic library named in an external function call. |
| Error 621 | "Could not find '%1' in dynamic library '%2'" |
|---|---|
Constant | COULD_NOT_FIND_FUNCTION |
SAP Sybase Error Number | 2224 |
SQL State | WW007 |
SQL Code | -621L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the function that could not be found. |
Parameter 2 | Name of the dynamic library in which the function could not be found. |
Probable Cause | The external function could not be found in the dynamic library. |
| Error 622 | "Could not allocate resources to call external function" |
|---|---|
Constant | ERROR_CALLING_FUNCTION |
SAP Sybase Error Number | 2225 |
SQL State | WW008 |
SQL Code | -622L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
| Error 623 | "Data definition statements not allowed in procedures or triggers" |
|---|---|
Constant | DDL_NOT_ALLOWED_IN_PROCEDURES |
SAP Sybase Error Number | 2226 |
SQL State | 52W21 |
SQL Code | -623L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The procedure or trigger definition contains a data definition statement (such as CREATE, DROP, GRANT, REVOKE, or ALTER). These statements are not allowed within procedures or triggers. |
| Error 624 | "Expression has unsupported data type" |
|---|---|
Constant | DATATYPE_NOT_ALLOWED |
SAP Sybase Error Number | 2227 |
SQL State | WW009 |
SQL Code | -624L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Either an external function or Java method was declared with a parameter or result data type that is not supported, or a Java field reference with an unsupported result type was attempted. |
| Error 625 | "Too many parameters to this external procedure call" |
|---|---|
Constant | TOO_MANY_PARAMETERS |
SAP Sybase Error Number | 2228 |
SQL State | WW010 |
SQL Code | -625L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | There is a maximum of 256 parameters to an external function call in 32-bit Windows. |
| Error 626 | "A thread used internally could not be started" |
|---|---|
Constant | THREAD_START_FAILURE |
SAP Sybase Error Number | 2229 |
SQL State | WW011 |
SQL Code | -626L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | This is a Windows 95 specific error. An operating system thread could not be started that is required to execute external functions. |
| Error 627 | "Disallowed language extension detected in syntax near '%1' on line %2" |
|---|---|
Constant | INVALID_SYNTAX_EXTENSION |
SAP Sybase Error Number | 2230 |
SQL State | 0AW03 |
SQL Code | -627L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The word or symbol where the syntax has been detected. |
Parameter 2 | Line number. |
Probable Cause | The statement you are trying to execute contains syntax that is not allowed with the current setting of the option sql_flagger_error_level. Modify the offending statement or set the sql_flagger_error_level option to a different value. |
| Error 628 | "Division by zero" |
|---|---|
Constant | DIV_ZERO_ERROR |
SAP Sybase Error Number | 2231 |
SQL State | 22012 |
SQL Code | -628L |
ODBC 2 State | 22012 |
ODBC 3 State | 22012 |
Severity Code | |
Probable Cause | A division by zero operation was detected. |
| Error 629 | "Invalid escape character '%1'" |
|---|---|
Constant | INVALID_ESCAPE_CHAR |
SAP Sybase Error Number | 2232 |
SQL State | 22019 |
SQL Code | -629L |
ODBC 2 State | S1000 |
ODBC 3 State | 22019 |
Severity Code | |
Parameter 1 | The escape character that is invalid. |
Probable Cause | The escape character string length must be exactly one. |
| Error 630 | "Invalid escape sequence '%1'" |
|---|---|
Constant | INVALID_ESCAPE_SEQ |
SAP Sybase Error Number | 2233 |
SQL State | 22025 |
SQL Code | -630L |
ODBC 2 State | S1000 |
ODBC 3 State | 22025 |
Severity Code | |
Parameter 1 | The escaped character. |
Probable Cause | A LIKE pattern contains an invalid use of the escape character. The escape character may only precede the special characters '%', '_', '[', and the escape character itself. |
| Error 631 | "RAISERROR executed: %1" |
|---|---|
Constant | RAISERROR_STMT |
SAP Sybase Error Number | 2234 |
SQL State | WW012 |
SQL Code | -631L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | RAISERROR message string. |
Probable Cause | A RAISERROR statement has been executed. The string associated with the RAISERROR statement is included in the text of the error message. |
| Error 632 | "WITH CHECK OPTION violated for insert/update on base table '%1'" |
|---|---|
Constant | WITH_CHECK_OPTION_VIOLATION |
SAP Sybase Error Number | 2235 |
SQL State | 44000 |
SQL Code | -632L |
ODBC 2 State | S1000 |
ODBC 3 State | 44000 |
Severity Code | |
Parameter 1 | Name of the base table being updated. |
Probable Cause | You attempted an insert or update operation on the indicated base table through a view (possibly nested). However, one or more values in the modified row(s) triggered a WITH CHECK OPTION violation. This violation occurs when a modified value causes one or more rows to fall outside the range of the view by making the view's WHERE clause evaluate to FALSE or UNKNOWN for that row. |
| Error 633 | "Update operation attempted on a read-only cursor" |
|---|---|
Constant | READ_ONLY_CURSOR |
SAP Sybase Error Number | 2236 |
SQL State | 42W30 |
SQL Code | -633L |
ODBC 2 State | S1009 |
ODBC 3 State | HY092 |
Severity Code | |
Probable Cause | You attempted an update operation on a cursor that was explicitly declared as read-only. |
| Error 634 | "Unterminated C string" |
|---|---|
Constant | UNTERMINATED_C_STR |
SAP Sybase Error Number | 2237 |
SQL State | 22024 |
SQL Code | -634L |
ODBC 2 State | 22024 |
ODBC 3 State | 22024 |
Severity Code | |
Probable Cause | The last byte of a C string host variable must contain the null character. |
| Error 635 | "GRANT of column permission on view not allowed" |
|---|---|
Constant | NO_COLUMN_PERMS_FOR_VIEWS |
SAP Sybase Error Number | 2240 |
SQL State | 52W22 |
SQL Code | -635L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You cannot grant permissions on columns for views. |
| Error 636 | "Duplicate referencing column" |
|---|---|
Constant | DUPLICATE_REFERENCING_COLUMN |
SAP Sybase Error Number | 2242 |
SQL State | 42W40 |
SQL Code | -636L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You supplied a duplicate column name in the list of referencing columns. |
| Error 637 | "Duplicate insert column" |
|---|---|
Constant | DUPLICATE_INSERT_COLUMN |
SAP Sybase Error Number | 2243 |
SQL State | 42W41 |
SQL Code | -637L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You supplied a duplicate column name in the list of insert columns. |
| Error 638 | "Right truncation of string data" |
|---|---|
Constant | STRING_RIGHT_TRUNCATION |
SAP Sybase Error Number | 2244 |
SQL State | 22001 |
SQL Code | -638L |
ODBC 2 State | 22001 |
ODBC 3 State | 22001 |
Severity Code | |
Probable Cause | Non-space characters were truncated upon the assignment of string data. |
| Error 639 | "Parameter name missing in call to procedure '%1'" |
|---|---|
Constant | PARAMETER_NAME_MISSING |
SAP Sybase Error Number | 2245 |
SQL State | 42W42 |
SQL Code | -639L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The name of the procedure. |
Probable Cause | Positional parameters were specified after named parameters in a call to this procedure. |