1. Oracle Autonomous Health Framework User's Guide
  2. Resolve ORA-07445 Exception Encountered: Core Dump Errors

Resolve ORA-07445 Exception Encountered: Core Dump Errors

For more information and videos, see https://blogs.oracle.com/database/post/ora-07445.

Follow these step-by-step instructions for everything you need to do to resolve ORA-07445.

ORA-07445: exception encountered: core dump occurs when an Oracle Database process encounters an operating system exception that can result in the creation of a core file.

The error message identifies the Oracle function that was executing when the exception occurred and can also contain diagnostic information such as memory addresses.

Oracle Database records the error in the database instance alert log. The associated diagnostic information can help determine the process and conditions that caused the exception.

Common causes of an ORA-07445 error include:

  • Invalid or unexpected data
  • Severe configuration problems
  • Software bugs

The impact of an ORA-07445 error can vary significantly. An isolated occurrence might only appear in the diagnostic logs, while a more serious condition can affect database availability.

For additional information about ORA-07445 errors, see the Oracle Database resources for ORA-07445.

Troubleshoot ORA-07445

Use the following workflow to diagnose and resolve an ORA-07445 error:

  1. Use Oracle Autonomous Health Framework (AHF) to generate an ORA-07445 Service Request Data Collection (SRDC).
  2. Upload the diagnostic collection to the My Oracle Support ORA-07445 troubleshooting tool and review its recommendations.
  3. If the problem cannot be resolved using the recommendations, create a Service Request (SR) and provide the diagnostic collection to Oracle Support.

Generate an ORA-07445 Diagnostic Collection

Log in to the system where the ORA-07445 error occurred.

As the Oracle software owner, run:

tfactl diagcollect -srdc ORA-07445

AHF prompts you to specify the date and time when the ORA-07445 error occurred.

If you do not know the exact date and time, press Enter to allow AHF to search for the applicable occurrence.

AHF also prompts you to specify the database name.

For example:

$ tfactl diagcollect -srdc ORA-07445

Enter the time of the ORA-07445 [YYYY-MM-DD HH24:MI:SS,<RETURN>=ALL] : 2024-03-11 10:11:22
Enter the Database Name [Required for this SRDC] : cdb19

Components included in this collection: OS DATABASE NOCHMOS ASM SOSREPORT

Preparing to execute support diagnostic scripts.

Collecting data for local node(s).

TFA is using system timezone for collection, All times shown in PDT.
Scanning files from 2024-03-11 09:41:22 PDT to 2024-03-11 10:14:32 PDT

Collection Id : 20240311101444mymachine1

Detailed Logging at :
/u01/app/grid21/oracle.ahf/data/repository/srdc_ora7445_collection_Mon_Mar_11_10_14_47_PDT_2024_node_local/diagcollect_20240311101444_mymachine1.log

Waiting up to 120 seconds for collection to start

2024/03/11 10:14:52 PDT : NOTE : Any file or directory name containing the string .com will be renamed to replace .com with dotcom
2024/03/11 10:14:52 PDT : Collection Name : tfa_srdc_ora7445_Mon_Mar_11_10_14_46_PDT_2024.zip
2024/03/11 10:14:53 PDT : Collecting Additional Diagnostic Information...
2024/03/11 10:14:53 PDT : Getting list of files satisfying time range [03/11/2024 09:41:22, 03/11/2024 10:14:32]
2024/03/11 10:15:34 PDT : Executing TFA rdahcve with timeout of 600 seconds...
2024/03/11 10:15:36 PDT : Executing IPS Incident Package Collection(s)...
2024/03/11 10:15:38 PDT : Generating IPS Pack for 1 incidents on database cdb19
2024/03/11 10:15:46 PDT : Executing SQL Script db_feature_usage.sql on cdb19 with timeout of 600 seconds...
2024/03/11 10:15:46 PDT : Executing Collection for ASM with timeout of 1800 seconds...
2024/03/11 10:15:56 PDT : Collecting ADR incident files...
2024/03/11 10:16:07 PDT : Executing Collection for AFD with timeout of 1860 seconds...
2024/03/11 10:16:11 PDT : Executing Collection for OS with timeout of 1920 seconds...
2024/03/11 10:16:15 PDT : Executing Collection for SOSREPORT with timeout of 1980 seconds...
2024/03/11 10:17:54 PDT : Completed Collection of Additional Diagnostic Information...
2024/03/11 10:17:58 PDT : Completed Local Collection
2024/03/11 10:17:58 PDT : Not Redacting this Collection on Exadata with no redaction option passed ..
2024/03/11 10:17:58 PDT : Not Redacting this Collection ...
2024/03/11 10:17:58 PDT : Collection completed on host: mymachine1
2024/03/11 10:17:58 PDT : Completed collection of zip files.

.---------------------------------------.
|           Collection Summary          |
+-------------+-----------+------+------+
| Host        | Status    | Size | Time |
+-------------+-----------+------+------+
| mymachine1  | Completed | 44MB | 185s |
'-------------+-----------+------+------'

Logs are being collected to:
/u01/app/grid21/oracle.ahf/data/repository/srdc_ora7445_collection_Mon_Mar_11_10_14_47_PDT_2024_node_local

/u01/app/grid21/oracle.ahf/data/repository/srdc_ora7445_collection_Mon_Mar_11_10_14_47_PDT_2024_node_local/mymachine1.tfa_srdc_ora7445_Mon_Mar_11_10_14_46_PDT_2024.zip

AHF collects the diagnostic information required to investigate the error and packages the information into a ZIP file.

If diagnostic packages are generated for multiple nodes, use the package from the node on which the ORA-07445 error occurred.

Review Recommendations in My Oracle Support

After generating the AHF diagnostic collection, use the My Oracle Support ORA-07445 troubleshooting tool to analyze the problem.

  1. Sign in to My Oracle Support.
  2. Search for ORA-07445, or open the ORA-07445 troubleshooting tool.
  3. Proceed to the diagnostic collection step.
  4. Select the option to upload a TFA package.
  5. Select the ZIP file generated by AHF for the node on which the error occurred.
  6. Upload the diagnostic package.
  7. After the upload completes, proceed to the next step in the troubleshooting tool.

The troubleshooting tool analyzes the diagnostic collection and compares information from the logs with known ORA-07445 problems.

Based on the analysis, the tool can recommend a relevant My Oracle Support Knowledge document.

The recommended document can provide:

  • Troubleshooting instructions
  • Known issues associated with the ORA-07445 error
  • Related Oracle Database bugs
  • Information about Database Release Updates (RUs) that contain applicable fixes

Review the recommendations and determine whether one of the identified solutions resolves the problem.

Create a Service Request

If the My Oracle Support troubleshooting tool does not identify an appropriate solution, or if additional assistance is required, create a Service Request with Oracle Support.

  1. Select Create SR in the troubleshooting tool.

  2. Provide the requested information, including:

    • Product
    • Product version
    • Support Identifier
    • Operating system
    • SR severity
  3. Select Create SR.

My Oracle Support creates the Service Request and assigns an SR number.

The AHF diagnostic collection that was uploaded during troubleshooting is associated with the Service Request so that Oracle Support can use the collected diagnostic information to continue the investigation.