Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 220 | "Savepoint '%1' not found" |
|---|---|
Constant | SAVEPOINT_NOTFOUND |
SAP Sybase Error Number | 2174 |
SQL State | 3B001 |
SQL Code | -220L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of savepoint. |
Probable Cause | You attempted to rollback to a savepoint that does not exist. |
| Error 221 | "ROLLBACK TO SAVEPOINT not allowed" |
|---|---|
Constant | ROLLBACK_NOT_ALLOWED |
SAP Sybase Error Number | 2175 |
SQL State | 3B002 |
SQL Code | -221L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted a ROLLBACK TO SAVEPOINT within an atomic operation to a savepoint established before the atomic operation. |
| Error 222 | "Result set not allowed from within an atomic compound statement" |
|---|---|
Constant | RESULT_NOT_ALLOWED |
SAP Sybase Error Number | 2176 |
SQL State | 3BW02 |
SQL Code | -222L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You used a SELECT statement with no INTO clause or a RESULT CURSOR statement within an atomic compound statement. |
| Error 230 | "sqlpp/dblib version mismatch" |
|---|---|
Constant | PP_DBLIB_MISMATCH |
SAP Sybase Error Number | 2178 |
SQL State | 08W18 |
SQL Code | -230L |
ODBC 2 State | 08801 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | Your executable has Embedded SQL source files that were preprocessed with a version of sqlpp that does not match the database interface library. |
| Error 231 | "Client/database server version mismatch" |
|---|---|
Constant | DBLIB_ENGINE_MISMATCH |
SAP Sybase Error Number | 2179 |
SQL State | 08W19 |
SQL Code | -231L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | Your executable uses a database interface library that does not match the version number of the database server. |
| Error 240 | "Unknown backup operation" |
|---|---|
Constant | UNKNOWN_BACKUP_OPERATION |
SAP Sybase Error Number | 2181 |
SQL State | WB001 |
SQL Code | -240L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You specified an invalid backup statement operation in a call to db_backup. |
| Error 241 | "Database backup not started" |
|---|---|
Constant | BACKUP_NOT_STARTED |
SAP Sybase Error Number | 2182 |
SQL State | WB002 |
SQL Code | -241L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A database backup could not be started. Either a backup is already running, or you do not have the required system privileges or authority (BACKUP, DBA or REMOTE DBA). |
| Error 242 | "Incomplete transactions prevent transaction log renaming" |
|---|---|
Constant | BACKUP_CANNOT_RENAME_LOG_YET |
SAP Sybase Error Number | 2183 |
SQL State | WB003 |
SQL Code | -242L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
| Error 243 | "Unable to delete database file" |
|---|---|
Constant | BACKUP_UNABLE_TO_DELETE_FILE |
SAP Sybase Error Number | 2184 |
SQL State | WB004 |
SQL Code | -243L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
| Error 244 | "Transaction log was truncated" |
|---|---|
Constant | LOG_TRUNCATED |
SAP Sybase Error Number | 2185 |
SQL State | WB005 |
SQL Code | -244L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | While an operation was occurring on the transaction log, the transaction log was truncated by another operation. |
| Error 245 | "Integrated login failed" |
|---|---|
Constant | INTEGRATED_LOGON_FAILED |
SAP Sybase Error Number | 2259 |
SQL State | 28W04 |
SQL Code | -245L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | The integrated login failed. You may not have a system account on the server computer. |
| Error 246 | "Integrated logins are not supported for this database" |
|---|---|
Constant | INTEGRATED_LOGON_UNSUPPORTED |
SAP Sybase Error Number | 2262 |
SQL State | 28W05 |
SQL Code | -246L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | 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. |
| Error 247 | "The integrated login ID guest can only be mapped to the guest database user ID" |
|---|---|
Constant | INTEGRATED_LOGON_GUESTMAP |
SAP Sybase Error Number | 2263 |
SQL State | 28W06 |
SQL Code | -247L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | You attempted to map the guest login ID to something other than guest. |
| Error 248 | "Cannot map a login ID to the sys or public user ID" |
|---|---|
Constant | LOGON_SYSMAP |
SAP Sybase Error Number | 2264 |
SQL State | 28W07 |
SQL Code | -248L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | You attempted to map a login ID to either SYS or PUBLIC. |
| Error 249 | "The login ID '%1' is already mapped to user ID '%2'" |
|---|---|
Constant | LOGON_MAPPED |
SAP Sybase Error Number | 2265 |
SQL State | 28W08 |
SQL Code | -249L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Parameter 1 | Name of the login ID that is already mapped. |
Parameter 2 | Name of the user that the login ID is already mapped to. |
Probable Cause | You attempted to map a login ID twice. |
| Error 250 | "Identifier '%1' too long" |
|---|---|
Constant | IDENTIFIER_TOO_LONG |
SAP Sybase Error Number | 2061 |
SQL State | 54003 |
SQL Code | -250L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The identifier that is too long. |
Probable Cause | An identifier that was specified is longer than 128 bytes. |
| Error 251 | "Foreign key '%1' for table '%2' duplicates an existing foreign key" |
|---|---|
Constant | DUPLICATE_FOREIGN_KEY |
SAP Sybase Error Number | 2062 |
SQL State | 52W06 |
SQL Code | -251L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The role name of the new foreign key. |
Parameter 2 | The table containing the foreign key. |
Probable Cause | You attempted to define a foreign key that already exists. |
| Error 260 | "Variable '%1' not found" |
|---|---|
Constant | VARIABLE_NOT_FOUND |
SAP Sybase Error Number | 2139 |
SQL State | 42W14 |
SQL Code | -260L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the variable that could not be found. |
Probable Cause | You attempted to DROP or SET the value of a SQL variable that was not created or was previously dropped. |
| Error 261 | "There is already a variable named '%1'" |
|---|---|
Constant | VARIABLE_EXISTS |
SAP Sybase Error Number | 2140 |
SQL State | 42W15 |
SQL Code | -261L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the variable that already exists. |
Probable Cause | You attempted to create a variable with the name of another variable that already exists. |
| Error 262 | "Label '%1' not found" |
|---|---|
Constant | LABEL_NOT_FOUND |
SAP Sybase Error Number | 2141 |
SQL State | 42W24 |
SQL Code | -262L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the label that could not be found. |
Probable Cause | You reference a label in a LEAVE statement, but the label could not be found. |