Re: serveroutput in PL/SQL scripts
From: Niall Litchfield <n-litchfield_at_audit-commission.gov.uk>
Date: Fri, 24 Aug 2001 13:19:27 +0100
Message-ID: <3b86464f$0$8510$ed9e5944_at_reading.news.pipex.net>
Date: Fri, 24 Aug 2001 13:19:27 +0100
Message-ID: <3b86464f$0$8510$ed9e5944_at_reading.news.pipex.net>
Sorry haven't looked at .tools for a while.
You are right dbms_output buffers the output for display. it then does the actual displaying at the end of the procedure. This is a royal PITA. You could use utl_file to write debug info to a log file though.
-- Niall Litchfield Oracle DBA Audit Commission UK "Adam" <ask_at_me.spam> wrote in message news:ao6h7.101$Nz1.2632_at_news.get2net.dk...Received on Fri Aug 24 2001 - 14:19:27 CEST
> No, because I don't need to output anything to a file. Just the screen,
like
> I wrote. And, YES Serveroutput is ON.
>
>
> "Markus Stuhlpfarrer" <mstuhlpfarrer_at_hollomey.com> wrote in message
> news:3B84EDBA.1F2E14C1_at_hollomey.com...
> > did you set spool on ?
> >
> > Adam wrote:
> >
> > > Hey.
> > >
> > > I have a PL/SQL script which is about 850 lines long. Along the way I
> have
> > > some dbms_ouput.put_line statements to show progress and so on.
> > >
> > > But it seems to me that when I execute the script from SQL*Plus the
> output
> > > doesn't show until the entire script has executed, and this is a
problem
> > > because somewhere along the line it hangs the DB for some reason, and
I
> > > don't know where. I realise I could comment out parts of the program,
> but
> > > that will take 100 years to trace the error. Instead, I would like to
> see
> > > the output lines when they are called, instead of when the script
> finishes,
> > > so that I can see where it fails or infinite loops or whatever.
> > >
> > > Anybody know of a SQL*Plus setting or PL/SQL command that forces the
> output
> > > on screen as the .put_line commands are reached?
> > >
> > > Thanks,
> > > Adam
> >
>
>