Exception when interrupting Testscript Debugging

zakko

Member³
I've got either a ORA-00603 or ORA-00604 when interrupting a testscript during debbuging. The exact steps to reproduce are as follows:

1. Run a Testscript, that is calling a DB procedure in Debug mode (F9) - that's at least what my script does. I can't tell whether this is mandatory for reproduction.
2. Stop script/debugging along the way during execution (Shift+Esc)
3. Run the same script again in Debug mode
The script doesn't enter Debug mode and continuously says "Executing...". It throws an exception after stoping its execution (Shift+Esc). I have seen ORA-00603 or ORA-00604 here.

Expected behavior would be, that the Testscript runs smoothly even in Debug mode for each execution - no matter, whether it was interrupted or not. As it runs ok the first time, I assume, that it's not the code of the script but Developer itself, that causes a problem here (let me know, if my assumption is wrong).

This occured with PL/SQL Developer Version 14.0.5.1986 (64 bit) on a fully patched Windows 10 Build 19041.
 
I tried the following:

  • Create a debug test procedure and compile it
  • Right-click on it and select "Test"
  • Press F9 to start the debugger
  • Step into the debug test procedure
  • Press Shift-Esc to break execution
  • An "ORA-06543: PL/SQL Developer: execution error - execution error" message is displayed
  • Press F9 again to start the debugger
  • The debugger starts again as expected
Can you verify that this matches the steps you took? Can you also let me know your Oracle Server version?
 
That's not exactly what happens on my machine. I first wrote an explicit test script with a call of the function under test, which is wrapped by a dbms_output.put_line call to see the returning string. The use case is completely driven from a test window.

The first "interruption" of the debugging-flow works smooth without any exception popup. The second try doesn't even start correctly, i.e. not entering debugging mode at all (e.g. iconbar for jumping into functions etc. stays grayed out) and after doing the Shift+Esc (klicking the red flash icon) to escape this "hang", I get the ORA-00603 or ORA-00604 on different attempts.

I'm running this on a Oracle 11g Release 11.2.0.4.0 (64bit).
 
Last edited:
I found another odd detail:

When I open PL/SQL Developer and start debugging of the testscript right away, it doesn't even start properly at the first attempt, showing the faulty behavior described in my last post.

The first debugging run only starts fine, if I initially compile the package that holds the function under test, even though it has already been compiled before and is available in the DB.
 
Last edited:
Ok, this was completely a user error - my bad. Actually this post could be deleted entirely, because it appeared to be not applicable at all.
 
Back
Top