Which background process does Automatic Shared Memory Management use to coordinate the sizing of memory components?

PMON (Process Monitor) cleans up failed user processes and releases resources, and has no role in SGA memory sizing.

SMON (System Monitor) handles instance recovery, coalesces free space in tablespaces, and manages temporary segments, but does not manage shared memory sizing.

MMNL (Manageability Monitor Light) performs lightweight tasks such as flushing the Active Session History buffer to disk, not SGA component sizing.

MMAN, the Memory Manager background process, is the dedicated Oracle process responsible for coordinating and implementing Automatic Shared Memory Management. It monitors memory component usage and automatically adjusts the sizes of the buffer cache, shared pool, large pool, Java pool, and streams pool based on workload demands within the configured SGA_TARGET limit.

MMON (Manageability Monitor) performs manageability tasks such as taking AWR snapshots and issuing server alerts, not automatic memory resizing.