12c Upgrade – Pre-Upgrade Utility sets PGA_AGGREGATE_LIMIT to 2 GB automatically
(Doc ID 2212556.1)
Last updated on APRIL 05, 2020
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
While upgrading to 18.104.22.168 (with DB PSU 22.214.171.124.160419 applied),the Oracle 12c-DBUA-upgrade process sets PGA_AGGREGATE_LIMIT to 2 GB.
This causes pga_aggregate_target > pga_aggregate_limit.In example below pga_aggregate_target has been set to 3700MB before upgrading to 12c. The DBUA set pga_aggregate_limit to 2 GB, so 3700 MB for PGA can’t be used. This forced an ORA-04036 in alert.log
Target Home had the April 2016 DB PSU 126.96.36.199.160419 Patch 22291127 installed
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Explanation about the parameter PGA_AGGREGATE_TARGET,PGA_AGGREGATE_LIMIT & What should I do if my upgrade fails with ORA-4036|