PGA Memory Leak Is Observed When DBMS_SQL.PARSE Is Invoked with 'Container' Parameter
(Doc ID 2704405.1)
Last updated on AUGUST 28, 2020
Applies to:PL/SQL - Version 126.96.36.199 and later
Information in this document applies to any platform.
The consumption of PGA memory increases rapidly when the procedure DBMS_SQL.PARSE is executed along with the parameter 'container' in an infinite loop. The memory consumption goes back to the initial value instantly as soon as the code is forcibly terminated. However, no such increase is observed when the same call is made without passing the parameter 'container'. The issue can be demonstrated using the following sample code.
Session 1 :-
The code is executed for the first time in the database.
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