Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2000 | Warning | 00000 | 0L | No message | This code indicates that there was no error or warning. Click here for a list of possible parameters and odbc states. |
| 2001 | Warning | 02000 | 100L | "Row not found" | You positioned a cursor beyond the beginning or past the end of the query. There is no row at that position. Click here for a list of possible parameters and odbc states. |
| 2002 | Warning | 01004 | 101L | "Value truncated" | You may have fetched data into a host variable or SQLDA variable not large enough to receive the value. Click here for a list of possible parameters and odbc states. |
| 2003 | Warning | 01W02 | 102L | "Using temporary table" | A temporary table has been created in order to satisfy the query. This warning can only occur on an OPEN statement. Click here for a list of possible parameters and odbc states. |
| 2004 | Warning | 01W03 | 103L | "Invalid data conversion" | 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. Click here for a list of possible parameters and odbc states. |
| 2005 | Warning | 01W04 | 104L | "Row has been updated since last time read" | 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. Click here for a list of possible parameters and odbc states. |
| 2006 | Warning | 01W05 | 105L | "Procedure has completed" | 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. Click here for a list of possible parameters and odbc states. |
| 2007 | Warning | 01W06 | 106L | "Value for column '%1' in table '%2' has changed" | A replicated UPDATE has found a value in an updated column that does not match the value when the original UPDATE was made. Click here for a list of possible parameters and odbc states. |
| 2008 | Warning | 01W08 | 111L | "Statement cannot be executed" | You specified a SQL statement for the PREPARE ... WITH EXECUTE statement that cannot be executed. If you specified an output SQLDA, it may contain a DESCRIBE of the prepared statement. Click here for a list of possible parameters and odbc states. |
| 2009 | Warning | 01000 | 200L | "Warning: %1" | A warning has occurred. The message indicates the condition that caused the warning. Click here for a list of possible parameters and odbc states. |
| 2011 | Error | 08W07 | -80L | "Unable to start database server" | It was not possible to start the database server. There may not be enough memory to run the database server. It may be that the executable cannot be found. Click here for a list of possible parameters and odbc states. |
| 2012 | Error | 08W08 | -81L | "Invalid database server command line" | It was not possible to start the database server because the command line was invalid. Click here for a list of possible parameters and odbc states. |
| 2013 | Error | 08W30 | -74L | "The selected database is currently inactive" | The selected database is in an inactive state. The database may be in the process of being started or shut down. Click here for a list of possible parameters and odbc states. |
| 2014 | Error | 08W29 | -75L | "Request to start/stop database denied" | You do not have permission to start or stop a database. The required permission is determined on the server command line. Click here for a list of possible parameters and odbc states. |
| 2015 | Error | 08W28 | -76L | "Request denied -- no active databases" | The server has denied your request as there are currently no running databases. Click here for a list of possible parameters and odbc states. |
| 2016 | Error | 08W27 | -77L | "Database name not unique" | The database cannot be started as its name conflicts with a previously started database. Click here for a list of possible parameters and odbc states. |
| 2017 | Error | 08W25 | -79L | "Invalid local database option" | An invalid database option was found in the DBS (DatabaseSwitches) connection parameter. Click here for a list of possible parameters and odbc states. |
| 2018 | Error | 08W09 | -82L | "Unable to start specified database: %1" | The database server was unable to start the specified database. Check the server window messages area for more details. If the server was being autostarted, using the server -o option or manually starting the server may give more details. Click here for a list of possible parameters and odbc states. |
| 2019 | Error | 08W10 | -83L | "Specified database not found" | 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. Click here for a list of possible parameters and odbc states. |
| 2020 | Error | 08W11 | -84L | "Specified database is invalid" | The database file you specified is invalid. The database server is stopped. Click here for a list of possible parameters and odbc states. |