3

I am experiencing something strange while using Oracle SQL Developer 4.0.1.14.

When I connect to a particular db and run a simple select * from table1; I get the result set. (Still happens regardless of the number of records in the table, which is few, however the table does contain over 170 fields)

If I try and run it a second time I get a java heap space error.

enter image description here

If I try and run it again it starts throwing Protocol violation errors, with a different numbered protocol error each successive run.

enter image description here

enter image description here

I have never experienced this problem with other oracle db’s, even when connecting through the same installation of SQL Developer.

The only way for me to be able to query that table again is to reconnect to the db. Other users of this same db do not experience this problem. Has anyone ever experienced this issue?

Improve this question
3
  • 4
    Consider not using UPPERCASE ONLY for your titles; as UPPERCASE translates to SCREAMING for many folks using the interwebs. Commented Mar 30, 2016 at 14:11
  • 1
    Does the problem go away if you increase the JVM memory allocation? Commented Mar 30, 2016 at 14:18
  • Yes that fixed it. Thank you very much. Commented Mar 30, 2016 at 18:40

3 Answers 3

Reset to default
7

you can edit sqldeveloper.conf and change the size of the heap space, by adding the following line:

 AddVMOption -Xmx4096M
Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

Here is the full path C:\Users\{username}\AppData\Roaming\sqldeveloper\19.2.1\product.conf
i was trying to import data from .xlsx file with 1M rows to a table and i'm getting error: java heap space, after adding this line, error still occurs
2

I know it is too late may be that could help someone else

in the explorer enter %appdata%

that will bring you to your : 

C:\Users\username\AppData\Roaming\

Find your sql developer in my case it was:

sqldeveloper

Find a file named: product.conf

Almost at the end of the file change the line:

AddVMOption -Xmx800m

into :

AddVMOption -Xmx2048m
Improve this answer

Comments

0

In my case I increased the heap size in "sqldeveloper.conf" to be 3072M --> 3GB but this didn't fix the issue.

AddVMOption -Xms1024M
AddVMOption -Xmx3072M

I found that there was another worksheet with different structure in the xlsx file I was trying to import. After deleting that extra unneeded worksheet I could import successfully. I was using MAC machine.
Final note: converting the excel file to csv and importing the later one was much faster than importing the excel file for the same data.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.