Ora-7445 Message [message #168878] |
Mon, 24 April 2006 00:00  |
renu123
Messages: 2 Registered: August 2005 Location: Malaysia
|
Junior Member |
|
|
Hi there
I wonder if anyone out there had encountered the following problem. It would be great if anyone could let me know how it was solved.
Thank you,
*** 2006-04-20 16:06:05.260
*** SESSION ID:(288.53192) 2006-04-20 16:06:05.235
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x10, PC: [0x1022ff8a8, 00000001022FF8A8]
*** 2006-04-20 16:06:05.262
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [00000001022FF8A8] [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;
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp()+328 CALL ksedst() 00000000B ? 000000000 ?
000000000 ? 00000004A ?
FFFFFFFF7FFEE5E8 ?
|
|
|
Re: Ora-7445 Message [message #168887 is a reply to message #168878] |
Mon, 24 April 2006 01:18  |
Frank Naude
Messages: 4593 Registered: April 1998
|
Senior Member |
|
|
Check if you can execute the code in the trace file manually. If you have a valid Oracle support contract in place, please also log a TAR/SR on Metalink:
07445, 00000, "exception encountered: core dump [%s] [%s] [%s] [%s] [%s] [%s]"
// *Cause: An OS exception occurred which should result in the creation of a
// core file. This is an internal error.
// *Action: Contact your customer support representative.
|
|
|