I'm getting an error every day around 10:15 p.m., and I think it's because of the RMAN Process. ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT.
top of page
To see this working, head to your live site.
Edited: Mar 14, 2022
ORA-04036: PGA Memory Used By The Instance Exceeds PGA_AGGREGATE_LIMIT
ORA-04036: PGA Memory Used By The Instance Exceeds PGA_AGGREGATE_LIMIT
2 answers2 replies
Like
4 Comments
bottom of page
RMAN Does take good amount of Oracle instance resources while triggering database backups. Here are the ideas to solve this issue:
Schedule RMAN backups to another time when the load on the database is less
Increase PGA_AGGREGATE_LIMIT value
Check to see if you have free RAM at OS level. Add 1GB or 2GB to PGA_AGGREGATE_LIMIT on the problematic database.
If you have multiple databases running on same server and does not have free RAM at OS level to add, then reduce the SGA size of other database by 1GB and add it to PGA on the problematic database.
Reduce SGA on another database: =============================== ALTER SYSTEM SET SGA_TARGET = (total size - 1GB);Increase PGA_AGGREGATE_LIMIT: ============= ALTER SYSTEM SET PGA_AGGREGATE_LIMIT = 5G;Check below articles to tune SGA, PGA and MEMORY_TARGET
How to check Oracle Instance Size
How to Increase MEMORY_TARGET
Hi Piyush!
Have you sheduled any rman backup around this time?