![pl sql developer set serveroutput on pl sql developer set serveroutput on](https://cf2.ppt-online.org/files2/slide/q/QNRtOJZrp2nPbFGhAozxjDg7eW0vMyXLKw8E1V/slide-13.jpg)
SQL> insert /*+ append monitor gather_plan_statistics */ into t1ģ ( select 1 from dual connect by level commit SQL> create table t1 nologging as select * from t where 1=0 SQL> create table t as select * from dba_objects Here's an example - firstly, with the database NOT in force logging mode It will be due to the execution plan of the query. It might be chewing up temp space, but it wont be due to logging or force logging. ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT If I pushed it to just an endless loop, eventually I got: Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
![pl sql developer set serveroutput on pl sql developer set serveroutput on](https://www.tutorialesprogramacionya.com/oracleya/temarios/imagentema/foto069.jpg)
![pl sql developer set serveroutput on pl sql developer set serveroutput on](https://facultyweb.kennesaw.edu/xtian2/images/5433lab/1.jpg)
My laptop did 500meg without any problemsģ dbms_output.put_line(rpad('x',1000,'x')) They might be getting an error, but I'd be surprised if its the SAME error. After all.who is going *read* all that output? So if you do 10,000 dbms_output calls with 1000 bytes in each, you'd expect to consume (approx) 10,000,000 bytes of memory for that session.Įventually.presumably you'll run out of process and/or server memory - at which point you'd have to ask yourself if that's really a practical use for dbms_output. "As there is no performance penalty, use UNLIMITED unless you want to conserve physical memory."īasically we are simply just going to consume memory (because we simply hold all the messages in a buffer until the call finishes).