I have a test window that has "crashed" because of failing to break a debug session on an 11g database. The result now is that the execution has stopped, but the green Run arrow and the red Break lightning are enabled like the debugging session was still aktive. Nothing happens whether I press the green arrow nor the red lightning.

The problem is that the test window can not be closed. I get the message: "Test Window cannot be closed, Script is still executing". If I press Terminate, nothing happens.

I am now severely limited in what I can do in PLD: no compilation, no running of new test scripts. Only option is to save all programs, selects etc. and use task manager to force PLD to end. Not a very elegant solution.

This can also happen if I run SQL scripts of test windows using a databse connected via a VPN connection and the VPN connection fails for some reason (network problems etc.)

Please make it possible to force close a test window no matter the state of the debugging session. It must always be possible to close a window and end PLD in an orderly fashion without having to use the task manager.

I have added this to the list of enhancement requests.

Thanks. Please make it a high priority, it causes great amounts of extra work and frustrations

i've experienced the same issue. i believe this works:
- click the X to close the window
- that terminates the debug session
- then Cancel the window closure

Still the probelem is persisting??
Any solution u got ??

---we are facing same issues ---Hari Developer Team

I have a similar problem, but I don't think the workaround from archer works for me. When I try to close the window, I get the "Test Window can't be closed..." box. Clicking Terminate give me the error:
Error during debug step:
ORA-03114: not connected to ORACLE
Debug session terminated.

but the debug session remains; the green arrow and the red lightning bolt are both active, and clicking them gives the same error.

Can PL/SQL Developer be modified to actually terminate the debug session when it says "Debug session terminated"? (I'm using Version 9.0.6.1665)

One other note: Right-clicking on the window in the Window List shows the "Close Window" disabled, but the "Execute" is enabled. (Choosing Execute just locks up PSD as "Initializing...")

To confirm, this is still an issue with 10.0.2

And it has been around for quite a while . . .

Debug session 'stuck' on ORA-03114 - not connected to oracle loop

This issue is still with 10.0.5. is there any plan to get it corrected? every time have to terminate the process from task management, it's very frustrating!

When I get this problem, I open another PL/SQL Developer program, open the sessions window and then kill the hung test session. That has always worked as far as I remember. It's still not elegant and it's a hassle, but I don't lose anything else this way.

This is still an issue with 11.0.0.1762. Thx for mike. In win'7 sometimes is possible to mouse right-click on taskbar, choose "close window" and next "try to restore".

The simplest workaround would be: to set run state of SQL/cmd window to "no" while not connecting to database and break button is clicked.

[quote=davqi]This issue is still with 10.0.5. is there any plan to get it corrected? every time have to terminate the process from task management, it's very frustrating![/quote]

+1

Still an issue at the latest version. Please Marco have a look at it.

I have the same problem. I cannot always close or stop a test window that doesn't answer anymore.

Please fix the problem, it's really frustrating us.

I am on 11.0.4.1774 02.15491 and test window keeps freezing at the end of the test run. Stepping through with debug.

This is a very annoying issue. Makes my productivity go way down. Is this a bug in PL/SQL Developer or in the way that we install it or in the way we install the Oracle client or ....?

Marco or someone please post a way for us to trouble shoot this. I would think with the minimal number of posts that not every user is experiencing this issue.

If found a resolution to this issue. In case someone else stumbles upon this thread. I was running the 10g oracle client with and 11g database (long story on why so no room for details here ;>). I upgrade my Oracle client to the same version as the DB and the debugger is behaving as expected.

So make sure that your Oracle Client matches the version of the DB that you are debugging on.

PL/SQL Developer
Version 11.0.6.1776
12.100110 - Unlimited user license
Service Contract: 5/1/2016
Windows 7 (64-bit) Build 7601 (Service Pack 1)

Sadly, it appears that this will never be fixed. I recently upgraded to Version 14 and just ran into the problem (again). Checking the forums, I still see my original post from 13 years ago ( Debug session 'stuck' on ORA-03114 - not connected to oracle loop ).

The problem can occur when a debugging session is left 'executing' too long, and Oracle times out the session. So, the previous workarounds (like killing the Oracle session) won't work, because Oracle has already killed the session on the database side.

I would have thought it should be a pretty 'simple' fix in PL/SQL Developer - when the user tries to close the window and receives the "Test Window cannot be closed, Script is still executing", and then clicks the Terminate button, and gets the error:
Error during debug step:
ORA-03114: not connected to ORACLE
Debug session terminated.

clear the 'flag' that indicates that the session is still executing. Since the session is already disconnected from Oracle, there is no need to be concerned about a dangling process on the Oracle side.

The only way I can see that will get out of the situation is to kill the PL/SQL Developer app in Task Manager. That is a bit drastic, but since there is no known work-around, that is the only way to solve the issue. (Trying to close the window from the Task Bar (or by clicking the X in the upper right of the application) just pops up the same "Test Window cannot be closed, Script is still executing" dialog.)

This problem should be very simple to reproduce - start a Debug session, disconnect the PC from the network, and try to do a step. Once the connection times out, the error should occur.

I'm assuming that fixing this is too low on the list of bug fixes for AA, likely because an insufficient number of people have let AA know that they have this problem. So if you do have this problem, let AA know, so it might inch up a tad on their 'bugs to fix' list.

Thanks
Juan

+1

+1

And another +1

We are working via VPN a lot and every time the connection drops and you do something like debugging you have to kill those sessions, sometimes it works, sometimes the only way out is killing PL/SQL Developer via the task manager. Can't close the window or application while debugging, can't stop debugging, can't disconnect, can't do anything. Handling connection errors during compares could be improved too.

+1

+1 Have had this issue forever with PL/SQL Developer. It is a great tool but the one feature that I like the best gives me the most trouble and that is a hung debug window (for any reason). Will highly appreciate if this is fixed.

+1 I have the same problem

Currently using PL/SQL Developer V13, and the issue still exists.
Is there a fix for this, and if not maybe some explanation?
Is it necessary for the connected user to have ALTER SESSION privilege? because this is required to use the workaround to open another PL/SQL Developer instance and kill the rogue test session.

Most annoying bug occurring on a daily basis to date, which should be solvable even in a suboptimal manner, regardless if it's related to some obscure oci driver bug.

+1

+1

+1

So irritating... SQL Developer doesn't seem to suffer from this.

+1

It is possible to kill the session(s) on the database server in order to be able to interact with the program again. However, debugging is no longer possible until plsd is restarted (debug = run).