Note in-line

Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

  The educated person is not the person 
  who can answer the questions, but the 
  person who can question the answers -- T. Schick Jr


Next public appearance2:
 March 2004 Hotsos Symposium - Keynote
 March 2004 Charlotte NC - OUG Tutorial
 April 2004 Iceland


One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html


Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___February


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


----- Original Message ----- 
> Not a worry, it's a workflow app.  A few users but
> not much load, a little volume.  I just need to make sure a
> given sequence of operations is not undertaken by more than
> one user per group (one lock/group) and a table lock is
> way too heavy to do this.  

Sounds like you just need each user to call allocate_unique
on startup to get a group-specific handle, then do a 
request in exclusive mode before doing the job and 
a release on completion. Users will then naturally queue
and resume with minimum lost time.  You could probably
do the thing just as easily by issuing a select for update
against a group-id row in a table - but dbms_lock makes
it easier because it can bypass the normal commit  activity.




-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jonathan Lewis
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to