I am getting the following error whenever I login to sql developer.
SEVERE 56 0 oracle.jdbc Error while registering Oracle JDBC Diagnosability MBean.
I get below error whenever I execute any query.
SEVERE 70 53918 oracle.dbtools.worksheet.sqlhistory.SqlHistoryTask oracle.dbtools.worksheet.sqlhistory.db.HistoryDB.readHistory(HistoryDB.java:99)
I use following versions
Java(TM) Platform 1.6.0_35
Oracle IDE 3.2.20.09.87
Versioning Support 3.2.20.09.87
I am working on Oracle11gR2.
Please help me to resolve this and let me know if you need more information.
Sounds like your sql history file is corrupt. Shut down SQL Developer. Find the SQL History directory file in your settings, rename it, and restart SQL Developer. That should get you back going.
If on windows, you'll find it somewhere near here
Edited by: Jeff Smith SQLDev PM on Jan 10, 2013 9:40 AM
What is the name of the file?
In my following directory, I am finding files like -106279910931224002history.xml -127801141215972537history.xml. There are so many files, around 334. Which one should I rename?
C:\Documents and Settings\sbutta\Application Data\SQL Developer\SqlHistory
cut all history.xml files and paste them to another folder as a precautionary purpose.
Also check that you tns listener started or not
you can check it by giving command tnsping your_tns_listner_name ie your connect string. if it is not running then
start the service and try again by opening the sql developer
if still problem exists then delete your sql developer folder in
C:\Documents and Settings\sbutta\Application Data\SQL Developer\
of your user profile and run sql developer again if this post helpful or correct please mark it . this will be beneficial for others like you and people will have interest in answering questions.
Edited by: Askdineshsinghminhas on Jan 10, 2013 7:09 AM
renaming the directory has the same effect, once it works, you can try moving your files back over, although it's likely one or more of them are problematic or corrupted...
Not sure what checking the listener does in this use case, the user is already connected to their database.