Debugging problem

[mpl1604]

We have often some problems with the debugger.
If we debug a procedure so we have often the probelm that the debugger hang up!!! We have to kill the debugger!

Extract from the error-logfile from oracle 9i generated after this kill:

*** 2006-10-04 10:06:10.439
*** SESSION ID12.19583) 2006-10-04 10:06:10.193
Exception signal: 10 (SIGBUS), code: 0 (unknown code), addr: 0x0000000000000000, PC: [0x40000000015265ac, memset()+92]

*** 2006-10-04 10:06:10.511

ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [memset()+92] [SIGBUS] [unknown code] [0x000000000] [] []

Current SQL statement for this session:
declare ret binary_integer; begin ret := PBSDE.DEBUG_LOOP; end;
----- PL/SQL Call Stack -----
object line object
handle number name
c0000000c7bc2538 769 package body SYS.PBREAK
c0000000c6e485d8 328 package body SYS.PBSDE
c0000000c6e485d8 745 package body SYS.PBSDE
c0000000c6e485d8 160 package body SYS.PBSDE
c0000000c6afe168 1 anonymous block
c0000000c64b76f8 225 procedure CONVDTA.CUSTOMS_DOC_W4_RRT
c0000000c98ad5e0 20 CONVDTA.HF4211CT_BEF_I
c0000000cc5e8da8 7 anonymous block
-----

----------------------------------------
O/S info: user: klemens.weitzel, term: WTSS3006, ospid: 13688:13696, machine: HOPPENET\WTSS3006
program: plsqldev.exe
application name: PL/SQL Developer, hash value=1190136663
action name: Test Window - Test 27.09.06, hash value=1071710304
last wait for 'pipe get' blocking sess=0x0 seq=837 wait_time=540273
handle address=c0000000c57bce38, buffer length=1000, timeout=e10
temporary object counter: 0
----------------------------------------

 

[Marco Kalter]

There are 2 things we can do to analyze this problem:

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 Oracle Debugger seems to have some stability issues when there is not enough free memory in the shared pool.