Oracle Sql Developer Closed Connection Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn sql developer connection timeout setting more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags
Sql Developer Keep Alive
Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like sql developer closes automatically you, helping each other. Join them; it only takes a minute: Sign up How can I keep Oracle SQL Developer from closing the DB connection? up vote 28 down vote favorite 5 Is there any way to keep sql developer disconnects frequently Oracle SQL Developer from closing my DB connections, or to increase the timeout? Sometimes during a long-running query SQL Dev will just close the connection, leaving my query running on the server but me with no results. If I RDP into the server and run SQL Dev locally it never seems to have this problem. oracle oracle10g oracle-sqldeveloper share|improve this question asked Aug 20 '09 at 22:48 Kevin Babcock 5,820145176 Related question with solution
Sql Developer Session Timeout
for SQL Developer 4: stackoverflow.com/questions/12999811/… –Vadzim Feb 23 '15 at 10:41 add a comment| 6 Answers 6 active oldest votes up vote 7 down vote accepted This doesn't sound like an issue with SQL developer, cetainly I've never come across it. Are you sure it's not something else, like your network? What happens if you connect from SQL plus from your desktop. share|improve this answer answered Aug 21 '09 at 4:49 Matthew Watson 9,43864675 Kind of late in marking this answer, but yes it was a network issue. –Kevin Babcock Mar 2 '11 at 1:57 add a comment| up vote 23 down vote I don't have the answer for this, but I'm experiencing the same problem. The firewall between my SQL Developer and the database automaticly closes "inactive" sessions. A long running query is according to the firewall an inactive session, so he closes it. I've not, yet, found how to make SQL Developer send packets over a connection with a long running query, so that the firewall doesn't close the connection. And I don't know if this is possible at all. So I don't think it is a SQL Developer problem, but a firewall issue. -- UPDATE There is an extension for SQL Developer that allows you to keep the connections active: http://sites.google.com/site/keepaliveext/ It's not totally finished yet (for example the notificat
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message sql developer reconnect automatically and try again. More discussions in SQL Developer All PlacesDatabaseDatabase Application DevelopmentSQL Developer This connection is currently busy try again oracle sql developer discussion is archived 3 Replies Latest reply on Mar 5, 2016 8:09 AM by Jeff Kemp SQL Developer 4.1.3 fails to reconnect
Oracle Sql Developer Reconnect Session
Jeff Kemp Jan 2, 2016 12:47 AM I can only reproduce this if I use the "Run Statement (F5)" function in a SQL Worksheet that is not assigned to any session. This problem only appeared after I http://stackoverflow.com/questions/1309254/how-can-i-keep-oracle-sql-developer-from-closing-the-db-connection upgraded from 4.0.3 to 4.1.3. I frequently work at a location where the network connection is flaky and gets reset every now and then. Previously, I could just disconnect and reconnect, but this bug now requires me to close SQL Developer down completely in order to reconnect.1. Open SQL Developer, connect to a session, do some work.2. Interrupt the connection (e.g. pull network cable, then plug in again).3. Disconnect SQL session.4. Open a SQL https://community.oracle.com/thread/3881596 Worksheet with a SQL query.5. Click Run Statement (F5). "Select Connection" pops up.6. Choose a connection using SSH tunnel.Error encountered "IO Error: The Network Adapter could not establish the connection; Vendor code 17002"7. Try opening any session using the Connections window.Expected: succeeds on 2nd attempt (this is what I used to experience with v4.0.3)Actual: IO Error persists.Workaround: close and re-open SQL Developer.SQL Developer Version 4.1.3.20 with JREBuild MAIN-20.78Windows 8.1 64-bit I have the same question Show 0 Likes(0) 1348Views Tags: none (add) sqldeveloper 4.1.3Content tagged with sqldeveloper 4.1.3 This content has been marked as final. Show 3 replies 1. Re: SQL Developer 4.1.3 fails to reconnect Jeff Smith Sqldev Pm-Oracle Jan 2, 2016 8:18 PM (in response to Jeff Kemp) That's a bug.No need to restart SQLDev though.VIew > Tunnels.Pick your tunnel, re-open it.Then you can connect.The bug fix will have a reconnect check the status of the tunnel so that's not necessary. Like Show 1 Likes(1) Actions 2. Re: SQL Developer 4.1.3 fails to reconnect user10421280 Jan 15, 2016 11:15 PM (in response to Jeff Smith Sqldev Pm-Oracle) I'm not trying to divert this thread, but it brought up a related question for me that I think about often. What are the proper steps for reconnecting to a database once the connection is lost? I generally have
minding your own business, doing your work, and you click in your favorite Oracle Database IDE. Do you get what you asked for? No! Instead, you are rewarded for your troubles with this puzzling and frustrating message. What the heck?!? http://www.thatjeffsmith.com/archive/2013/09/oracle-sql-developer-and-the-dreaded-connection-busy-message/ Abort? Try again? Busy? The Long Answer When you connect to a database in SQL Developer you are actually making two connections. We use one connection to run background queries in the the worksheet. This makes the code assist features work. The other connection is used to do EVERYTHING else. The only exception is when you open an UNSHARED worksheet. It's called ‘unshared' because we open another dedicated connection just for that worksheet. sql developer So, if you see this message in SQL Developer, it means your request has timed out while waiting for the main connection to become available. For example: when you ask to see a table's data in a table editor, we first ask to lock the JDBC connection so we can run our ‘SELECT * FROM…' query. If the JDBC comes back and says, sorry we're busy, we try again. We give up after a oracle sql developer certain amount of time and give you the error message. At that point you get to: Try again - ask for the lock to run the query again Abort - give up Now, I realize this explanation has only given you more questions to ask, so let's go through those now. But I'm not doing anything, how could the connection be busy What's probably happening is the columns page query is still technically executing when you go to click on the ‘Data' page in a view or table editor. Or, something you're doing somewhere else in the tool is still using the main connection. Still don't think you're doing anything? Do you have any reports (or Monitor Sessions) on auto-refresh? Or maybe you've gotten cute and installed/created a ‘keep alive' extension to thwart connection-idle disconnects? Oh yeah… In earlier versions of SQL Developer you might run into this error more frequently because of poor session management - that's on us. But in version 4, you should VERY rarely see this message. In fact I've been spending the entire morning trying to get this message to pop-up and I failed. Even if I click ‘Abort' the data comes back anyway?!? The dance of the ‘are you busy' and the ‘yes we are' is colliding with the timeout perfectly just