ORA 7445 [lstclo()+34]
(Doc ID 1609413.1)
Last updated on FEBRUARY 26, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 to 12.1.0.1 [Release 11.2 to 12.1]Oracle 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.
Symptoms
The alert log shows an ORA-07445 [lstclo()+34] like below multiple times per day:
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x0] [PC:0x936F636, lstclo()+34] [flags: 0x0, count: 1]
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_ora_111113.trc (incident=594602):
ORA-07445: exception encountered: core dump [lstclo()+34] [SIGSEGV] [ADDR:0x0] [PC:0x936F636] [Address not mapped to object] []
Incident details in: <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/incident/incdir_594602/<instname>_ora_111113_i594602.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Wed Aug 21 09:09:13 2013
Dumping diagnostic data in directory=[cdmp_20130821090913], requested by (instance=1, osid=111113), summary=[incident=594602].
Wed Aug 21 09:09:15 2013
Sweep [inc][594602]: completed
Sweep [inc2][594602]: completed
The call stack from the trace file shows functions similar to:
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 |