"User '%1' has the row in '%2' locked"
Item | Description |
---|---|
SQLCode |
-210L |
Constant |
LOCKED |
SQLState |
42W18 |
ODBC 2 State |
40001 |
ODBC 3 State |
40001 |
Sybase Error Code |
2169 |
Severity Code |
|
Parameter 1 |
Name of another user. |
Parameter 2 |
Table that generates the error. |
The operation failed because another connection holds a lock on the same object you are attempting to modify. With INSERT, UPDATE, DELETE, SELECT, or MERGE statements this error is typically caused by attempting to read or write a row that is locked by another user, while the database option 'blocking' is set to Off. With data definition statements, including CREATE, DROP, GRANT, REVOKE, REFRESH, or ALTER, this error can be generated when the connection executing the DDL statement is unable to obtain an exclusive lock on the object to be modified (table, view, materialized view, or index) so that the operation can proceed.