Re: Simple PL/SQL output question

From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Wed, 9 Mar 2011 17:22:23 +0000
Message-ID: <AANLkTi=2VUnv=zCOc0KVUAHdeDDFvuO8VGzB_est8hdn_at_mail.gmail.com>

I don't know about TOAD but for R to work I'd expect to have a DBMS_OUTPUT.ENABLE(....) line in the anonymous block itself.

On Wed, Mar 9, 2011 at 4:29 PM, Dennis Williams < oracledba.williams_at_gmail.com> wrote:

> Thanks Mike. Here is an abbreviated version of my script.
>
> SET ECHO OFF
> SET VERIFY OFF
> SET SERVEROUTPUT ON
> DECLARE
> -- local variables and cursors
> BEGIN
> -- PL/SQL code
> DBMS_OUTPUT.PUT('------------------------------------------');
> DBMS_OUTPUT.NEW_LINE;
> DBMS_OUTPUT.PUT_LINE('QH Source Lot ID = '||LotRec.AppID);
> DBMS_OUTPUT.PUT_LINE('QH State = '||LotRec.State);
> END;
> /
>
> On Wed, Mar 9, 2011 at 10:21 AM, Michael Moore <michaeljmoore_at_gmail.com>wrote:
>
>> It would help to SEE what you did.
>> Mike
>>
>>
>> On Wed, Mar 9, 2011 at 7:43 AM, Dennis Williams <
>> oracledba.williams_at_gmail.com> wrote:
>>
>>> List,
>>>
>>> I recently wrote a SQL script containing a PL/SQL anonymous block. I used
>>> DBMS_OUTPUT to sent results to the screen. This worked fine when I copied
>>> and pasted the script into a SQL*Plus session. However, when I just hit "r"
>>> to rerun the script, I noticed that it produced no output. Later I passed
>>> this to a user who ran it using Toad and got no output. Can anybody tell me
>>> what (isn't) going on?
>>>
>>> The reason I used PL/SQL in this manner is that I needed more logic than
>>> SQL itself could provide. In our environment, creating database objects
>>> requires a lot of red tape, but we have a read-only account that can be used
>>> to run queries or ad-hoc scripts.
>>>
>>> Thanks,
>>> Dennis Williams
>>>
>>
>>
>

-- 
Niall Litchfield
Oracle DBA
http://www.orawin.info

--
http://www.freelists.org/webpage/oracle-l

Received on Wed Mar 09 2011 - 11:22:23 CST