Re: SYS.DBMS_OUTPUT buffer overflow... Limited to 2000 bytes of output.(?)
Date: 1997/04/18
Message-ID: <5j82po$mrm_at_news.rl.af.mil>#1/1
First off thanks to everyone from all over the world that has replied to this posting. Germany, France, Russia and AOL members...
Actually you do see the output. The buffer seems to automatically flush when it hits its default of 2000 chars. I was getting about 2000 chars of output and then and error message telling me I exceded the default 2000 byte limit. That is why I new the program was working and it was entirely a buffer size limitation problem.
So... Your recommendations worked great and thanks again...
One other good thing came of this though, I purchased the ORACLE PL/SQL Programming book by ORACLE PRESS. Author Scott Urman. On page 353 he states the default limit is 20,000. Needless to say I(we) now know it is definetely 2000. So, I emailed him and let him know he has an error . So far after reading this book for about an hour, I would say it is pretty good.
So... Two people benifited from this posting. Myself and the author. I love Usenet. Its the best way to solve those funny little coding problems that would otherwise cause a person pull out his/her hair.
Thanks again...
Mark...
In article <5j5ora$imc$1_at_mark.ucdavis.edu>, wgweis_at_ucdavis.edu says...
>
>Everyone posting to this letter seems to have the same idea...
>But ... does anyone have an idea how to get the d**** thing
>to flush its' buffer? There doesn't seem to be any PL/SQL
>equivalent of the C function flush(<file descriptor>).
>the reason I ask is that if your procedure / function crashes
>you will NOT see the output.
>
>citton_at_shom.fr (Citton Laurent) wrote:
>
Received on Fri Apr 18 1997 - 00:00:00 CEST
