Re: Q: DBMS_OUTPUT display while processing?

From: <>
Date: Tue, 10 Aug 1999 15:04:50 GMT
Message-ID: <7opf28$e7m$>

[Quoted] In article <>, wrote:
> A copy of this was sent to
> (if that email address didn't require changing)
> On Sat, 07 Aug 1999 23:23:56 GMT, you wrote:
> >Hi,
> >
> >I have a large PL/SQL package with 20 procedures within the package.
> >The purpose of the package is do some batch process which will take
> >about 10 hours.
> >
> >I tried to have DBMS_OUTPUT.PUT_LINE in every single procedure to
> >out the status so that I can monitor each process(to see if there is
> >errors) while the package is still running. However, the DBMS_OUTPUT
> >didn't display until the whole package is done. This is very
> >Is there any work around?
> >
> >Thanks in advance.
> >
> >Ed
> >
> >
> >Sent via
> >Share what you know. Learn what you don't.
> dbms_output cannot be display until the procedure is done executing.
> one option that works very well is the dbms_application_info. this
allows you
> to set values in the v$session table (to tell where you are) and in
8.0 and up,
> to put many rows in the V$SESSION_LONGOP table with the
> dbms_application_info.set_session_longops procedure. these rows are
> immediately (no commit needed) so they are perfect for monitoring
long running
> procedures from any terminal (a simple query shows the status of a
long running
> procedure that has calls to dbms_application_info in it)....
> --
> See for my columns 'Digging-in to
> Current article is "Part I of V, Autonomous Transactions" updated
June 21'st
> Thomas Kyte
> Oracle Service Industries Reston, VA USA
> Opinions are mine and do not necessarily reflect those of Oracle

Thomas, Can you give us an example for how to use dbms_application_info.set_session_longops procedure ? [Quoted] Thanks Ted Chyn(

Sent via
Share what you know. Learn what you don't. Received on Tue Aug 10 1999 - 17:04:50 CEST

Original text of this message