Break button is not working.

D

Dragonba

Member
Hi all,

I have problem with PL/SQL Developer. Break button is not working for me. Icon is active (red), but after executing some query and click on the button, nothing happened. Also query never stop and PL/SQL Developer crash after some time. All queries are working on coleague computer with same preferences and break button is working for him too. Any ideas what to do with this?
 
Can you go to Preferences > Oracle / Connection and check how the "Session Mode" option is set? If it is set to "Single Session", can you change it to "Dual Session" or "Multi Session", restart PL/SQL Developer, and try again?
 
I am having the same issue on PL/SQL Developer 14 w/ Oracle 19c (19.3) client connecting to a 12c database (12.2). I am able to kill the session from another window and then I get a TNS bad packet error. I am using multi-session mode.
 
To obtain some more diagnostic information, can you modify the PL/SQL Developer shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer 14\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the %APPDATA%\PLSQL Developer 14 directory (e.g. C:\Users\\AppData\Roaming\PLSQL Developer 14).

 
Thanks. In the log file I can see that the break is sent, and that there is no subsequent "ORA-01013: user requested cancel of current operation" exception, which one would expect. Not all operations allow a break though.

As a test, can you run the following script in a SQL Window or Test Window and try to break it?

Code: 
begin
  dbms_lock.sleep(seconds => 60);
end;

This procedure will "sleep" for 60 seconds, and you should be able to break it instantaneously.

Let me know how this turns out.
 
It behaves the same as trying to kill a query and hangs. I am 22 minutes into it "running"; eventually the connection will time out and die.
 
Last edited:
Some other observations:

If I am in an SQL window and hit break, nothing happens and the query runs forever (or until the connection idles and dies). If I try to close the tab I get a prompt something is running and am offered a Terminate button. Clicking that button hangs the entire application.

If I am in a TEST window and hit break it behaves the same as the SQL window. If I try to close the tab I get the same prompt as the SQL window except it DOES actually terminate the PL/SQL block.

Hopefully this adds some insight.
 
Last edited:
Maybe this is an environment problem. Can you start PL/SQL Developer, connect to this database, go to Help > Support Info and send me the text from the "Info" tab page?
 
I see that you are using a 64 bit Oracle19 client. We have one more problem report like this for this exact client configuration. Even though we have not been able to reproduce this issue, the customer was able to resolve this by using the 32 bit version of PL/SQL Developer and a 32 bit Oracle Client.

As a test, can you download the 32 bit version of PL/SQL Developer and check if this resolved the issue for you too?

 
At the moment I can only suggest that you try a previous Oracle Client version. Can you try this with an Oracle12 Client?
 
Hey.
99% of times I try to break execution it is not working since we installed version 14.02.1969. Maybe something changed recently? Before it was +/- fine.

EDIT: Ok, 99% of times is a little bit too harsh, but the bottom line is - lately something has changed to worse with this. Idk, looked through latest update changelog, couldn't find anything related.
 
Last edited:
If/when break does not work for me and I don't want to wait, I open another PL/SQL Developer. Then I use the sessions tool to kill the session.
 
Got another complaint from a co-worker that the cancel SQL is no working anymore.
We're using version 14.0.3.1981.
Killing sessions is not an option because there are databases where I don't have ALTER SYSTEM priviliges.
We can try closing the SQL window and PLSQL developer offers a button "Terminate". But when I press that, plsqldev becomes not responding and the only option is to kill it.
 
Just got another complaint from a co-worker that lately Break is not working. Yes, we are using the same plsql dev version and same databases but still. Is there any way we could diagnose the prolem?
 
I'll jump into this conversation. I'm using PSD 14.0.4.1985. The About window says
OCI: version 12.1
DLL: c:\Oracle\instantclient_19_8\oci.dll
and I'm connected to an 11.2.0.4 DB
I'm using the 64 bit version of Instant Client
I have a query running and shortly after starting it, I clicked the red lightening bolt to break it and nothing happened. I've clicked it multiple times and nothing, also tried Session -> Break from the menu as well and nothing. PSD is still responsive, but the query continues to run. My Session Mode is "Multi session"

I used a Test window for the dbms_lock.sleep(seconds => 60); run against at 12.1 DB and it did not stop it. In fact, the Test window is still Executing.... and the time is up over 4 minutes now.

If I try to close the running tab and click Terminate, then that locks up PSD (which is probably to be expected).

I've successfully used Session Break before on prior versions of PSD against these two DBs when I was using the Instant Client 12.1. Is this a change in how Instant Client itself it working?
 
I re-pointed PSD back to the instantclient_12_1 I still had on my machine and ran the dbms_lock.sleep(20); test against the 12.1 DB. At 8 seconds, I pressed the red icon to break the session. At the 15 second mark, I I had the pop-up window appear that stated
ORA-01013: user requested cancel of current operation
ORA-06512: at "SYS.DBMS_LOCK", line 205
ORA-06512: at line 7

View program sources of error stack?

So it looks like PSD works correctly with Instant Client 12.1 for doing breaks, but not with Instant Client 19.8
 
I faced that problem recently. I put the line "DISABLE_OOB=on" in sqlnet.ora to overcome it. Don't ask me what Oracle changed and where it's documented: I don't know.
 
If you have MetaLink access, DISABLE_OOB is defined in Doc ID 373475.1 - What is DISABLE_OOB (Out Of Band Break)?

The short answer is it simply changes how the break is sent from client to server whether it is sent using urgent data provided by the underlying protocol. So it could be Oracle tweaked that underlying protocol handling in Instant Client 19c, but just a guess.
 
Yes, in my case the problem was - I was using Oracle client 19c against older (11g) databases.
Switching back to client version 12 helped.
Thanks guys for the hint!
 
You must log in or register to reply here.

Similar threads

R
  • Discussion Discussion
No query results after changing connection, and break button doesn't work
Replies
3
Views
1K
Marco Kalter
Marco Kalter
L
  • Discussion Discussion
Problem with Test Window when session is killed
Replies
4
Views
1K
Scovron
S
A
  • Discussion Discussion
Recall statement
Replies
1
Views
660
fabrice
F
S
  • Discussion Discussion
Problem with program
Replies
1
Views
353
Marco Kalter
Marco Kalter
Z
  • Discussion Discussion
Right/Left Arrow keys and Caret Behavior on Windows
Replies
3
Views
465
zitot
Z
Back
Top