Forum Stats

  • 3,770,505 Users
  • 2,253,129 Discussions
  • 7,875,493 Comments

Discussions

Categories

SQL Developer 17.2 doesn't show DBMS Output

andre_d
andre_d Member Posts: 4
edited Jul 24, 2017 7:50AM in SQL Developer

Hi,

I am testing version 17.2 of SQL Developer and have stumbled across this problem:

SQL Developer does not display the DBMS server output, neither in the connected DBMS Output window nor in the Script Output window.

To test I used the following code in a regular worksheet:

set serveroutput on;

begin DBMS_OUTPUT.PUT_LINE('this is dbms_output speaking'); end;

The DBMS Output window shows nothing, the Script Output window just outputs that the script ran successfully.

On the previous version of SQL Developer ( Version 4.2.0.17.089, Build 17.089.1709) this works as excpeted, showing the text in both windows.

I am using:

- SQL Developer (Version 17.2.0.188, with JDK included)

- Windows 7 Enterprise with German region settings

- Oracle 10g database with german NLS

Is this a bug or am I missing some sort of configuration option?

Regards, André

Frank Orellana
· Share on TwitterShare on Facebook

Best Answer

  • Gary Graham-Oracle
    Gary Graham-Oracle Member Posts: 3,256 Bronze Crown
    edited Jul 18, 2017 11:17AM Accepted Answer

    As explained in http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf even extended support for 10g expired in July 2013, and any follow-on sustaining support does not include new patches for the database itself, but might get you a SQL Developer fix in a patch or upgrade.  I say "might" since one possible resolution status for a bug is "NOT FEASIBLE TO FIX".

    You should also note, due to dependencies with other components in the Oracle stack, that a fix or workaround might not be found only in the database or the application.  Here is a case involving 10g and 17.2 where the workaround is to avoid using older versions of the JDBC driver:

    So, in your case, it may possibly make a difference whether you use the default JDBC driver (12.2.0.1) shipped with 17.2, or a previous driver (potentially as old as 11.2.0.3).    

    · Share on TwitterShare on Facebook

Answers

  • thatJeffSmith-Oracle
    thatJeffSmith-Oracle Distinguished Product Manager Posts: 8,094 Employee
    edited Jul 12, 2017 8:43AM

    I don't see any issues in my setup.

    Win7, connected to 12c database running on Oracle Linux

    Version 17.2.0.188

    dbms-output172.png

    · Share on TwitterShare on Facebook
  • dz_r
    dz_r Member Posts: 69
    edited Jul 12, 2017 8:59AM

    I have the same problem when I'm connected to database 10g.

    With database 12c it works.

    Frank Orellana
    · Share on TwitterShare on Facebook
  • thatJeffSmith-Oracle
    thatJeffSmith-Oracle Distinguished Product Manager Posts: 8,094 Employee
    edited Jul 12, 2017 9:50AM

    does v4.2 work with your 10g db? and exactly what version of 10g?

    · Share on TwitterShare on Facebook
  • Andris Perkons-Oracle
    Andris Perkons-Oracle Posts: 1,099 Employee
    edited Jul 12, 2017 11:12AM

    Hi,

    I can confirm that 4.2 works with 10g (unpatched 10.2.0.1 on Solaris x86), whereas 17.2 does not.

    11g, 12c -> no problems.

    Andris

    · Share on TwitterShare on Facebook
  • dz_r
    dz_r Member Posts: 69
    edited Jul 13, 2017 1:48AM 
    thatJeffSmith-Oracle napisał(-a):does v4.2 work with your 10g db? and exactly what version of 10g?

    SQL Developer 4.2.0.17.089 works fine with database 10g.

    New SQL Developer 17.2.0.188 works with:

    - Oracle Database 12c Standard Edition Release 12.1.0.2.0

    - Oracle Database 11g Enterprise Edition Release 11.2.0.1.0

    and doesn't work with:

    - Oracle Database 10g Enterprise Edition Release 10.2.0.4.0

    · Share on TwitterShare on Facebook
  • andre_d
    andre_d Member Posts: 4
    edited Jul 13, 2017 3:53AM

    Using Oracle DB 10.2.0.5.0 Standard Edition on Linux x86 64-bit here.

    SQL Developer Version 4.2.0.17.089 works

    SQL Developer Version 17.2.0.188 does not

    · Share on TwitterShare on Facebook
  • thatJeffSmith-Oracle
    thatJeffSmith-Oracle Distinguished Product Manager Posts: 8,094 Employee
    edited Jul 13, 2017 9:55AM

    You'll need to log an SR with MOS on this. I'm assuming you have an extended support contract on 10g since it's about 7 years old.

    · Share on TwitterShare on Facebook
  • andre_d
    andre_d Member Posts: 4
    edited Jul 18, 2017 5:48AM

    Unfortunately we don't have extended support for that database, so I can't log an SR. But the db will be updated soon, so I don't worry.

    But just for my understanding: since the 10.2. database version is out of regular support, it is also not "officially" supported by SQL Developer anymore, only via Extended support?

    · Share on TwitterShare on Facebook
  • Gary Graham-Oracle
    Gary Graham-Oracle Member Posts: 3,256 Bronze Crown
    edited Jul 18, 2017 11:17AM Accepted Answer

    As explained in http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf even extended support for 10g expired in July 2013, and any follow-on sustaining support does not include new patches for the database itself, but might get you a SQL Developer fix in a patch or upgrade.  I say "might" since one possible resolution status for a bug is "NOT FEASIBLE TO FIX".

    You should also note, due to dependencies with other components in the Oracle stack, that a fix or workaround might not be found only in the database or the application.  Here is a case involving 10g and 17.2 where the workaround is to avoid using older versions of the JDBC driver:

    So, in your case, it may possibly make a difference whether you use the default JDBC driver (12.2.0.1) shipped with 17.2, or a previous driver (potentially as old as 11.2.0.3).    

    · Share on TwitterShare on Facebook
  • andre_d
    andre_d Member Posts: 4
    edited Jul 24, 2017 7:49AM

    Gary, thanks for the explanation.

    I will give changing the JDBC driver a try if I have the time.

    · Share on TwitterShare on Facebook
This discussion has been closed.