ORA-4030 PGA Usage Diagnostic Script [Video]
(Doc ID 1087789.1)
Last updated on SEPTEMBER 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Goal
When getting ORA-04030 errors, it is important to see the memory usage on the database for comparison to Operating System usage. The scripts can be used on any platform. NOTE: Explicitly setting SGA_MAX_SIZE with 11g Automatic Memory Management (AMM) can lead to confusion in the internally calculated SGA size. On 11g with AMM, the SGA size and PGA_AGGREGATE_TARGET can show up differently in various V$ tables.
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 |
| Requirements |
| Configuring |
| Instructions |
| Sample Code |
| Sample Output |
| References |