NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ
for more details.
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
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
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
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...