nerdexam
Oracle

1Z0-052 · Question #118

View Exhibit to examine the current memory allocation and parameter settings, respectively. Why are advisors not available for the shared pool and the buffer cache?

The correct answer is C. because Automatic Shared Memory Management (ASMM) is enabled for the database instance. When Automatic Shared Memory Management (ASMM) is enabled via SGA_TARGET, Oracle manages shared pool and buffer cache sizes automatically, disabling their individual memory advisors.

Managing the Database Instance

Question

View Exhibit to examine the current memory allocation and parameter settings, respectively. Why are advisors not available for the shared pool and the buffer cache?

Exhibits

1Z0-052 question #118 exhibit 1
1Z0-052 question #118 exhibit 2

Options

  • Abecause the DB_CACHE_ADVICE parameter is set to OFF
  • Bbecause Automatic Memory Management (AMM) is disabled for the database instance
  • Cbecause Automatic Shared Memory Management (ASMM) is enabled for the database instance
  • Dbecause the values for the DB_CACHE_SIZE and SHARED_POOL_SIZE parameters were not set initially

How the community answered

(37 responses)
  • A
    5% (2)
  • B
    3% (1)
  • C
    84% (31)
  • D
    8% (3)

Why each option

When Automatic Shared Memory Management (ASMM) is enabled via SGA_TARGET, Oracle manages shared pool and buffer cache sizes automatically, disabling their individual memory advisors.

Abecause the DB_CACHE_ADVICE parameter is set to OFF

DB_CACHE_ADVICE=OFF only disables the Buffer Cache Advisor and cannot explain why the Shared Pool Advisor is also unavailable.

Bbecause Automatic Memory Management (AMM) is disabled for the database instance

AMM being disabled (MEMORY_TARGET not set) does not cause the absence of component-level advisors - ASMM being active is the relevant condition.

Cbecause Automatic Shared Memory Management (ASMM) is enabled for the database instanceCorrect

When ASMM is enabled by setting SGA_TARGET to a non-zero value, Oracle automatically tunes the buffer cache and shared pool sizes internally, rendering the Buffer Cache Advisor and Shared Pool Advisor unavailable because manual advisory guidance is not applicable when Oracle controls those allocations.

Dbecause the values for the DB_CACHE_SIZE and SHARED_POOL_SIZE parameters were not set initially

Not setting initial values for DB_CACHE_SIZE and SHARED_POOL_SIZE does not prevent advisors from running; advisor availability is governed by whether ASMM is active.

Concept tested: ASMM impact on SGA component memory advisors

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-memory.html

Topics

#ASMM#memory advisors#shared pool#buffer cache

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 1Z0-052 Practice