Skip to Main Content

SQL Developer

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

SQL Developer 17.2 doesn't show DBMS Output

andre_dJul 12 2017 — edited Jul 24 2017

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é

This post has been answered by Gary Graham-Oracle on Jul 18 2017
Jump to Answer

Comments

top.gun

OMG - where do I start!

If you are using Oracle for commercial purposes then you or your client needs a licence from Oracle. So really you should stop now.

Once you have your licence from Oracle, you can do a simulated import (ie show metadata) like this:

imp ar/live show=y statistics=none buffer=100000 feedback=100000 log=/gers/live/tmp/CUST_190312.log file=/gers/live/tmp/CUST_190312.dmp

Then if the above works you can do the real import (ie metadata and data) like this:

imp ar/live full=y statistics=none buffer=100000 feedback=100000 log=/gers/live/tmp/CUST_190312.log file=/gers/live/tmp/CUST_190312.dmp

Dean Gagne-Oracle

You can always use

imp help=y

to give you the available commands and options.  If you only want the data, then you can use:

imp user/password file=your_file.dmp rows=y

Hope this helps.

Dean

Lisa-Oracle

Hi AJVinkles,

You need to add ignore=y since the table pre-exists

Using IGNORE=y instructs Oracle to ignore any creation errors during the import

and permit the import to complete.

imp user/password file=  log= FROMUSER= TABLES=  ignore=y

rows=y as stated above is the default so it is not needed in the command

Regards,

Lisa

1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Aug 21 2017
Added on Jul 12 2017
10 comments
15,993 views