Automatic Shared Memory Management is disabled for your database instance. You realize that there are cases of SQL statements performing poorly because of repeated parsing activity, resulting in…

The SQL Access Advisor recommends schema-level changes such as new indexes, materialized views, or partitioning to optimize query execution plans - it does not address memory configuration or parsing frequency.

The SGA Memory Advisor gives high-level guidance on overall SGA sizing and is most relevant when ASMM is enabled - with ASMM disabled, the repeated parsing symptom specifically points to the shared pool component, not the SGA as a whole.

The PGA Memory Advisor helps tune memory allocated for sort, hash join, and bitmap operations in the program global area - parsing is a server process activity within the SGA shared pool, not the PGA.

SQL parsing activity - specifically hard parses where execution plans are recomputed - occurs in the library cache component of the shared pool. When ASMM is disabled the shared pool size is fixed, so the V$SHARED_POOL_ADVICE view (accessed via the shared pool memory advisor) provides sizing recommendations to reduce hard parsing overhead and improve performance.

The buffer cache memory advisor recommends sizing for the database buffer cache to reduce physical I/O - buffer cache sizing does not affect SQL parsing, which is governed by the shared pool.