Re: more dbms_alert problems

mlcampb1_at_mikec.b30.ingr.com (Mike Campbell) writes: [code deleted, except for this call]
> dbms_output.put_line(to_char(dept_record.deptno) || ' ' ||
 

>Having gotten all of this set up I now get into SQL*Plus in 2 different
>windows. In window 1 I set serveroutput on so that my dbms_output stuff
>will work and then execute the mike procedure. I am surprised because
>when I execute the mike procedure I don't get anything displayed
>immediately like I thought I would since I do a dbms_output BEFORE my
>call to dbms_alert.waitone. What happens is that after my timeout period
>(15 secs) has expired the results come back from my initial dbms_output
>loop and then 'my error text' gets displayed. It does not go back
>through the <<readagain>> loop like I was hoping.

[text deleted]

>Any help here would be appreciated.

It's documented *somewhere*, but what happens in SQL*Plus when you set serveroutput on is that SQL*Plus collects and prints serveroutput when your call returns - ie, you *won't* see anything displayed in SQL*Plus until your function/procedure call returns. This is because SQL*Plus "blocks" until your call returns. Hence, you will not see any text immediately, only hen your procedure finishes.

>==============================================================================
>Mike Campbell Phone : (205)730-3623
>Senior Customer Application Engineer Internet : mlcampb1_at_ingr.com
>Intergraph Corp. Fax : (205)730-3300
>Huntsville, AL 35894-0001 Mailstop : GD3002

--
Ken Stewart,                    Telephone:   (301) 907 2225
Oracle Federal,     	        Fax:         (301) 657 0037
Bethesda, MD 20814              Internet:    kstewart_at_us.oracle.com