We use the following structure to utilize the
features of DBMS_ALERT:
Job_Server; UNIX SCript
While true do
# wait for dbms_alert.signal
sqlplus uname/pwd _at_dbms_waitone
Start_Some_Unix_Job &
Done
A trigger in a table causes the signal to be generated. THis
in turn fires off the Unix job. This works great, but consider
the following case:
There is a definite interval between Start_Some_Unix_Job and
the next waitone call. In this period, if some signal is generated, that
client is not serviced by the Job_Server. I want to avoid this. ORACLE
does not (as far as I can tell) stack the sgnals so that the next time
the server comes around and waits, it will get signalled automatically
because, while it was away kicking off the job, some one else had signalled.
How do I get this done? Is DBMS_PIPE the answer? Do Gurus here have sample
DBMS_PIPE code that I can use as a basis?
thanks a lot,
-Badri
Received on Wed Mar 13 1996 - 00:00:00 CET
