Re: Q: DBMS_OUTPUT display while processing?

From: Chris Hamilton <>
Date: Tue, 10 Aug 1999 04:23:34 GMT
Message-ID: <>

On Mon, 09 Aug 1999 22:31:51 +0800, Connor McDonald <> wrote:

>Chris Hamilton wrote:

>> I had a similar problem. I created a series of "Job Control" tables:
>> JC_JOBS -- one row per batch job per run.
>> JC_TASKS -- one row per task of each job.
>> JC_EVENTS -- one row per event of each task.
>> And a package called JOB_CONTROL.
>> My batch PL/SQL programs make calls to JOB_CONTROL, which in turn
>> populates the tables with status rows, which have timestamps and
>> descriptions of the tasks. You can then track the ongoing status of
>> jobs, seeing where it is and how long it took to get to that point.
>> Also tracked are parameters passed to the various events (procedures),
>> etc.
>> Very handy.
>> Chris
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Christopher Hamilton
>> Oracle DBA -- Wall Street Sports
>The only downside being that you need to commit to see that status from
>a different session...

Yes, true. For us, though that's okay, due to the nature of our batch jobs. Each "event" is pretty much something that should be committed anyway.

Your mileage may vary, of course.


Christopher Hamilton
Oracle DBA -- Wall Street Sports Received on Tue Aug 10 1999 - 06:23:34 CEST

Original text of this message