ORA-7445 in core dump while debugging when CDC is enabled

[Ray D]

The below codes match bug 2978401 (ORA-7445 RUNNING PL/SQL DEVELOPER TOOL TO DEBUG PL/SQL WHEN CDC ENABLED). Oracle recommends to run a script if CDC is not being used to remove the CDC objects. This affects version 9.2.0.3.0 and was closed by oracle as 'they could not reproduce'.

Do you have any ideas on the fix for this if we need the CDC database objects? We have re-opened a tar with Oracle on this subject. We are using the latest version of PL/SQL Developer 5.1.6.747.

Thanks,

Ray

This is the trace info of the core dump:

*** 2004-06-03 13:54:48.043
*** SESSION ID310.36932) 2004-06-03 13:54:48.039
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x10, PC: [0x1021c72a8, 00000001021C72A8]
*** 2004-06-03 13:54:48.047
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [00000001021C72A8] [SIGSEGV] [Address not mapped to object] [0x000000010] [] []
Current SQL statement for this session:
BEGIN
/* NOP UNLESS A TABLE OBJECT */
IF dictionary_obj_type = 'TABLE' AND sys.dbms_cdc_publish.active > 0
THEN
sys.dbms_cdc_publish.change_table_trigger(dictionary_obj_owner,dictionary_obj_name,sysevent);
END IF;
END;

 

[Marco Kalter]

I'm afraid this bug has to be fixed by Oracle, because it's a core dump as a result of a DDL trigger in debug mode.

 

[John T.]

We are having this same problem using 9.2.0.5 EE. I am trying to get Oracle to address it but I am being told it is PL/SQL Developer's problem as it does not happen when we compile through sql*plus. We really can't live with this problem and the workaround mentioned in the Oracle Bug is a problem for us because we are going to be using the CDC (change data capture) feature soon. What is it that PL/SQL DEVELOPER is doing that would cause the ora-7445 to occur?

 

[Marco Kalter]

You can reproduce it in SQL*Plus like this:

SQL> alter session set plsql_debug=true;
SQL> @yourpackage.sql

This should help you get support from Oracle.