MEMORY_TARGET versus SGA_TARGET in 19c 

Beside ASMM in combination with large_page. To avoid competent between shared_pool and buffer_cache I recommend set some minimum values for that biggest areas.

Hi Tom This video is very helpful to understand the automatic memory Can you please create a video on Latches and how it works

To someone from a SQL Server (hush at the back!) background, things like AMM are very appealing - set a single parameter for memory, and let the database software figure things out from there. I figure it has a better idea of it's own memory needs at various points in time than I do. But when I tried it, I encountered no end of problems (like the ones described here), and so quickly fell back to ASMM. Really, managing two parameters isn't that much of a hardship - the delineation between the two is clear (shared & private), and the AWR reports are really good at showing you the predicted impact of changes to the SGA and PGA. It sounds like to get AMM to *really* work, Oracle would need to re-architect the memory architecture of its DB software, and that is no small task.

Thank you sir

Asmm bugs flashbacks! Huge page hell.

>has anything changed for 19c No ) I still never use AMM on instances I care about and have do disable ASMM on any database where load is significant and performance is important. Such a nice and useful features ))

Come on Connor - Its pronounced "cash". I assume you are using the American friendly pronuciation 😃