Fixing SQL Developer 4.0

Back when I was going through installing my programming/editor related tools, I had installed SQL Developer, but it wouldn’t work for me.  Well, time to revisit!  I have it working now!

SQL Developer 4.0

Just to recap, I had installed SQL Developer using the sqldeveloper-package tool.  I downloaded the Windows 32/64-bit zip file from Oracle’s SQL Developer Download Page.  In a nutshell, here’s the commands for installing:

[sourcecode]sudo apt-get install sqldeveloper-package
make-sqldeveloper-package -b output \
sqldeveloper-4.0.0.13.80-no-jre.zip
sudo dpkg -i sqldeveloper_4.0.0.13.80+0.2.4-1_all.deb[/sourcecode]

You can read my notes near the end of this post.

Now, when I launched it, it opened a new window, and I could see the splash screen while it attempted to load.  Before it could finish, it would crash.  I found a crash report in the /tmp directory.  It starts with:

[sourcecode]#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f1600476320, pid=14041, tid=139732527163136
#
# JRE version: Java(TM) SE Runtime Environment (7.0_51-b13) (build 1.7.0_51-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.51-b03 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C 0x00007f1600476320
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#

————— T H R E A D —————

Current thread is native thread

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x00007f1600476320[/sourcecode]

Thanks to Adrian’s comment on Jeff Smith’s blog, I found that I could fix it by unsetting some environment variables.  So, here’s what I did.  I edited the launcher script that was installed…

[sourcecode]sudo  gedit /usr/bin/sqldeveloper[/sourcecode]

Then, I added the following 2 lines at the top:

[sourcecode]unset GNOME_DESKTOP_SESSION_ID
unset DBUS_SESSION_BUS_ADDRESS[/sourcecode]

Editing the SQL Developer Launcher

After making that change and saving it, SQL Developer launched with no problem.

SQL Developer About Screen

Resources

that JEFF SMITH: Oracle SQL Developer 4.0 Is Finally Here

10 thoughts on “Fixing SQL Developer 4.0

  1. works for sql developer 4.0.2.15.21 too!

    I added your two unset lines to my ~/sqldeveloper-4.0.2.15.21/sqldeveloper.sh:

    #!/bin/bash
    unset GNOME_DESKTOP_SESSION_ID
    unset DBUS_SESSION_BUS_ADDRESS
    cd “`dirname $0`”/sqldeveloper/bin && bash sqldeveloper $*

Leave a Comment

Your email address will not be published. Required fields are marked *