Re: DBMS_OUTPUT not printing . . .

From: Simons Michael <msimons_at_laola.de>
Date: 1998/03/06
Message-ID: <34FF3632.13E51A61_at_laola.de>#1/1


smith_at_ali.com.au wrote:
>
> In article <DA7A9D0CBC2A0825.120B9F3732CFCFE7.447700676252C782_at_library-
> proxy.airnews.net>,
> "Douglas Heydrick" <heydrick_at_airmail.net> wrote:
> >
> > A stored procedure exists on database 'A' (proc). I tried to execute said
> > procedure from database 'B' within SQL*Plus (execute proc_at_A). There are
> > DBMS_OUPUT statements in the stored procedure which do not produce any
> > output from the SQL*Plus session on database 'B'.
> >
> > doug
> >
> > heydrick_at_airmail.net
> >
> >
> You need to include the line
>
> set serveroutput on;
>
> at the start of your SQL*PLUS script.

I guess the problem is based on using a package variable (within dbms_output) in a distributed environment. Calling proc_at_A connected to B initiates an instance of dbms_output_at_A. The output of proc_at_A is stored in dbms_output.buffer_at_A. SQL*Plus only prints the contents of dbms_output.buffer_at_B and that is in need nothin'. bye michael

-- 
---------------------------------------------------------
.. and on the third day he rebooted into Linux-1.3.84 ...
   (Linus Torvalds, Easter Kernel Release 1996)
Received on Fri Mar 06 1998 - 00:00:00 CET

Original text of this message