Start a new topic

Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?

[This topic is migrated from our old forums. The original author name has been removed]

I'm using Oracle 10g which expanded the size limit on a PUT_LINE from 255 to 32K.  However, DBVisualizer still seems to have the 255 limit.  Consider the following cases:

-- This says "command processed but no rows were affected" - no DBMS output is produced.  Remove 1 character from the string and it works
DECLARE
BEGIN
  DBMS_OUTPUT.PUT_LINE ('1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456');
END;


-- Things work the same way using a PUT, then a PUT_LINE.  Once you cross 255 characters, no error or output is returned
DECLARE
BEGIN
  DBMS_OUTPUT.PUT ('1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890');
  DBMS_OUTPUT.PUT_LINE ('123456');
END;



Hopefully this is something that can be fixed in a configuration file.  If not, I guess I'll just have to wait for a new release.

Thanks for any help,
Sammy


[This reply is migrated from our old forums.]

Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Sammy, Thanks for your post. This will be fixed in the next EA. Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
This problem still seems to exist, and it's been more than 3 years since the original post. Could you please take another look at the problem? We are not up to Oracle Database 11g Release 11.1.0.0. Thanks, Sammy
[This reply is migrated from our old forums. The original author name has been removed]

Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Sorry - previous post should read we are "now" up to Oracle Database 11g Release 11.1.0.0. DBVis version is 710.1560.
[This reply is migrated from our old forums.]

Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Sammy, First make sure you upgrade your version of DbVisualizer. 710.1560 is an early access version that was replaced with the official 7.1 in June. The DBMS_OUTPUT issue was fixed 3 years ago. It requires Oracle 10.2 or later and a JDBC driver that reports proper version information for the database server. What JDBC driver version are you using? Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
New JDBC is all I needed. Thanks for the usual great support!
[This reply is migrated from our old forums.]

Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Great! Regards Roger