From: smith@ali.com.au
Subject: Re: DBMS_OUTPUT not printing . . .
Date: 1998/03/03
Message-ID: <6dii8c$1eu$1@nnrp1.dejanews.com>#1/1
References: <DA7A9D0CBC2A0825.120B9F3732CFCFE7.447700676252C782@library-proxy.airnews.net>
X-Originating-IP-Addr: 203.2.182.223 proxy [proxyserver (MSProxy/1.0) for 192.0.0.34]
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 4.0; Windows 95; BPH01)
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Wed Mar 04 03:37:20 1998 GMT
Newsgroups: comp.databases.oracle.misc,comp.databases.oracle.server,comp.databases.oracle.tools



In article <DA7A9D0CBC2A0825.120B9F3732CFCFE7.447700676252C782@library-
proxy.airnews.net>,
  "Douglas Heydrick" <heydrick@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@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@airmail.net
>
>
You need to include the line

       set serveroutput on;

at the start of your SQL*PLUS script.


-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/   Now offering spam-free web-based newsreading


