XML backup fails due to ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
In attempt to perform a XML backup, it fails due to an error on database: ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT
Environment
Jira Server / Data Center connected to an Oracle Database
Diagnosis
A SQL Exception is thrown when performing a XML Backup, which is related to the Oracle Database running out of memory.
On the stack trace at atlassian-jira.log we can obverse errors like these:
1
2
3
.../secure/admin/XmlBackup.jspa [c.a.j.w.action.util.XmlBackup] Exception occurred backing up: java.lang.RuntimeException: java.sql.SQLException: ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT
....
java.lang.RuntimeException: java.sql.SQLException: ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMITCause
Program Global Area (PGA) is an area in memory that is used by sessions in Oracle databases for session-related activities like sorting. In 11g PGA can grow without any restriction if the session demands. Usually, un-tunable processes, consume a lot of PGA, which can impact the overall memory usage of the database.
So in 12c, PGA_AGGREGATE_LIMIT was introduced, which puts a cap on the PGA growth. In Oracle Database 12c, a new parameter called PGA_AGGREGATE_LIMIT sets a hard limit on the amount of PGA taken up by an instance. When the overall PGA occupied by all the sessions in that instance exceed the limit, Oracle kills the session holding the most un-tunable PGA memory, releasing all PGA memory held by that session.
Solution
Increasing the PGA_AGGREGATE_LIMIT should fix the issue:
Set PGA_AGGREGATE_LIMIT to a higher value, example:
1
alter system set pga_aggregate_limit=3072M scope=both;Was this helpful?