tag:blogger.com,1999:blog-25740336.post6568524092045219054..comments2023-08-24T22:26:48.675+01:00Comments on The PeopleSoft DBA Blog: nVision Performance Tuning: Table of ContentsDavid Kurtzhttp://www.blogger.com/profile/00468908370233805717noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-25740336.post-32626910310277302782018-02-02T09:45:52.282+00:002018-02-02T09:45:52.282+00:00You need to set PGA_AGGREGATE_LIMIT to 0. Paramet...You need to set PGA_AGGREGATE_LIMIT to 0. Parameter has default value like 2G and if any session hits the limit, gets terminated. This was introduced in 12c and need to be set to 0, for it to behave normally.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-25740336.post-44273811287778759592017-10-19T20:52:03.230+01:002017-10-19T20:52:03.230+01:00Thank you for such a timely series. I am trying to...Thank you for such a timely series. I am trying to resolve an ORA-04036 PGA memory used by instance exceeds PGA_AGGREGATE_LIMIT errors on a user nvision report in our Oracle 12.1.0.2 database. The report runs fine in our prod environment where optimizer_features_enable='10.2.0.4'. I have tried many different combinations of performance options for the trees in the layout to no avail. I am looking forward to more posts on this topic.Maggie K.https://www.blogger.com/profile/12503651805156451328noreply@blogger.com