Actually it is possible to set UNLIMITED but unfortunately it does not have the expected effect. I've run the following code in SQL Developer:

SET SERVEROUTPUT ON SIZE UNLIMITED
BEGIN
   FOR I IN 1..100000 LOOP 
      dbms_output.put_line (i || ' this is a line');
   END LOOP;
END;
/

The output was:

(...)
50553 this is a line
50554 this is a line
50555 this is a line


Error starting at line : 2 in command -
BEGIN
   FOR I IN 1..100000 LOOP 
      dbms_output.put_line (i || ' this is a line');
   END LOOP;
END;
Error report -
ORA-20000: ORU-10027: buffer overflow, limit of 1000000 bytes
ORA-06512: at "SYS.DBMS_OUTPUT", line 32
ORA-06512: at "SYS.DBMS_OUTPUT", line 97
ORA-06512: at "SYS.DBMS_OUTPUT", line 112
ORA-06512: at line 3
20000. 00000 -  "%s"
*Cause:    The stored procedure 'raise_application_error'
           was called which causes this error to be generated.
*Action:   Correct the problem as described in the error message or contact
           the application administrator or DBA for more information.

This shows that SQL Developer 17.4.0 reduces the output to 1000000 bytes.

However, maybe it is still a good idea to set UNLIMITED and let the SQL Developer team know about this limitation. In that case we may expect that in a future version the buffer is in fact unlimited.

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions