Hi,
I am using SQL Developer 18.3 and it doesn't show DBMS Output.
Database version: 12.1.0.2.0
However, if I run the same on SQL*Plus for the same schema and database, it runs fine:
Moreover, if I connect to another database also version 12.1.0.2.0 on the same SQL developer, it runs fine:
Am I missing some configuration?
Regards,
Susana
there's no configuration
does the dbms panel work?
does 18.4 work?
Thank you for your help.
No, DBMS panel doesn't show anything too:
18.4 has the same behavior.
i don't have a 12.1.0.2 db anymore but i can confirm this is working as expected in 12.2 and 18c
smoliveira wrote:
Thank you for your help.
No, DBMS panel doesn't show anything too:
18.4 has the same behavior.
Perhaps a silly question, but did you remember to click the '+' button on the Dbms Output, and specify the database for which it is to be active?
Here is an interesting test case in 3 steps, not exactly your case, but showing that we can get DBMS_OUTPUT to the Script Output tab to stop working.
My configuration is Windows 10, SQL Developer 18.4 against an 11g XE DB, Java 1.8.0_201, OCI thick connection with Oracle Instant Client 18.3:
1) Set serveroutput on, then run script (f5) on the anonymous block with the DBMS_OUTPUT statement. It works fine.
2) Next, in the View -> Dbms Output pane, open the existing SCOTT connection, and run the anonymous block again. It works, in both output tabs.
3) Finally, close the SCOTT tab in the Dbms Output tab, then run the anonymous block again. The 'Test' text does not appear in Script Output tab this time!
So something is not quite perfect here.
Cheers
Thank you for your feedback.
I tried to follow your test, but it never print nothing:
So it does not work on one specific 12.1.0.2 database, but it does on another, using the same install of SQL Developer 18.3 / 18.4. And it works on both when using a sqlplus client.
The only other things I can think of...
1) Check if the 12.1.0.2 databases are at different patch levels or have different one-off patches applied.
2) Check if the 12.1.0.2 database that DBMS_OUTPUT does not work for over a JDBC connection has any relevant warnings showing up in the server's alert log.
Good luck on researching the problem!
Thank you for your support.
1) Check if the 12.1.0.2 databases are at different patch levels or have different one-off patches applied.
The database that DBMS doesn't work has the following patches:
The other one hasn't any patches.
2) Check if the 12.1.0.2 database that DBMS_OUTPUT does not work for over a JDBC connection has any relevant warnings showing up in the server's alert log.
I don't have access to the server's logs. I tried to run through a JDBC connection and it prints fine.
