Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

I've come across an excellent article by Jeff Smith recently that describes how to enable debug mode in SQL Developer. This has been a useful source of information in my recent quest to solve some connectivity issues with certain databases, however it wasn't the final answer I was after.

Jeff's article wasn't completely useful because SQL Developer was doing this...

Every second or so the Reconnect dialog would tell me 'Your database connection has been reset. Any pending transactions or session state has been lost.' Over and over again with no chance of having a glimpse at the debug log inside SQL Developer itself.

So I got thinking that the SQL Developer debug logging looks like standard Java logging with some custom properties set so a standard FileHandler should work...and it does!

This is what I added to the end of the sqldeveloper/sqldeveloper/bin/logging-debug.conf file...


Don't forget to add 'IncludeConfFile sqldeveloper-debug.conf' to the sqldeveloper.conf file to make this work, as per Jeff's article.

Adjust the path to your log file to suit.

After doing this I could see my log file filled with messages and didn't have to try and debug these inside SQL Developer itself...
 Log Output
<message>RaptorTask: Object Selection: The connection to database MY_DATABASE is closed.</message>


Did you like this post or found it useful? Considering supporting this Blog to keep its web servers running, any amount helps! Thanks!
Have comments or feedback on what I wrote? Please share them below!
comments powered by Disqus
Other posts you may like...