- Introduction
- nVision Performance Options
- Effects of Performance Options
- Indexing of Ledger, Budget and Summary Ledger Tables
- Partitioning of Ledger, Budget and Summary Ledger Tables
- Additional Oracle Instrumentation for nVision
- Logging Selector Usage
- Analysis of Tree Usage with the Selector Log
- Interval Partitioning and Statistics Maintenance of Selector Tables
- Compression without the Advanced Compression option
- Maintaining Statistics on Non-Partitioned Selector Tables
- Excel -v- OpenXML
- Hinting nVision with SQL Profiles
Related Posts:
- Setting Oracle Session Parameters for Specific Process Scheduler Processes
- Running nVision in a Mixed OpenXML/Excel mode
- Practical Application Performance Tuning: An nVision Case Study (Video)
@go-faster.co.uk on BlueSky
Posts
2 comments :
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.
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.
Post a Comment