Mode Requested Lock mode requested. For the TX lock, lock id1 and lock id2 are the same when they are contending for the same resouces. Within the block, we have a record of the each transactions pertaining to the data in that particular block. If the transaction is not committed or rolled back, then other subsequent transactions may have to wait for that resource. This is easily resolved by looking at a combination of two monitors.
Most locking issues are application specifics.
Killing the unix shadow process which is not recommended. When killing the unix shadow process, please be careful of shared servers in a multi-threaded environment. This is very similar to the monitor lock output. Again, SID 6 and 9 are waiting on SID 5. This may not indicate the statement that is holding the resource.