I am currently evaluating Version 6.0.2.880 of PLSQL Developer. A number of our team have a problem with debugging. It tends to hang leaving 'executing' on the message bar. I can not close down the test window because it says the script is still executing.

For the code I am running it seems to hang on the RAISE_APPLICATION_ERROR line.
We have flushed the shared_pool, resized it to 200MB and reloaded the dbms_debug packages and none of this has worked.

Please can you advise us what to do next.

Maybe this is an environment problem. Can you go to Help > About, press the 'Info' button, press the 'Copy all pages' button on this info screen, and paste this text into an e-mail reply?

We are having the same problem with both versions 6.0.2.880 and 6.0.3.893. Our Oracle DB version is 9.2.0.5.0.
An additional note: PL/SQL Developer is still functional when this happens, but CPU usage is about 30% while the Debugger is executing. When you try to Break (Shift-Esc), after about 10 seconds then CPU usage becomes 99%, and the window keeps "Executing" indefinitely.

I did some further investigating, and the issue seems to be related to Oracle RAC. When trying the same debugging action on a "single" database, debugging works OK. So in our case the temporary solution is to log on to a single node of the RAC cluster.

We don't use RAC and still have the debugger hang on a regular basis. So far just cope with it. There definitely is some relationship between the size of the package and frequency of hanging. We chop down the size of a package and the debugger is happier. Also, the load on the sever is an issue. I suspect it's some server side resource becaue I can debug large packages after hours just fine. Have not located the limiting resource yet.

Could this be another manifestation of the bug discussed in this thread:
PLSQL Developer hangs on PBSDE.DEBUG_LOOP (WAIT = pipe get).

When the debugger hangs, we get a 7445 error in the system log indicating that the real problem is with a named pipe, not the debugger itself. The Oracle debugger uses named pipes for its asynchronous communication.

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

[quote]Originally posted by Ted Struik:
I did some further investigating, and the issue seems to be related to Oracle RAC. When trying the same debugging action on a "single" database, debugging works OK. So in our case the temporary solution is to log on to a single node of the RAC cluster. [/quote]Yes, we use RAC and debugger hangs regularly. If we connect on single node the debugger works fine.