ORA-07445 [_memset] [SIGSEGV] and PMON Terminated the Instance
(Doc ID 1223333.1)
Last updated on JANUARY 16, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.7 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
*** Checked for relevance on 26-Apr-2013 ***
Symptoms
Database terminated by PMON with the following errors:
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xFFFFFFFF7FFF5C28] [PC:0xFFFFFFFF7C700F78, _memset()+120]
ORA-07445: exception encountered: core dump [_memset()+120] [SIGSEGV] [ADDR:0xFFFFFFFF7FFF5C28] [PC:0xFFFFFFFF7C700F78] [Address not mapped to object] []
ORA-00490: PSP process terminated with error
PMON (ospid: 24602): terminating the instance due to error 490
ORA-07445: exception encountered: core dump [_memset()+120] [SIGSEGV] [ADDR:0xFFFFFFFF7FFF5C28] [PC:0xFFFFFFFF7C700F78] [Address not mapped to object] []
ORA-00490: PSP process terminated with error
PMON (ospid: 24602): terminating the instance due to error 490
If we look in Call Stack Trace section of the trace file generated by the error, we can find the following functions:
sdbgrfcvp_convert_pathinfo <- sdbgrfcfpf_convert_fileloc_pfname <- dbgrlWriteAlertDetail_int
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |