Debugger hangs

[Ilia Vinikovetsky]

Starting from version 6.0 I experience a strange behavior of PL/SQL Developer: it hangs when starting debugger.
This never happens on the first "Start debugger" in the session. But already second start frequently hangs and let's say fourth start almost never could be completed.
Is there some PL/SQL Developer setting that I missed and which could cause such behavior?
Thank you in advance

 

[Ivan C.]

Ilia,

We've been having the same problem in Oracle 9i databases. We fix them by increasing the shared pool size (usually doubling it).

 

[Ilia Vinikovetsky]

Ivan,

Thank you for your feedback. I'll try to implement your recommendation. Although we keep shared pool doubled in comparison with its default value. But anyway I'll use this option. Thank you very much once more.

 

[Marco Kalter]

Can you let me know your exact PL/SQL Developer version (Help > About)?

 

[Eggie]

I always use the following piece of code to prevent the debugger from hanging:

i binary_integer;
i := dbms_debug.set_timeout(timeout => 60);

put it at the start of the procedure/function to debug.

 

[Ilia Vinikovetsky]

Currently I run PL/SQL Developer version 6.0.3.893, but if I am not wrong these hangs started from version 6.0
I also wil test the timeout setting.
Thank you very much.

 

[minervino]

Try this sql:

select trigger_name from dba_triggers where TRIGGERING_EVENT = ('ERROR')

If you have a trigger with TRIGGERING_EVENT = 'ERROR', is big the possibility of hang. Try disable it and do a test..

If this don't work, see if you have any of this types of trigger too:

'LOGON',
'CREATE OR ALTER',
'CREATE',
'ALTER',
'ALTER OR RENAME',
'LOGON',
'LOGOFF',
'TRUNCATE'

select trigger_name from dba_triggers where TRIGGERING_EVENT in ('LOGON','CREATE OR ALTER','CREATE','ALTER','ALTER OR RENAME','LOGON','LOGOFF','TRUNCATE')

Try disable it too and repeat the test..

Good lucky

 

[minervino]

Try this sql (correct now):

select trigger_name from dba_triggers where TRIM(TRIGGERING_EVENT) = ('ERROR')

If you have a trigger with TRIGGERING_EVENT = 'ERROR', is big the possibility of hang. Try disable it and do a test..

If this don't work, see if you have any of this types of trigger too:

'LOGON',
'CREATE OR ALTER',
'CREATE',
'ALTER',
'ALTER OR RENAME',
'LOGON',
'LOGOFF',
'TRUNCATE'

select trigger_name from dba_triggers where TRIM(TRIGGERING_EVENT) in ('LOGON','CREATE OR ALTER','CREATE','ALTER','ALTER OR RENAME','LOGON','LOGOFF','TRUNCATE')

Try disable it too and repeat the test..

Good lucky