Home » DbVisualizer Forums » DbVisualizer » DbVisualizer - Support

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

This question is answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 6 - Pages: 1 - Last Post: Jul 30, 2010 6:01 PM Last Post By: Roger Bjarevall
Sammy

Posts: 38
Registered: 10/26/06
Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Posted: Apr 18, 2007 5:15 PM
 
   thread.click_reply Reply

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

Roger Bjarevall


Posts: 3,181
Registered: 12/17/04
Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Posted: Apr 23, 2007 6:55 PM    global.in_response_to.tooltip in response to: Sammy
 
   thread.click_reply Reply
Sammy,

Thanks for your post. This will be fixed in the next EA.

Regards

Roger
Sammy

Posts: 38
Registered: 10/26/06
Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Posted: Jul 29, 2010 3:33 PM    global.in_response_to.tooltip in response to: Sammy
 
   thread.click_reply Reply
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
Sammy

Posts: 38
Registered: 10/26/06
Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Posted: Jul 29, 2010 3:36 PM    global.in_response_to.tooltip in response to: Sammy
 
   thread.click_reply Reply
Sorry - previous post should read we are "now" up to Oracle Database 11g Release 11.1.0.0. DBVis version is 710.1560.
Roger Bjarevall


Posts: 3,181
Registered: 12/17/04
Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Posted: Jul 29, 2010 6:03 PM    global.in_response_to.tooltip in response to: Sammy
 
   thread.click_reply Reply
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
Sammy

Posts: 38
Registered: 10/26/06
Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Posted: Jul 30, 2010 5:30 PM    global.in_response_to.tooltip in response to: Sammy
 
   thread.click_reply Reply
New JDBC is all I needed. Thanks for the usual great support!
Roger Bjarevall


Posts: 3,181
Registered: 12/17/04
Re: Making DBMS_OUTPUT.PUT_LINE work properly with Oracle 10g's 32K limit?
Posted: Jul 30, 2010 6:01 PM    global.in_response_to.tooltip in response to: Sammy
 
   thread.click_reply Reply
Great!

Regards

Roger

Point your RSS reader here for a feed of the latest messages in all forums