Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Q: Asynchronous processing

Re: Q: Asynchronous processing

From: Doug Cowles <dcowles_at_bigfoot.com>
Date: Sat, 07 Aug 1999 20:45:11 -0400
Message-ID: <37ACD317.F44CD2F7@bigfoot.com>


I'm acutally just learning about this topic myself, but you might consider the dbms_pipe package. This allows inter-session communication irregardless of commits. Off hand I would say send a message to a pipe in the trigger, then things won't be blocked, and then have you procedure listening on the other end of the pipe. I'm looking into it so that I can have a trigger contact
the operating system and page me when there is an entry on a custom error table.
I'd be curious how you make out..

huh wrote:

> Hi,
>
> Can someone suggest me how to invoke a PL/SQL procedure asynchronously?
> I've got a table A with columns task and status. I need a PL/SQL procedure
> to be run in case the status has changed. I can't use a simple trigger
> because
> the procedure's task is extensively time consuming and I can't block any
> connection for a long time.
>
> My intention is to run "somehow" this procedure from trigger.
> I guess ORACLE uses sheduled jobs.
> Can I use it? Programmatically create a job (which will execute my
> procedure)
> and programaticaly run this job from trigger....
>
> Pointers to manuals (or other useful accessible info sources) are good for
> me too.
>
> Maybe there is a more elegant way to do this.
> What about limitations?
>
> TIA
>
> --
> Thank you for keeping >anti-spam< habit:
> not including my address in your reply.
Received on Sat Aug 07 1999 - 19:45:11 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US