pl/sql developer hang

[swakoo]

my pl/sql developer hangs whenever i tried to step in the code..
any one know the reason?
is it because my code is too long?
my code are 3000+ line only..
thanks

 

[Makker]

Is it in the debugger (think it is, since you talk about stepping into code).
I experience it sometimes too, especially when debugging code called by triggers, over db-links or using dynamic sql. But sometimes I cannot explain it. But it helps me when I add the line:
i:=dbms_debug.set_timeout(timeout => 60);
as the first line in my script. I added it also to my template (with a question what the timeout should be). I also asked allround automations if this could be added to the default test template.

Success,
Martien

 

[swakoo]

i think i got the ans to it..
i tried remove some of the code with i dun need for testing the part which i wanted to test and make it 2996 line. and it works perfectly with the step in..
and next i added afew line to make it 3003 line. this time round it hangs..
haha..

 

[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