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 |
|---|---|---|---|---|---|
| 2173 | Error | 42W23 | -215L | "Procedure in use by '%1'" | You attempted to DROP a procedure that is being used by other active users of the database. Click here for a list of possible parameters and odbc states. |
| 2174 | Error | 3B001 | -220L | "Savepoint '%1' not found" | You attempted to rollback to a savepoint that does not exist. Click here for a list of possible parameters and odbc states. |
| 2175 | Error | 3B002 | -221L | "ROLLBACK TO SAVEPOINT not allowed" | You attempted a ROLLBACK TO SAVEPOINT within an atomic operation to a savepoint established before the atomic operation. Click here for a list of possible parameters and odbc states. |
| 2176 | Error | 3BW02 | -222L | "Result set not allowed from within an atomic compound statement" | You used a SELECT statement with no INTO clause or a RESULT CURSOR statement within an atomic compound statement. Click here for a list of possible parameters and odbc states. |
| 2177 | Error | 3BW01 | -213L | "Savepoints require a rollback log" | You cannot use savepoints when the database server is running in bulk mode without a rollback log. Click here for a list of possible parameters and odbc states. |
| 2178 | Error | 08W18 | -230L | "sqlpp/dblib version mismatch" | Your executable has Embedded SQL source files that were preprocessed with a version of sqlpp that does not match the database interface library. Click here for a list of possible parameters and odbc states. |
| 2179 | Error | 08W19 | -231L | "Client/database server version mismatch" | Your executable uses a database interface library that does not match the version number of the database server. Click here for a list of possible parameters and odbc states. |
| 2181 | Error | WB001 | -240L | "Unknown backup operation" | You specified an invalid backup statement operation in a call to db_backup. Click here for a list of possible parameters and odbc states. |
| 2182 | Error | WB002 | -241L | "Database backup not started" | A database backup could not be started. Either a backup is already running, or you do not have the required authority (BACKUP, DBA, or REMOTE DBA). Click here for a list of possible parameters and odbc states. |
| 2183 | Error | WB003 | -242L | "Incomplete transactions prevent transaction log renaming" | The last page in the transaction log was read by a call to db_backup. One or more currently active connections have partially completed transactions, preventing the transaction log file from being renamed. Reissue the db_backup call. Click here for a list of possible parameters and odbc states. |
| 2184 | Error | WB004 | -243L | "Unable to delete database file" | You attempted to delete a database file, but it could not be deleted. The file name should not be the same as any database file that is currently in use. Click here for a list of possible parameters and odbc states. |
| 2185 | Error | WB005 | -244L | "Transaction log was truncated" | An operation was being performed on the transaction log such as SQL Remote or Replication Agent processing and the transaction log was truncated by an independent backup during that operation. Click here for a list of possible parameters and odbc states. |
| 2186 | Error | 99999 | -297L | "User-defined exception signaled" | A stored procedure or trigger signaled a user-defined exception. This error state is reserved for use within stored procedures or triggers that contain exception handlers, as a way of signaling an exception that can be guaranteed to not have been caused by the database server. Valid SQLSTATE values range from 99000 to 99999 and are set by the user when executing the signal SQL statement. Click here for a list of possible parameters and odbc states. |
| 2187 | Error | 42W22 | -298L | "Attempted two active database requests" | In embedded SQL, you attempted to submit a database request while you have another request in progress. You should either use a separate SQLCA and connection for each thread accessing the database, or use thread synchronization calls to ensure that a SQLCA is only accessed by one thread at a time. Click here for a list of possible parameters and odbc states. |
| 2188 | Error | 57014 | -299L | "Statement interrupted by user" | You canceled a statement during its execution. The database was able to stop the operation without doing a rollback. If the statement is INSERT, UPDATE, or DELETE, any changes made by the statement will be canceled. If the statement is a data definition statement (for example CREATE TABLE), the statement will be canceled, but the COMMIT that was done as a side effect will not be canceled. Click here for a list of possible parameters and odbc states. |
| 2189 | Error | 40000 | -300L | "Run time SQL error -- %1" | An internal database error occurred. If it can be reproduced, it should be reported to iAnywhere. You may be able to work around this problem by modifying the associated query statement. Click here for a list of possible parameters and odbc states. |
| 2190 | Error | 40W01 | -301L | "Internal database error %1 -- transaction rolled back" | An internal database error occurred. If it can be reproduced, it should be reported to iAnywhere. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| 2191 | Error | 40W02 | -302L | "Terminated by user -- transaction rolled back" | You canceled a statement while the database was executing. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| 2192 | Error | 40W03 | -304L | "Disk full '%1' -- transaction rolled back" | Your hard disk is out of space. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| 2193 | Error | 40W04 | -305L | "I/O error %1 -- transaction rolled back" | SQL Anywhere has detected a problem with your hard disk. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |