This content has been marked as final. Show 3 replies
Probably most of the heavy consumption is PGA related.
Have a look at the AWR history views concerning memory consumption. ADDM, ASH, AWR etc should give you more insight. See also the awr/addm/ash/-rpt.sql scripts in $ORACLE_HOME/rdbms/admin on the database server. You (officially) would need Diagnostic en Tuning pack licenses though, so be warned (even for "touching" those views). Probably the heavy consumption of memory is or (wrong) storage related or inefficient code...
Thanks for the pointers Marco - we do have tuning licenses and I use those tools regularly......
This post was actually to see if there's some sort of parameter that can be applied to limit the amount of memory that the XSLT processor tries to grab - e.g. set a memory limit of 2Gb for XSLT and let it manage itself within that limit.