ORA-07445: exception encountered: core dump
OracleWhat does it mean?
An Oracle server process crashed unexpectedly after receiving an operating system-level exception (e.g. SIGSEGV segmentation fault, access violation) and produced a core dump. Unlike ORA-00600, the error is triggered by a signal from the operating system.
Why does it happen?
Usually an Oracle software bug, memory corruption, corrupt data/index blocks, incompatible libraries or a hardware/memory failure. The function name and signal type (e.g. SIGSEGV) in the message identify the code path that crashed.
How to fix it
Preserve the generated trace and incident files and the alert.log, and search My Oracle Support with the function name + signal; a patch is usually required. Run hardware/memory tests and align operating system and Oracle patch levels. If corruption is suspected, run RMAN VALIDATE / DBVERIFY. If it recurs, open an SR and send the core dump to Support.
More from this engine
- ORA-03135connection lost contact
- ORA-01033ORACLE initialization or shutdown in progress
- ORA-00600internal error code, arguments: [...]
- ORA-01102cannot mount database in EXCLUSIVE mode
- ORA-29913error in executing ODCIEXTTABLEOPEN callout
- ORA-19804cannot reclaim N bytes disk space from M bytes limit
- ORA-00494enqueue held for too long by 'inst N, osid M'