This odd behavior seems to be confirmed by running the following query as sysdba: I found out that when using SQL Developer, it's more likely to happen, even though in a bunch of cases the closing statement worked, apparently a few minutes after the COMMIT, on the contrary, SQL*Plus never failed a shot. It means it's time to ask what type of client you are issuing the SQL statements from. However if, after issuing either of the above, you are still getting the dreaded error message: I also tried with ROLLBACK FORCE to no avail. The theory says that in order to explicitly close a database link connection, you must perform either of the following:ĬOMMIT - or ROLLBACK ALTER SESSION CLOSE DATABASE LINK test_link ĬOMMIT - or ROLLBACK begin dbms_session.close_database_link('TEST_LINK') end Yet another web article about ORA-02080? Hopefully not.Īfter reading several entries on this error and its remedies, including Tom Kyte's entry, I realized that the suggested cure is not always working, at least not on Oracle XE 10gR2 (at the moment I can't say on other versions, may be you can contribute on this). One of these approaches usually resolves the issue.Always check out the original article at for latest comments, fixes and updates. If not, doing (2A) may be convenient if you prefer to import connections rather than re-enter them manually. If you decide to go with (3), you can either migrate settings from an earlier SQL Developer install or not.
Launch SQL Developer and import your connections. On Windows 7 for SQL Developer 3.0.04.34, for example, it can be found at:Ĭ:\Users\\AppData\Roaming\SQL Developer\system3.0.04.34D. Either delete or rename the system directory. Back-up the connections by right-clicking on the Connections node, select Export Connections., then follow the Export dialog.Ĭ. Rather than (2), alternately you could download the latest SQL Developer (3.2.09.30), unzip it into an empty directory, and start it up.Ī.
Try restarting SQL Developer after removing its system directory (but only after first backing up your connection information!).ģ. Using the latest jdk1.6.0_xx update is recommended.Ģ. Make sure you are not pointing to a Java 7 jdk in your nf file. You may want to try out the most common fixes:ġ. You have described a variation on theme that can be found in many posts on this forum.
0 kommentar(er)
