Hi Dafydd Griffith,
To address your query generic terms, I would suggest you to refer the following Note
EBS Database Parameter Settings Analyzer (Doc ID 1953468.1)
Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1)
I hope this could help to answer your query.
Thanks for that. I've just run it against our current production system (Manual Memory Management) and it suggests that I up the SGA_TARGET from 4GB to 14GB. I can't do that as we don't have the RAM so the server migration is timely!
As the current system is a RAC server and were moving to a non RAC environment then I suspect I'm looking at a figure of around 20-28Gb for the SGA_TARGET? Obviously I'll have to add on extra for the PGA if I go the AMM route and define MEMORY_MAX_TARGET at around 30-40GB?
Is 40GB a realistic size for running AMM on a Solaris 11 server or is it just too big if the block size is the default 8k? It's looking like I'm better off going the ASMM and large/huge pages route?
In my experience, large/huge page plus sga_target always outperforms AMM with EBS. If you enable AMM, you will see the MMON process running at 100% CPU most of the time trying to guess what the memory allocation should be as the system constantly switches between predominantly transaction processing to long running batch workloads like create accounting or other long running frequent reports. The pga_aggregate_target parameter is not a limit either. If you query v$sesstat, you can find individual EBS sessions using more PGA than pga_aggregate target. If you have hundreds of users, you really need to ensure you have enough free RAM on the server to handle UGA/PGA memory grabs by shadow processes which are outside of ASSM/AMM memory allocations. Otherwise you can find the server heavily swapping when a long running process suddenly grabs 10-20GB of UGA or PGA.
Many thanks for that.
If anyone else has an opinion then please express it here. I have a few weeks left before I have to implement this.