Home › Discussions › Questions & Answers › Historical Analysis of Program Global Area (PGA) Utilization

Historical Analysis of Program Global Area (PGA) Utilization

Avatar photoCustomer Questions & Answers 5 replies

We are experiencing slowdowns during large batch jobs that involve complex sorting, suggesting high PGA usage. Which Blitz Report can show the historical PGA size and related statistics?

5 replies

  • Support Enginatics

    Use the DBA AWR PGA History report. This report shows the history of database PGA size and other relevant statistics, retrieved from `v$pgastat` and displayed in megabytes.

  • Does tuning PGA allocation benefit from using Large/Huge pages on Linux, similar to SGA?

  • Support Enginatics

    No, the tuning documentation specifies that while SGA allocation benefits from large/huge pages, PGA allocation does not benefit from this configuration.

  • What is the key parameter for controlling the overall PGA allocation, and what is a general sizing guideline for a large EBS environment (1001-2000 users)?

  • Support Enginatics

    The key parameter is `pga_aggregate_target`. For 1001-2000 users, a recommended value is around 20G.

  • You must be logged in to reply to this post.