Re: enabling dbms_output.put_line without giving set serveroutput on

A copy of this was sent to Anurag <anurag_at_synergy-infotech.com> (if that email address didn't require changing) On Sat, 27 Nov 1999 22:49:54 -0800, you wrote:

>Hi,
>Then what is this dbms_outputenable() .
>

calls to dbms_output.put* just put lines of text into an array.

if you have not called dbms_output.enable -- these calls to put* are ignored (the array is not filled up).

is you issue "set serveroutput on" in sqlplus or svrmgrl, it does 2 things

• it calls dbms_output.enable to tell the dbms_output package to start buffering data.
• it sets a flag in these programs telling them to call dbms_output.get_lines AFTER any statement has been executed (check for output to print on the screen).

You may call dbms_output.enable from your own apps (pro*c, pl/sql etc) and then call dbms_output.get_lines to get the buffered output as well.

so, "set serveroutput on" is the sqlplus command to let sqlplus get the buffered output and print.

dbms_output.enable is the mechanism that tells the dbms_output package to buffer the output.

since dbms_output is used for debugging, it is common to leave the calls to dbms_output in your code and just never call 'enable' unless you need this debug information (you can leave the calls to dbms_output in your code with minimal runtime overhead)

>Thanks
>Anurag
>
>also reply at
>anurag_at_synergy-infotech.com
>
>
>* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
>The fastest and easiest way to search and participate in Usenet - Free!

--
See http://osi.oracle.com/~tkyte/ for my columns 'Digging-in to Oracle8i'... Current article is "Part I of V, Autonomous Transactions" updated June 21'st  

Thomas Kyte                   tkyte_at_us.oracle.com
Oracle Service Industries     Reston, VA   USA

Opinions are mine and do not necessarily reflect those of Oracle Corporation Received on Sun Nov 28 1999 - 07:51:11 CST