Disabling Core Dump Generation by Oracle Processes
(Doc ID 397404.1)
Last updated on MAY 01, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 7.3.4.0 to 10.2.0.3 [Release 7.3.4 to 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Information in this document applies to any platform.
This note applies to all versions of the database on all supported versions of Unix and Linux.
Goal
An ORA-7445 error indicates that an Oracle process has encountered a runtime fault and has generated a core dump. ORA-7445 errors can occur in any Oracle user or background process.
A trace file is always generated when the RDBMS traps an ORA-7445 error. All of the useful information in the core dump is written to the ORA-7445 trace file and Oracle Support and Development engineers rarely need to examine the core file itself. Occasionally, we encounter situations where a bug or corruption will cause hundreds or even thousands of core dumps to be generated in a short period of time. Repetitive 'storms' of ORA-7445 errors and their associated core dumps can cause a file system to fill up completely and actually prevent identifying the specific diagnostics needed to resolve the problem. The repetitive generation of very large core files can also have a significant negative impact on performance.
Therefore, there are times when it may be helpful to block the generation of core dumps by Oracle processes.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |