Migrated to 10.2 eratic behaviour

tonyg

Member
Hi,

I have used the pl/sql developer tool for a number of years, mostly against oracle 10.1.

Having recently moved to a RAC 10.2 environmnet, I find that the debugging seems to be a little eratic.

This morning I want to run and debug a procedure, and I go through the usual process of switching the procedure to be compiled in debug mode, I then right click on TEST and enter the procedure parameters into the lower pane.

When I click on the start debugger button, instead of opening the debug window and putting me onto the first executable line, it just goes straight into execute mode, and doesn't make any of the line step buttons active.

I can hit the break button and it the comes out of execute mode, but if I try again I get the same result.

If I close and restart the tool again, I get the same result.

I am on version 10.0.0.1050, any help would be greatly appreciated.

regards
Tony
 
Perhaps the program needs to be compiled with debug information first? To verify this, right-clock on the program unit and select "Add debug information" and retry the debugger.
 
From first post "I go through the usual process of switching the procedure to be compiled in debug mode"

Yep, did that.
 
Hi Marco,

I am connect not as sys, but as the schema owner of the object to be tested/debugged.

thanks
Tony
 
No thoughts or comments then?

We've used you tool for the last couple of years with great success, but are having problems on our new RAC environemnt.
 
No immediate ideas yet. To obtain some more diagnostic information, can you modify the shortcut and add the debugsql parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" debugsql

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory.
 
Back
Top