Skip to main content

Standard Value to set SGA and PGA Memory in Oracle

Standard Value to set SGA and PGA Memory in Oracle

Setting the appropriate values for SGA (System Global Area) and PGA (Program Global Area) is crucial for optimizing Oracle database performance. If you have 64 GB of total memory available on your server, you need to allocate memory to SGA and PGA wisely to balance between database cache, session management, and overall performance. Below are some guidelines for setting SGA and PGA values:

Recommended Allocation Strategy

For a server with 64 GB of total memory, consider the following strategy:

  1. SGA and PGA Distribution:
    • Typically, allocate about 60-70% of the total memory to Oracle, leaving some for the OS and other processes.
    • For example, if using 60% of 64 GB, then about 38 GB can be allocated to Oracle memory (SGA + PGA).
  2. SGA and PGA Breakdown:
    • SGA (System Global Area): Allocate about 75-80% of Oracle's allocated memory.
    • PGA (Program Global Area): Allocate about 20-25% of Oracle's allocated memory.

Memory Settings Calculation Example:

  • Total Memory for Oracle: 60% of 64 GB = 38 GB (approximately).
  • SGA Size: 75% of 38 GB ≈ 28.5 GB.
  • PGA Size: 25% of 38 GB ≈ 9.5 GB.

Suggested Parameter Values:

  1. SGA Settings:


    ALTER SYSTEM SET sga_target = 28G SCOPE = BOTH; ALTER SYSTEM SET sga_max_size = 28G SCOPE = SPFILE;
  2. PGA Settings:


    ALTER SYSTEM SET pga_aggregate_target = 9G SCOPE = BOTH; ALTER SYSTEM SET pga_aggregate_limit = 12G SCOPE = SPFILE; -- Optional, to cap PGA memory usage

Considerations:

  • OS Memory Requirements: Ensure that about 30-40% of the memory is left for the operating system and other processes, i.e., at least 18-26 GB.
  • Adjust Based on Workload: These values are starting points. You may need to fine-tune based on database workload, session count, and performance observations.
  • Monitor Memory Usage: Use Oracle’s AWR (Automatic Workload Repository) reports and views like v$sga_target_advice and v$pga_target_advice to monitor memory usage and adjust as needed.

Key Points:

  • SGA is used for shared memory structures, including the buffer cache, shared pool, and redo log buffer.
  • PGA is used for session-specific memory, sorting, and hash joins, important for complex queries and OLAP operations.

Properly setting and managing SGA and PGA helps ensure that your Oracle database performs efficiently, avoiding memory shortages or over-allocations that can impact system stability and performance.






Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...