In today’s article, we will cover the ORA-04036: error that comes at the end of the upgrade while performing an upgrade on the database.
After examining it, I noticed that I got the following error.
1 2 3 | ORA-00028: your session has been killed ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT of 4000 MB |
The problem is roughly as follows, PGA space is a space used for existing sessions and on 11G this space can grow independently depending on capacity.
In 12C and later, ” pga_aggregate_limit ” parameter was introduced. Since this parameter limits us, it leads to error.
In fact, the first thing to do is to find the answer to the question of why the kill process consumes so much resources.
If we look at the quick solutions,
For example, you can set the “pga_aggregate_limit” limit to 0.
1 | alter system set pga_aggregate_limit=0 scope=both; |
Or you can increase the limit.
1 | alter system set pga_aggregate_limit=4096M scope=both; |