Debugger hang on Oracle RAC

[dariociacci]

Hi,
I have some problems while trying to debug a packaged procedure on Oracle (9.2.0.8 & 10.2.0.3 RAC).
The debugger stops after the first step and then it hangs.
The trace file of my debug session on (9.2.0.8) reports the following lines:
......
31/01/2008 15:58:15 TOracleQuery TestForm.TestQuery End
Result = ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 157000 bytes of shared memory ("shared pool","HL7LABPROCS","pl/sql source","pl/sql source")
Duration = 14.719
31/01/2008 15:58:15 FinalizeTargetSession starts
31/01/2008 15:58:15 TOracleQuery $022036C0 Start Query.Execute
SQL = select 'x' from dual
31/01/2008 15:58:15 TOracleQuery $022036C0 End (1 record processed)
Duration = 0.234
31/01/2008 15:58:15 TOracleQuery Debugger.FinalizeTargetQuery Start Query.Execute
SQL = begin
sys.dbms_debug.default_timeout := 3600;
sys.dbms_debug.debug_off;
end;
31/01/2008 15:58:15 TOracleQuery Debugger.FinalizeTargetQuery End
Duration = 0.11
31/01/2008 15:58:15 FinalizeTargetSession ends
31/01/2008 15:58:15 TSQLThread SQLThread Suspend
...

ORA-04031 occurs despite more than 100MB of shared pool available as shown in v$sgastat.

In the other case (10.2.0.3 RAC Environment) the hang occurs whithout error messages in the trace file.

My PL/SQL Developer version is 6.0.6.947.

Do you have some ideas??

Thanks,

Dario.

 

[Marco Kalter]

Can you go to Tools > Preferences > Oracle / Debugger, disable the "Update call stack after each step" option, and try again?

 

[dariociacci]

Hi Marco,
thanks for your suggestion.
I've already tried this and the behavior does not change.
It seems this happen only in RAC environment, in all other site with NON RAC database all works well.

Regards,
Dario.

 

[Simon Bridgnell]

Hi,

I'm experiencing the same problem on a 10.2.0.1 database with PLSQL Developer Version 7.1.3.1381.

I am permitted to occasionally debug a function/procedure, but more times then not will hang.

I've also tried Marco's suggestion - this did not appear to work.

However, if I connect to the instance rather then the database then the debugging option works all the time, every time.

Not sure what the solution to this is, but the short-term work-around is to connect to an instance. If there is a known fix, please let me know.

Regards,
Simon

 

[ucdba]

If you log on to only one instance of the RAC database the debug session will not hang. I think the problem is that the debug session logs on to a different instance.

 

[rayma1]

Hi,

Same problem I am experiencing. Any solution from the creator?

Regards,

 

[Marco Kalter]

We're looking into a solution to force the debugger to use a specific instance.