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

Historical Analysis of Program Global Area (PGA) Utilization

Avatar photoCustomer August 15, 2023 at 6:47 pm

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?

Viewing 4 reply threads
  • Author
    Replies
    • Support August 16, 2023 at 7:55 am  

      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.

    • Avatar photoCustomer August 18, 2023 at 3:47 am  

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

    • Support August 19, 2023 at 9:49 am  

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

    • Avatar photoCustomer August 21, 2023 at 3:20 am  

      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 August 21, 2023 at 6:52 pm  

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

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: