Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 92 | "'%1' is not a valid class file" |
|---|---|
Constant | BAD_CLASS_FILE |
SAP Sybase Error Number | 2269 |
SQL State | WP002 |
SQL Code | -92L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the invalid file. |
Probable Cause | A file passed to the INSTALL JAVA statement was not a valid Java class file. |
| Error 93 | "Class '%1' has no public field '%2'" |
|---|---|
Constant | FIELD_NOT_FOUND |
SAP Sybase Error Number | 2273 |
SQL State | WW013 |
SQL Code | -93L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the class in which the named field could not be found. |
Parameter 2 | The name of the field that could not be found. |
Probable Cause | An expression referenced a field that either does not exist or is not public. |
| Error 94 | "Invalid type for field reference" |
|---|---|
Constant | INVALID_FIELD_REFERENCE |
SAP Sybase Error Number | 2274 |
SQL State | WW014 |
SQL Code | -94L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An expression attempted to reference a field or a method of a non-Java value. Field references via . and >> are only valid when applied to Java objects. |
| Error 95 | "Parse error: %1" |
|---|---|
Constant | INVALID_PARSE_PARAMETER |
SAP Sybase Error Number | 2380 |
SQL State | 08W49 |
SQL Code | -95L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Parameter 1 | Description of the parsing error. |
Probable Cause | An error occurred while parsing a connection string. |
| Error 96 | "Database server already running" |
|---|---|
Constant | ENGINE_ALREADY_RUNNING |
SAP Sybase Error Number | 2028 |
SQL State | 08W23 |
SQL Code | -96L |
ODBC 2 State | S1000 |
ODBC 3 State | HY000 |
Severity Code | |
Probable Cause | The database server was not able to start because a server with the same name was already running. |
| Error 97 | "Database page size too big: %1" |
|---|---|
Constant | PAGE_SIZE_TOO_BIG |
SAP Sybase Error Number | 2031 |
SQL State | 08W22 |
SQL Code | -97L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Parameter 1 | Database name. |
Probable Cause | You attempted to start a database with a page size that exceeds the maximum page size of the running server. Either restart the server and include this database name on the command line, or restart the server with the required page size. |
| Error 98 | "Authentication violation" |
|---|---|
Constant | AUTHENTICATION_VIOLATION |
SAP Sybase Error Number | 2034 |
SQL State | 08W21 |
SQL Code | -98L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | You attempted to connect to a server that has been authenticated for exclusive use with a specific application. |
| Error 99 | "Connections to database have been disabled" |
|---|---|
Constant | CONNECTIONS_DISABLED |
SAP Sybase Error Number | 2035 |
SQL State | 08W04 |
SQL Code | -99L |
ODBC 2 State | 08005 |
ODBC 3 State | 08005 |
Severity Code | |
Probable Cause | Connections to the network database server have been disabled. You will receive this error until connections have been enabled. |
| Warning 100 | "Row not found" |
|---|---|
Constant | NOTFOUND |
SAP Sybase Error Number | 2001 |
SQL State | 02000 |
SQL Code | 100L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | You positioned a cursor beyond the beginning or past the end of the query. There is no row at that position. |
| Error 100 | "Database server not found" |
|---|---|
Constant | ENGINE_NOT_RUNNING |
SAP Sybase Error Number | 2036 |
SQL State | 08W01 |
SQL Code | -100L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The database server is not running, or is in the process of starting up or shutting down, or the interface library is unable to find it. |
| Warning 101 | "Value truncated" |
|---|---|
Constant | TRUNCATED |
SAP Sybase Error Number | 2002 |
SQL State | 01004 |
SQL Code | 101L |
ODBC 2 State | 01004 |
ODBC 3 State | 01004 |
Severity Code | |
Probable Cause | You may have fetched data into a host variable or SQLDA variable not large enough to receive the value. |
| Error 101 | "Not connected to a database" |
|---|---|
Constant | NOT_CONNECTED |
SAP Sybase Error Number | 2037 |
SQL State | 08003 |
SQL Code | -101L |
ODBC 2 State | 08003 |
ODBC 3 State | 08003 |
Severity Code | |
Probable Cause | You are not connected to a database, or you executed the DISCONNECT statement and have not connected to a database again. |
| Warning 102 | "Using temporary table" |
|---|---|
Constant | TEMPORARY_TABLE |
SAP Sybase Error Number | 2003 |
SQL State | 01W02 |
SQL Code | 102L |
ODBC 2 State | 01000 |
ODBC 3 State | 01000 |
Severity Code | |
Probable Cause | A temporary table has been created to satisfy the query. This warning can only occur on an OPEN statement. |
| Error 102 | "Database server connection limit exceeded" |
|---|---|
Constant | TOO_MANY_CONNECTIONS |
SAP Sybase Error Number | 2038 |
SQL State | 08W03 |
SQL Code | -102L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Probable Cause | You exceeded the number of computers allowed to connect to the server. If you are running the network database server, the limit is specified in your license agreement. The server may be running low on cache, and as a result it cannot accept any more database connections. The personal database server is restricted to 10 connections. |
| Warning 103 | "Invalid data conversion" |
|---|---|
Constant | CANNOT_CONVERT |
SAP Sybase Error Number | 2004 |
SQL State | 01W03 |
SQL Code | 103L |
ODBC 2 State | 01S01 |
ODBC 3 State | 01S01 |
Severity Code | |
Probable Cause | The database could not convert a value to the required type. The value being converted was either supplied to the database on an insert, update, or as a host bind variable, or was a value retrieved from the database into a host variable or SQLDA. |
| Error 103 | "Invalid user ID or password" |
|---|---|
Constant | INVALID_LOGON |
SAP Sybase Error Number | 2039 |
SQL State | 28000 |
SQL Code | -103L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | You supplied an invalid user ID or an incorrect password. |
| Warning 104 | "Row has been updated since last time read" |
|---|---|
Constant | ROW_UPDATED_WARNING |
SAP Sybase Error Number | 2005 |
SQL State | 01W04 |
SQL Code | 104L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | You fetched a row from a SCROLL cursor. The row was previously fetched from the same cursor, and one or more columns in the row has been updated since the previous fetch. The column(s) updated may or may not be fetched by the cursor; this warning just indicates that the row from the table has been updated. If the cursor involves more than one table, a row from one or more of the tables has been updated. |
| Error 104 | "Invalid user ID or password on preprocessed module" |
|---|---|
Constant | INVALID_MODULE_LOGON |
SAP Sybase Error Number | 2041 |
SQL State | 28W01 |
SQL Code | -104L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | You specified an invalid user ID or password when a module was preprocessed. |
| Warning 105 | "Procedure has completed" |
|---|---|
Constant | PROCEDURE_COMPLETE |
SAP Sybase Error Number | 2006 |
SQL State | 01W05 |
SQL Code | 105L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | There are no more result sets available for this procedure. An OPEN or a RESUME statement may have caused the procedure to execute to completion. |
| Error 105 | "Database cannot be started -- %1" |
|---|---|
Constant | UNABLE_TO_CONNECT |
SAP Sybase Error Number | 2042 |
SQL State | 08001 |
SQL Code | -105L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | Reason that database cannot be started. |
Probable Cause | The specified database cannot be started. Either it does not exist, it is not a database, it is corrupt, or it is an older, unsupported format. |