20
Process became runnable before lock it was waiting for was released.
The Lock Manager maintains queues of lock requests to enable server tasks to obtain read, write, and update locks as needed. A task sleeps while waiting for a lock request to be granted. Error 1249 is raised when the task awakes but the Lock Manager detects an abnormal condition in the lock queue for that lock. Error 1249 is raised in the following states:
State |
Meaning |
|---|---|
1 |
The lock request was granted, but the lock is not at its expected position in the queue. |
2 |
The lock received a signal to requeue, but it is not at its expected position in the queue. |
Error 1249 is caused by an Adaptive Server problem and breaks the connection to the server. In a common scenario leading to this error, separate sessions open cursors on the same table, and the user aborts one session in the middle of an update; attempting the same transaction again raises the 1249 error.
Call Sybase Technical Support.
When you call Sybase Technical Support, have the information available that is listed in “Reporting errors”.
All versions
