My Oracle Support Banner

Sort Area Does Not Go Beyond 3.7G Even If The PGA_AGGREGATE_TARGET Is High Enough (Doc ID 2207390.1)

Last updated on MARCH 12, 2021

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Although sufficient memory is allocated in RAM, sorting still uses the temporary space on disk after reaching a 3.7Gb limit. The following testcase reproduces the problem:

Setting _PGA_MAX_SIZE or _SMM_MAX_SIZE to larger values, does not help. Increasing the PGA_AGGREGATE_TARGET does not allow the memory allocated for sorts to increase more then 3.7Gb.

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


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