The session requests the mutex for a cursor object in exclusive mode, and it must wait because the resource is busy. The mutex is busy because either the mutex is being held in exclusive mode by another session or the mutex is being held shared by one or more sessions. The existing mutex holder(s) must release the mutex before the mutex can be granted exclusively.
| Parameter | Description |
|---|---|
| P1 | Hash value of cursor |
| P2 | Mutex value (top 2 bytes contain SID holding mutex in exclusive mode, and bottom two bytes usually hold the value 0) |
| P3 | Mutex where (an internal code locator) OR’d with Mutex Sleeps |
Oracle Database Internal Mechanism 