How to manage buffer overflow

Question

hi
If stored procedure is written and if the buffer overflows then how do i tackle buffer overflow.
Thanks
ram

Answer 1

> DBMS_OUTPUT knows nothing about "Standard Output".
Exactly. And to expand on William's comments.. <adding some weight to it by brandishing a lead pipe> ;-)
That "buffer" sits smack inside the PGA as a PL/SQL static variable. And throwing tons of data into is just plain stupid.
The best place for data is where? In some PL/SQL collection variable? That consumes "expensive" (dedicated and not shared) server memory? That needs to be "cleaned" by a client call (and does this really free the memory malloc'ed)? Data that cannot be filtered, aggregated, sorted, and analysed?
Or is the best place for data in a table? An Oracle table? That can be filtered, sorted, aggregated and analysed? That can have a trigger to capture PL/SQL call stack and neat session stuff for debugging and analysis.
And yes, I think we need to be very clear and very blunt about this.
DBMS_OUTPUT is primitive.
DMBS_OUTPUT is primarily for debugging purposes.
DBMS_OUTPUT has no place in production code.
DBMS_OUTPUT is not a "write" method to some "standard output".
Using DBMS_OUTPUT as some render-client-display is missing the very basic issue of what client-server is.
Is missing the point of how to use Oracle. And use it correctly.
And if you think that DBMS_OUTPUT is a means to buffer/cache data for some report writing purposes, or for some client to retrieve.. then. you are missing it by a very, very, obscenely wide margin.