How To Get a Stack Trace
(Doc ID 557409.1)
Last updated on FEBRUARY 14, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 8.1.7.4 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Goal
Sometimes, when an ORA-7445 error is signalled, the trace file written to report the error does not contain a valid stack trace. A normal stack will be found at the beginning of the trace file and will start with the dump functions, followed by the functions accessed by that process, in reverse order, and will end with sou2o. Where the stack trace has failed there may be no stack trace at all or the stack trace may only contain the dump functions such as kse*, or OS functions.
A valid stack trace is essential to the diagnosis of an ORA-7445 error.
The purpose of this document is to give guidance on getting a stack trace where none is printed in the trace file.
The intended audience is database administrators and support engineers.
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 |