Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Warning 0 | No message |
|---|---|
Constant | NOERROR |
SAP Sybase Error Number | 2000 |
SQL State | 00000 |
SQL Code | 0L |
ODBC 2 State | 00000 |
ODBC 3 State | 00000 |
Severity Code | |
Probable Cause | This code indicates that there was no error or warning. |
| Error 72 | "No database file specified" |
|---|---|
Constant | NO_DATABASE_FILE |
SAP Sybase Error Number | 2021 |
SQL State | 08W39 |
SQL Code | -72L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The database server was started but there was no specified database file. The server is stopped. |
| Error 74 | "The selected database is currently inactive" |
|---|---|
Constant | DATABASE_NOT_ACTIVE |
SAP Sybase Error Number | 2013 |
SQL State | 08W30 |
SQL Code | -74L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The selected database is in an inactive state. The database may be in the process of being started or shut down. |
| Error 75 | "Request to start/stop database denied" |
|---|---|
Constant | START_STOP_DATABASE_DENIED |
SAP Sybase Error Number | 2014 |
SQL State | 08W29 |
SQL Code | -75L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You do not have permission to start or stop a database. The required permission is determined on the server command line. |
| Error 76 | "Request denied -- no active databases" |
|---|---|
Constant | REQUEST_DENIED_NO_DATABASES |
SAP Sybase Error Number | 2015 |
SQL State | 08W28 |
SQL Code | -76L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Probable Cause | The server has denied your request as there are currently no running databases. |
| Error 77 | "Database name not unique" |
|---|---|
Constant | ALIAS_CLASH |
SAP Sybase Error Number | 2016 |
SQL State | 08W27 |
SQL Code | -77L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The database cannot be started as its name conflicts with a previously started database. |
| Error 78 | "Dynamic memory exhausted" |
|---|---|
Constant | DYNAMIC_MEMORY_EXHAUSTED |
SAP Sybase Error Number | 2024 |
SQL State | 08W26 |
SQL Code | -78L |
ODBC 2 State | S1001 |
ODBC 3 State | HY001 |
Severity Code | |
Probable Cause | A failure occurred when the database server was trying to allocate dynamic memory. |
| Error 79 | "Invalid local database option" |
|---|---|
Constant | INVALID_LOCAL_OPTION |
SAP Sybase Error Number | 2017 |
SQL State | 08W25 |
SQL Code | -79L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | An invalid database option was found in the DBS (DatabaseSwitches) connection parameter. |
| Error 80 | "Unable to start database server" |
|---|---|
Constant | UNABLE_TO_START_ENGINE |
SAP Sybase Error Number | 2011 |
SQL State | 08W07 |
SQL Code | -80L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | It was not possible to start the database server. There may not be enough memory to run the database server. It may also be that the executable cannot be found. |
| Error 81 | "Invalid database server command line" |
|---|---|
Constant | INVALID_COMMAND_LINE |
SAP Sybase Error Number | 2012 |
SQL State | 08W08 |
SQL Code | -81L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | It was not possible to start the database server because the command line was invalid. |
| Error 82 | "Unable to start specified database: %1" |
|---|---|
Constant | UNABLE_TO_START_DATABASE |
SAP Sybase Error Number | 2018 |
SQL State | 08W09 |
SQL Code | -82L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | Reason the database could not be started, if known. |
Probable Cause | The database server was unable to start the specified database. Check the database server messages window for more details. If the server was being started automatically, you can use the database server -o option to view messages from the database server or start the server manually to try to obtain more information about why the database cannot be started. |
| Error 83 | "Specified database not found" |
|---|---|
Constant | DATABASE_NOT_FOUND |
SAP Sybase Error Number | 2019 |
SQL State | 08W10 |
SQL Code | -83L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The database server was unable to find the specified database. The database server may be attempting to start a database file that cannot be opened or that cannot be found on the network. You may be attempting to connect to a database name that is not running. |
| Error 84 | "Specified database is invalid" |
|---|---|
Constant | INVALID_DATABASE |
SAP Sybase Error Number | 2020 |
SQL State | 08W11 |
SQL Code | -84L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The database file you specified is invalid. The database server is stopped. |
| Error 85 | "Communication error" |
|---|---|
Constant | COMMUNICATIONS_ERROR |
SAP Sybase Error Number | 2022 |
SQL State | 08W12 |
SQL Code | -85L |
ODBC 2 State | 08S01 |
ODBC 3 State | 08S01 |
Severity Code | |
Probable Cause | There is a communication problem between the application and the server. |
| Error 86 | "Not enough memory to start" |
|---|---|
Constant | NO_MEMORY |
SAP Sybase Error Number | 2025 |
SQL State | 08W13 |
SQL Code | -86L |
ODBC 2 State | S1001 |
ODBC 3 State | HY001 |
Severity Code | |
Probable Cause | The database server started, but stopped because there was not enough memory. |
| Error 87 | "Database name required to start server" |
|---|---|
Constant | DATABASE_NAME_REQUIRED |
SAP Sybase Error Number | 2026 |
SQL State | 08W14 |
SQL Code | -87L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | You did not supply a database name. A database name is required to start a database server. |
| Error 88 | "Client/server communications protocol version mismatch" |
|---|---|
Constant | PROTOCOL_MISMATCH |
SAP Sybase Error Number | 2027 |
SQL State | 08W15 |
SQL Code | -88L |
ODBC 2 State | 08S01 |
ODBC 3 State | 08S01 |
Severity Code | |
Probable Cause | The connection failed because the protocol versions of the client and the server do not match. Ensure the client and server software are the same version. |
| Error 89 | "Database server not running in multi-user mode" |
|---|---|
Constant | ENGINE_NOT_MULTIUSER |
SAP Sybase Error Number | 2029 |
SQL State | 08W16 |
SQL Code | -89L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The database server was started for bulk loading (the -b option) and cannot be used as a network server. Stop the database server, and start again without -b. |
| Error 90 | "Argument %1 of procedure '%2' cannot be NULL" |
|---|---|
Constant | ARGUMENT_CANNOT_BE_NULL |
SAP Sybase Error Number | 2267 |
SQL State | WP000 |
SQL Code | -90L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The argument number that cannot be NULL. |
Parameter 2 | The name of the procedure that cannot receive the NULL parameter. |
Probable Cause | You passed a NULL value to a procedure expecting a scalar argument. For example, a Java procedure that has an 'int' argument cannot receive a NULL value. |
| Error 91 | "Procedure '%1' terminated with unhandled exception '%2'" |
|---|---|
Constant | UNHANDLED_EXTENV_EXCEPTION |
SAP Sybase Error Number | 2268 |
SQL State | WP001 |
SQL Code | -91L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the procedure that returned the unhandled exception. |
Parameter 2 | The fully qualified Java class name of the unhandled exception. |
Probable Cause | A Java procedure terminated with an active exception, and this exception is reflected in SQL as an error status. |