My Oracle Support Banner

ORA-4031 Trace File Analysis (Doc ID 1397578.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.


The purpose of this document is to provide some insight in to what information in ORA-4031 trace files can be used to perform an analysis on the root cause of the ORA-4031 error. When dealing with ORA-4031 errors first the ORA-4031 Troubleshooting Tool on My Oracle Support should be used to get an understanding on what might be the cause of the issue. This tool can be found on the My Oracle Support website through Knowledge > Tools and Training > Diagnostic Tools.

This document is intended for DBAs.

Before reading this article, the user must have a good understanding of SQL in order to be able to query the data dictionary views using information provided in the trace files.

Troubleshooting Steps

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
Troubleshooting Steps
 The trace file from the ADR trace directory
 Oracle version and process information
 The heap chunk allocation that failed
 The process state and user session state objects
 The call stack
 The subpool memory utilization statistics
 The library cache statistics
 The reference to the incident trace file name
 The incident trace file from the ADR incident directory
 The call stack
 Memory allocations of the process
 The process state
 The cursor dump of all cursors
 The Auto SGA Transfer History
 The General Configuration section

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.