Re: triggers, db jobs, & raising errors

So would there be another method for calling a stored procedure from another stored procedure such that the caller continues while the other runs? We were trying to achieve some degree of parallelism in processes (vs. in a single query). Is there some distinction between a "batch job" and a "stored procedure" that I'm missing, other than that the latter necessarily resides in the database?

Thanks,
Neal

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:oai6luc116v1siv6au6hu6kmemtco7c7rn_at_4ax.com...
> On Thu, 08 Aug 2002 21:22:23 GMT, "Neal Helman" <nhelman_at_peakpeak.com>
> wrote:
>
> >I realize that the job is probably running under a background process,
but
> >isn't there some sort of connection between the calling connection and
that
> >background process?
>
> There isn't. Why should it? Basically you run batch jobs through
> dbms_job.
> You are misusing the dbms_job facility for purposes it wasn't designed
> for.
>
> Regards
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Fri Aug 09 2002 - 23:53:25 CDT