Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| -221L | Error | 2175 | 3B002 | "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. |
| -222L | Error | 2176 | 3BW02 | "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. |
| -230L | Error | 2178 | 08W18 | "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. |
| -231L | Error | 2179 | 08W19 | "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. |
| -240L | Error | 2181 | WB001 | "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. |
| -241L | Error | 2182 | WB002 | "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. |
| -242L | Error | 2183 | WB003 | "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. |
| -243L | Error | 2184 | WB004 | "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. |
| -244L | Error | 2185 | WB005 | "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. |
| -245L | Error | 2259 | 28W04 | "Integrated login failed" | The integrated login failed. You may not have a system account on the server machine. Click here for a list of possible parameters and odbc states. |
| -246L | Error | 2262 | 28W05 | "Integrated logins are not supported for this database" | The current database is an older database and does not have the information to map integrated login IDs to database user IDs. You must upgrade your database to use integrated logins. Click here for a list of possible parameters and odbc states. |
| -247L | Error | 2263 | 28W06 | "The integrated login ID guest can only be mapped to the guest database user ID" | You attempted to map the guest login ID to something other than guest. Click here for a list of possible parameters and odbc states. |
| -248L | Error | 2264 | 28W07 | "Cannot map a login ID to the sys or public user ID" | You attempted to map a login ID to either SYS or PUBLIC. Click here for a list of possible parameters and odbc states. |
| -249L | Error | 2265 | 28W08 | "The login ID '%1' is already mapped to user ID '%2'" | You attempted to map a login ID twice. Click here for a list of possible parameters and odbc states. |
| -250L | Error | 2061 | 54003 | "Identifier '%1' too long" | An identifier was specified is longer than 128 bytes. Click here for a list of possible parameters and odbc states. |
| -251L | Error | 2062 | 52W06 | "Foreign key '%1' for table '%2' duplicates an existing foreign key" | You attempted to define a foreign key that already exists. Click here for a list of possible parameters and odbc states. |
| -260L | Error | 2139 | 42W14 | "Variable '%1' not found" | You attempted to DROP or SET the value of a SQL variable that was not created or was previously dropped. Click here for a list of possible parameters and odbc states. |
| -261L | Error | 2140 | 42W15 | "There is already a variable named '%1'" | You attempted to create a variable with the name of another variable that already exists. Click here for a list of possible parameters and odbc states. |
| -262L | Error | 2141 | 42W24 | "Label '%1' not found" | You reference a label in a LEAVE statement, but the label could not be found. Click here for a list of possible parameters and odbc states. |
| -263L | Error | 2142 | 42W25 | "Invalid absolute or relative offset in FETCH" | You specified an offset in a FETCH that was invalid or NULL. Click here for a list of possible parameters and odbc states. |