>Thanks Edward,
>
>I was thinking that SYS(2011) checked to see if anyone had the record locked - that could have been a fun one... I DO infact want to check if anyone has records locked. It looks like I'll need to perform a SYS(2011) to check for the current W/S's locks and include them in the result set, then attempt to lock the remaining records, and only include the failed locks in my result set.
>
>It could be worse.

You may have separate table where application will write/delete entries (primary keys) when it locks/unlocks records. So, you can always have some administrative utility to browse this table and see user's activity. Obviously, it makes sense if you use some flavor of pessimistic buffering scheme.