Re: serveroutput in PL/SQL scripts

[Quoted] [Quoted] There is NONE! A big shame, since Oracle is such a big company.

DBMS_OUTPUT.put_line is queuing ALL your output to a PL/SQL table whose max [Quoted] size is 1,000,000 characters (only if you set it that high, the default is much lower).

And, as you noticed, the msgs don't come out until after the PL/SQL has ended. Very unuseful.

I wrote something that uses TEXT_IO for use in Forms and Reports, but TEXT_IO isn't available outside of them. Mine writes to a file and closes it [Quoted] after each write, so I can at least get an idea of how things are going.

There are 'options', do a google search on DBMS_OUTPUT to see the ideas about pipes. It sounds like more work than anyone should have to do to get something so simple as console I/O.

"Adam" <ask_at_me.spam> wrote in message news:LE4h7.64$Nz1.1724_at_news.get2net.dk...
> 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
>
>
Received on Mon Aug 27 2001 - 16:17:25 CEST