Well, I don't know about anyone else, but I make use of it to synchronize data upload
programs for our testers. Can't have two instances of the upload program processing
the same tester, they'd duplicate data. Anyhow, we normally run 4 instances of this
program the dbms_lock package works
I came across a very nice example a while ago
where there were 4 concurrent sessions feeding
data into a holding table, and one session consuming
from the table.
The rules said that the consumer could not run
while the producers were loading the table, but
multiple producers were allowed to run.
, but I like it)... there is a
nifty wrapper for DBMS_LOCK. I based my code off of that.
From: Carel-Jan Engel [EMAIL PROTECTED]
Date: 2004/01/21 Wed AM 08:24:25 EST
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: Has anyone done any scalability work on dbms_lock
Hmm, that's actually a very good idea.
It might actually do the job here. Thanks.
Nuno Souto
[EMAIL PROTECTED]
Jamadagni, Rajendra [EMAIL PROTECTED] wrote:
if it is single instance you could also use global application
contexts ... (alas they don't work in RAC across node) ...
--
Please
