-
We got this once in a while. I suspect it happens whenever we run a certain sql statement in some program. Anyone know how to fix this or if this pose any danger to the database? I checked the dump trace file. It is like
Thanks.Tue Nov 21 10:29:20 2000
*** SESSION ID:(78.46440) 2000.11.21.10.29.20.000
Exception signal: 11
ORA-07445: exception encountered: core dump [11] [] [] [] [] []
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
skdstinit+0xa0 CALL 0 ? 7FFF0480 ? 0 ? 0 ?
ksedst+0xc0 CALL skdstinit 0 ? 7FFF0480 ? 0 ? 0 ?
ssexhd+0xcc CALL ksedst B ? 7FFF0480 ? 0 ? 0 ?
_sigtramp+0x64 CALL ssexhd B ? 7FFF0480 ? 0 ? 0 ?
_sigtramp+0x64 CALL _sigtramp B ? 7FFF0480 ? 0 ? 0 ?
_sigtramp+0x64 CALL _sigtramp B ? 7FFF0480 ? 0 ? 0 ?
_sigtramp+0x64 CALL _sigtramp B ? 7FFF0480 ? 0 ? 0 ?
And so on.
-
Looks like quite a painfull O/S error! Heres the output from the AIX oerr command to analyse ORA errors:
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.
-
In general, ORA-7445 and ORA-600 messages should be reported to Oracle. There is most likely a patchset or a work-around that adresses the problem.
This error probably generated a trace file in your udump or bdump directory. Check that file for the SQL that was running when the error was generated.
-
A quick search on metalink revealed that this might be related to a previous SHUTDOWN ABORT that caused block corruption.
