Re: Reproducing ORA-04036

Hi Nehad,

I slightly amended the package to raise an ORA-4036 in my 19c database:

https://gist.github.com/mvelikikh/3306c657ab43ea1a32304114dc4c84d2

Here is the call:

>
> SQL> exec pkg.fill_memory
> BEGIN pkg.fill_memory; END;
>
> *
> ERROR at line 1:
> ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT
>

Here is the alert log:

2020-08-21T13:29:05.537784+00:00
> Errors in file
> /u01/app/oracle/diag/rdbms/racdb/racdb2/trace/racdb2_ora_99191.trc
> (incident=64761) (PDBNAME=PDB):
> ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT
> PDB(3):Incident details in:
> /u01/app/oracle/diag/rdbms/racdb/racdb2/incident/incdir_64761/racdb2_ora_99191_i64761.trc
> 2020-08-21T13:29:14.350039+00:00
> Errors in file
> /u01/app/oracle/diag/rdbms/racdb/racdb2/trace/racdb2_ora_99191.trc
> (incident=64762) (PDBNAME=PDB):
> ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT
> PDB(3):Incident details in:
> /u01/app/oracle/diag/rdbms/racdb/racdb2/incident/incdir_64762/racdb2_ora_99191_i64762.trc
> 2020-08-21T13:29:15.546665+00:00
> Errors in file
> /u01/app/oracle/diag/rdbms/racdb/racdb2/trace/racdb2_ora_99191.trc
> (incident=64763) (PDBNAME=PDB):
> ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT
> PDB(3):Incident details in:
> /u01/app/oracle/diag/rdbms/racdb/racdb2/incident/incdir_64763/racdb2_ora_99191_i64763.trc
> 2020-08-21T13:29:20.324556+00:00
> PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT of 3072 MB
> (3):KILL SESSION for sid=(416, 25734):
> (3): Reason = pga_aggregate_limit
> (3): Mode = KILL HARD SAFE -/-/-
> (3): Requestor = DBRM (orapid = 15, ospid = 10928, inst = 2)
> (3): Owner = Process: USER (orapid = 95, ospid = 99191)
> (3): Result = ORA-0
>

It is a two node RAC 19.6 with pga_aggregate_limit=3G:

[oracle_at_rac2 ~]$ $ORACLE_HOME/OPatch/opatch lspatches
> 30484981;OJVM RELEASE UPDATE: 19.6.0.0.200114 (30484981)
> 30489227;OCW RELEASE UPDATE 19.6.0.0.0 (30489227)
> 30557433;Database Release Update : 19.6.0.0.200114 (30557433)
>
> OPatch succeeded.
>

Best regards,
Mikhail Velikikh

On Fri, 21 Aug 2020 at 13:51, Noveljic Nenad <nenad.noveljic_at_vontobel.com> wrote:

> Anybody has a script for reproducing ORA-04036 in 19c? Allocating PL/SQL
> collections doesn’t trigger the error:
>
>
>
> SQL> select max(pga_alloc_mem)/power(1024,2) from v$process ;
>
> MAX(PGA_ALLOC_MEM)/POWER(1024,2)
> --------------------------------
> 6466.71202
>
> SQL> show parameter pga
>
> PARAMETER_NAME TYPE VALUE
> ------------------------------------------------------------ -----------
> ----------------------------------------------------------------------------------------------------
> pga_aggregate_limit big integer 2G
>
>
> SQL> !dbhome
> .../product/19.7.0.0.200414
>
>
>
> I had a nice test case with excessive PGA allocations during parsing in
> 12c, but “unfortunately” Oracle fixed that problem.
>
>
>
> Best regards,
>
>
>
> Nenad
>
>
>
> https://nenadnoveljic.com/blog/about
>
>
>
> ____________________________________________________
>
> Please consider the environment before printing this e-mail.
>
> Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
>
>
> Important Notice
> This message is intended only for the individual named. It may contain
> confidential or privileged information. If you are not the named addressee
> you should in particular not disseminate, distribute, modify or copy this
> e-mail. Please notify the sender immediately by e-mail, if you have
> received this message by mistake and delete it from your system.
> Without prejudice to any contractual agreements between you and us which
> shall prevail in any case, we take it as your authorization to correspond
> with you by e-mail if you send us messages by e-mail. However, we reserve
> the right not to execute orders and instructions transmitted by e-mail at
> any time and without further explanation.
> E-mail transmission may not be secure or error-free as information could
> be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
> processing of incoming e-mails cannot be guaranteed. All liability of
> Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively
> referred to as "Vontobel Group") for any damages resulting from e-mail use
> is excluded. You are advised that urgent and time sensitive messages should
> not be sent by e-mail and if verification is required please request a
> printed version. Please note that all e-mail communications to and from the
> Vontobel Group are subject to electronic storage and review by Vontobel
> Group. Unless stated to the contrary and without prejudice to any
> contractual agreements between you and Vontobel Group which shall prevail
> in any case, e-mail-communication is for informational purposes only and is
> not intended as an offer or solicitation for the purchase or sale of any
> financial instrument or as an official confirmation of any transaction.
> The legal basis for the processing of your personal data is the legitimate
> interest to develop a commercial relationship with you, as well as your
> consent to forward you commercial communications. You can exercise, at any
> time and under the terms established under current regulation, your rights.
> If you prefer not to receive any further communications, please contact
> your client relationship manager if you are a client of Vontobel Group or
> notify the sender. Please note for an exact reference to the affected group
> entity the corporate e-mail signature. For further information about data
> privacy at Vontobel Group please consult www.vontobel.com.
>

--
http://www.freelists.org/webpage/oracle-l