Trace file - Probe:S:debug_loop: timeout.

marc.wilson

Member²
When using the debugger in PLSDev to debug packages, we are getting trace files in the udump dir on the server with the follwing message:

*** 2003-12-10 16:21:59.819
*** SESSION ID:(100.22101) 2003-12-10 16:21:59.791
Probe:read_pipe: receive failed, status 3
Probe:S:debug_loop: timeout. Action 1

More than once the Oracle session could be killed via oracle and had to be terminated via the OS w/ kill .

Additional symptoms included:
1. The package that was being debugged is locked and cannot be recompiled via another session.
2. Checking "Allow compilation while debugging" on "Tools->Preferrences->Program Window" does not consistently remedy the package locking symptom. (the hung debug session may have something to do with it)
3. The table that was being accessed from within the package being debugged will have often have an exclusive lock on it that is not freed until the process is terminated.

A side affect seems to be that PLSQLDev seems to hang if any attempt to recompile the package or truncate and/or drop an exclusively locked table via the Object Browser. (i.e. PLSDev does not seem to timeout)
If there is somewhere to set the timeout value, I have missed it.

We are on Oracle 8.1.7.0.0.

There does not seem to be much info on the Internet for "Probe:S:debug_loop: timeout."

Any help would be greatly appreciated...

thank you,
--marc
 
This version should be okay. Perhaps you can try the following:

1. Reload the dbms_debug packages.

As a result of previous dbms upgrades, the dbms_debug packages can cause problems. You can logon to the server computer, go to $ORACLE_HOME/rdbms/admin, start SQL*Plus under the SYS account, and run pbload.sql. This will reload the dbms_debug packages. Check if this has a positive influence on the problem.

2. Increase the shared pool size.

The debugger requires some extra memory, so it may be necessary to increase the shared pool size.
 
Back
Top