Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 987 | "Invalid procedure subtype '%1' for type '%2'" |
|---|---|
Constant | INVALID_PROCEDURE_SUBTYPE |
SAP Sybase Error Number | 2654 |
SQL State | WW056 |
SQL Code | -987L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The procedure subtype. |
Parameter 2 | The procedure type. |
Probable Cause | A procedure or function was specified with an invalid subtype for the given procedure type. |
| Error 988 | "Invalid response from the HTTP server" |
|---|---|
Constant | INVALID_HTTP_RESPONSE |
SAP Sybase Error Number | 2655 |
SQL State | WW057 |
SQL Code | -988L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The response from the remote HTTP server was invalid. It may have been empty, malformed, missing header information, and so on. |
| Error 989 | "NAMESPACE attribute is not valid with procedure type '%1'" |
|---|---|
Constant | INVALID_NAMESPACE_ATTRIBUTE |
SAP Sybase Error Number | 2656 |
SQL State | WW058 |
SQL Code | -989L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The NAMESPACE attribute on the procedure. |
Probable Cause | The NAMESPACE attribute is only applicable to procedures of type SOAP. |
| Error 990 | "The secure connection to the remote host failed: %1" |
|---|---|
Constant | SECURE_CONNECTION_FAILED |
SAP Sybase Error Number | 2657 |
SQL State | WW059 |
SQL Code | -990L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | A message describing the error that occurred. |
Probable Cause | The server was unable to initiate a secure connection with the remote host. |
| Error 991 | "Clause '%1' has invalid attribute '%2'" |
|---|---|
Constant | INVALID_PROCEDURE_ATTRIBUTE |
SAP Sybase Error Number | 2658 |
SQL State | WW060 |
SQL Code | -991L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The attribute on the procedure. |
Parameter 2 | The attribute value or cause of failure. |
Probable Cause | The attribute value specified on the procedure is not valid. |
| Error 992 | "The specified listener could not be registered" |
|---|---|
Constant | CANNOT_REGISTER_LISTENER |
SAP Sybase Error Number | 2659 |
SQL State | 54W04 |
SQL Code | -992L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The specified listener could not be registered because the maximum number of listeners has been reached, the class name is already in use, or system resources are not available. |
| Error 993 | "LOAD TABLE not allowed on temporary table with ON COMMIT DELETE ROWS" |
|---|---|
Constant | INVALID_TEMP_TABLE_COMMIT_ACTION |
SAP Sybase Error Number | 2660 |
SQL State | WL007 |
SQL Code | -993L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The LOAD TABLE statement automatically commits at completion. If a temporary table being loaded was declared with ON COMMIT DELETE ROWS, the rows are discarded at completion. |
| Error 994 | "Too many arguments for function or procedure '%1'" |
|---|---|
Constant | TOO_MANY_ARGUMENTS |
SAP Sybase Error Number | 2661 |
SQL State | 42WAC |
SQL Code | -994L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The name of the function or procedure. |
Probable Cause | You supplied an argument list that the database server cannot handle. This can happen if the argument list of the function or stored procedure is too long. Rebuilding the database with a larger page size could prevent this error. |
| Error 995 | "Warning detected when optimizing SELECT INTO is treated as an error" |
|---|---|
Constant | SELECT_INTO_WARNING_TREATED_AS_ERROR |
SAP Sybase Error Number | 2662 |
SQL State | WP016 |
SQL Code | -995L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The SELECT...INTO #TEMPTABLE statement cannot proceed if a warning is detected while optimizing the query. To fix the problem, test the query by removing the INTO clause, and resolve the reported warning. |
| Error 996 | "Specified local connection ID not found" |
|---|---|
Constant | LOCAL_CONNECTION_NOT_FOUND |
SAP Sybase Error Number | 2663 |
SQL State | WO024 |
SQL Code | -996L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | There is no connection with the specified connection ID. |
| Error 997 | "Local connection ID does not refer to the current database" |
|---|---|
Constant | LOCAL_CONNECTION_NOT_TO_CURRENT_DB |
SAP Sybase Error Number | 2664 |
SQL State | WO025 |
SQL Code | -997L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The specified connection ID is for a connection to a database other than the current database. |
| Error 998 | "Cannot close a remote JDBC connection that is not the current connection" |
|---|---|
Constant | CANNOT_CLOSE_JDBC_CONNECTION |
SAP Sybase Error Number | 2665 |
SQL State | WO026 |
SQL Code | -998L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | When attempting to close a remote JDBC connection, the specified connection must be the local connection. |
| Error 999 | "Invalid request log format on line %1" |
|---|---|
Constant | INVALID_REQUEST_LOG_FORMAT |
SAP Sybase Error Number | 2667 |
SQL State | WW020 |
SQL Code | -999L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The line number in the log file. |
Probable Cause | The request log file format is invalid. The request log may have been created with an older version of the software. |
| Error 1000 | "Temporary space limit exceeded" |
|---|---|
Constant | TEMP_SPACE_LIMIT |
SAP Sybase Error Number | 2668 |
SQL State | 54W05 |
SQL Code | -1000L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The connection has exceeded its temporary-space usage limit. This limit is based in part on the amount of free-space remaining on the drive containing the temporary file. Try deleting unused files from the drive, or placing the temporary file on a drive with more space available. See the -dt server option to specify a directory for temporary files. |
| Error 1001 | "Parameter '%1' in procedure or function '%2' does not have a default value" |
|---|---|
Constant | NO_DEFAULT_FOR_PARM |
SAP Sybase Error Number | 2669 |
SQL State | 08W71 |
SQL Code | -1001L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the parameter. |
Parameter 2 | The name of the procedure or function. |
Probable Cause | An attempt was made to use DEFAULT as a procedure or function argument, but the corresponding parameter does not have a default value. |
| Error 1002 | "The option '%1' is not recognized" |
|---|---|
Constant | UNRECOGNIZED_OPTION |
SAP Sybase Error Number | 2670 |
SQL State | WW062 |
SQL Code | -1002L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the option. |
Probable Cause | The specified option was not recognized. The option may have been spelled incorrectly. |
| Error 1003 | "Too many distinct group mappings for integrated user" |
|---|---|
Constant | INTEGRATED_LOGON_TOO_MANY_MAPPINGS |
SAP Sybase Error Number | 2671 |
SQL State | 28W10 |
SQL Code | -1003L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | The integrated user does not have an explicit mapping in the database but does have group mappings. There are too many distinct group mappings. You must either reduce the number of distinct group mappings or add an explicit mapping for the user. |
| Error 1004 | "Unable to start specified database: '%1' is not a database" |
|---|---|
Constant | FILE_NOT_DB |
SAP Sybase Error Number | 2672 |
SQL State | 08W85 |
SQL Code | -1004L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The name of the database file. |
Probable Cause | The specified file is not a valid database file. |
| Error 1005 | "Unable to start specified database: '%1' was created by a different version of the software" |
|---|---|
Constant | FILE_WRONG_VERSION |
SAP Sybase Error Number | 2673 |
SQL State | 08W86 |
SQL Code | -1005L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The name of the database file. |
Probable Cause | The specified database file was created by a different version of the software, and it cannot be read by this version. |
| Error 1006 | "Unable to start specified database: '%1' is not a valid database file" |
|---|---|
Constant | FILE_BAD_DB |
SAP Sybase Error Number | 2674 |
SQL State | 08W87 |
SQL Code | -1006L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The name of the database file. |
Probable Cause | The specified file is not a valid database. |