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!
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:
sudo apt-get install sqldeveloper-package make-sqldeveloper-package -b output \ sqldeveloper-220.127.116.11.80-no-jre.zip sudo dpkg -i sqldeveloper_18.104.22.168.80+0.2.4-1_all.deb
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:
# # 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
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…
sudo gedit /usr/bin/sqldeveloper
Then, I added the following 2 lines at the top:
unset GNOME_DESKTOP_SESSION_ID unset DBUS_SESSION_BUS_ADDRESS
After making that change and saving it, SQL Developer launched with no problem.