Posted on 2002-03-19
Last Modified: 2008-03-03
ERROR at line 1:
ORA-20000: ORU-10028: line length overflow, limit of 255 bytes per line
ORA-06512: at "SYS.DBMS_OUTPUT", line 99
ORA-06512: at "SYS.DBMS_OUTPUT", line 65
ORA-06512: at "SCOTT.FOOL", line 9
ORA-06512: at line 1
Yes, is 255 bytes per line the upper limit. Actaully the column value is in number of lines but package treats in one line. How to increase this display over 255 bytes in SQL%Plus.
Question by:sesh2002

Expert Comment

ID: 6879540
Did you try setting "serveroutput wrapped", which should wrap lines within the linesize value, as needed for your output ?

Expert Comment

ID: 6880000
The ENABLE procedure in DBMS_OUTPUT sets the size of the output buffer while executing.  The maximum size is 1,000,000.  Just use this line in your procedure before calling PUT_LINE:


You can use any buffer size you want.


Author Comment

ID: 6881843
cqilbert78fr, serveroutput wrapped is not there in SQL*PLus. But set wrap on/off it is there but using it, still the error persists.
asimovsky, In SQL*Plus, even if we enable greater size, the error persists. But writing to a file on server, it is okay. Do we have any other packages or SQL*Plus parameter whereby we can avoid this error. --- sesh 2002
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 6881850
asimovsky, what i did was to create a table with single varchar2(300) column and then inserted a string of > 255 characters. When i retreive in PL/SQL and try to display using DBMS_OUTPUT.PUT_LINE, I get this error. -- sesh2002

Author Comment

ID: 6881853
asimovsky, what i did was to create a table with single varchar2(300) column and then inserted a string of > 255 characters. When i retreive in PL/SQL and try to display using DBMS_OUTPUT.PUT_LINE, I get this error. -- sesh2002
LVL 11

Expert Comment

ID: 6882923
You can't avoid that limit of 255 bytes per line.
In fact (I hope the other experts will agree) DBMS_OUTPUT is one of the worst thing created by Oracle. And unfortunately there are no alternative packages that can be used instead.
What you can do is create a simple procedure/package which you'll use instead of DBMS_OUTPUT.
What you have to do is parse the string that needs to be displayed, break it in smaller chunks and display it using DBMS_OUTPUT.
You can even make it even more flexible by overloading your procedures to accept whatever types of variables you want. DBMS_OUTPUT.PUT_LINE accepts only VARCHAR2, DATE and NUMBER.
The easier (and more expensive) way is to purchase such a package. I think that the RevealNet PL/Vision package created by Steven Feuerstein includes that functionality. Unfortunately after Quest Software took over Revelnet evrything on that great site has moved and I can't find anything there!
You can search the site for the PL/Vision package or maybe some other expert knows where to get it from, or knows some other similar tool...
Hope that helps!

Expert Comment

ID: 6885882
see sqlplus help

set linesize xxx - sets limit of line length of output
set serveroutput on xxx - sets limit of bytes printed to output
LVL 11

Expert Comment

ID: 6886494
konektor, the set linesize is a SQL*Plus setting and it doesn't change the limit of the DBMS_OUTPUT. You can set the linesize to several thousand, but you still won't be able to display more than 255 bytes using DBMS_OUTPUT.
set serveroutput on xxx - sets limit of bytes printed to output - that is true, but it sets the total buffer size of DBMS_OUTPUT messageS. It again doesn't affect the DBMS_OUTPUT.PUT_LINE limit.

Accepted Solution

sora earned 30 total points
ID: 6888053
No problem - use procedure SORA_PUT_LINE instead of DBMS_OUTPUT.PUT_LINE   !!!!

create or replace procedure
sora_put_line( line in varchar2, limit in integer)
x varchar2(4000);
n pls_integer := null;
s pls_integer := 1;
 x := substr(line,s,least(limit,(length(line)-s+1) ));
 s := s + length(x);
 if s > length(line)
 end if;
end loop;
end sora_put_line;

Usage example:

                char_per_line IN INTEGER);

****Note: the char_per_line must be less than 255, but the string can be much much much more than 255 chars******

 w varchar2(1000) := '12345678901234567890123456789012345678901234567890';

As you can see the above example is able to output a string which is 50 x 12 = 600 characters

In fact, there is no limit on this one:


Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why doesn't the Oracle optimizer use my index? Querying too much data Most Oracle developers know that an index is useful when you can use it to restrict your result set to a small number of the total rows in a table. So, the obvious side…
Truncate is a DDL Command where as Delete is a DML Command. Both will delete data from table, but what is the difference between these below statements truncate table <table_name> ?? delete from <table_name> ?? The first command cannot be …
Via a live example, show how to take different types of Oracle backups using RMAN.
This video shows how to copy an entire tablespace from one database to another database using Transportable Tablespace functionality.

735 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question