Let’s say you have a database and you want to encrypt the SQL*Net (or jdbc) traffic from the db server to the client (e.g. Alas, it’s not just my eyes that are getting old. It’s embarrassing how often that happens.
This time, though, I’m blogging about it, including the error message, so that next year when I Google the error message, I’ll find my own blog post. Like I said, when you don’t do something frequently, you forget the details. Each time I went through the same issues and errors. Worked it out again 18 months ago using SQL Developer.
ORACLE SQL DEVELOPER UBUNTU 14.04 HOW TO
I worked out how to do it years ago (using SSH without the assistance of SQL Developer). I didn’t set up my SSH tunnel in SQL Developer correctly. I’ll spare you most of the trials I attempted working through the different upgrades and provide the spoiler: it was operator error. It allows you to encrypt SQL*Net (or any other kind of traffic) between your laptop and database (or other) server. All went well until I tried to set up the connections that require an SSH tunnel. SSH Tunnel ConnectionsĪfter increasing the SQL Dev font size (my eyes aren’t what they used to be) I endeavored to recreate my connections. I don’t do a SQL Dev upgrade that often, so I forgot that it would overwrite everything. Sadly, this isn’t the first time I’ve done this. The challenge started when I realized that by “upgrading” SQL Developer on my Mac, I actually overwrote the previous install, thereby deleting all of my connections and preferences. Naturally, I updated to the latest JDK, which is higher than SQL Dev 18.1 supports, but hey, why not?Īny time you change more than one thing, troubleshooting becomes complicated. I recently did multiple upgrades on my Mac: the O/S to High Sierra, SQL Developer to 18.1, and then the JDK to bring it up to a level that SQL Dev requires.
0 kommentar(er)
