Oracle Database Administration from Zero to Hero - Managing Database Memory (Part 2 of 2)

The lecture covers memory management in databases, focusing on manual, automatic, and shared memory management. It explains how to set memory sizes, use memory advisors for optimal settings, and provides guidelines for new systems. Advanced topics like buffer cache areas are briefly introduced.

What is a key characteristic of manual shared memory management?

• It uses fixed memory sizes for each area.

• It automatically optimizes performance.

• It dynamically adjusts memory sizes.

• It is the most commonly used approach.

What is the primary purpose of a memory advisor in database management?

• To allocate memory equally across all areas.

• To provide an estimation of optimal memory target values.

• To disable manual memory management.

• To increase the physical memory of the system.

How does the AMM advisor help in optimizing database performance?

• By disabling unused memory areas.

• By suggesting new database features.

• By providing alternative memory target sizes and their impact.

• By increasing the database size automatically.

What is the recommended memory allocation for OLTP systems?

• 40% SGA and 60% BGA

• 60% SGA and 40% BGA

• 70% SGA and 30% BGA

• 50% SGA and 50% BGA

When should you query the memory advisor to verify optimal memory sizes?

• Only during peak workload times.

• Immediately after setting up the database.

• After a few hours or days of normal workload.

• Before enabling AMM.

What should be done if the system documentation specifies memory requirements?

• Use the default memory settings.

• Allocate 50% of memory to the OS.

• Enable AMM and ASMM.

• Follow the documentation and ignore general guidelines.

What is the purpose of additional buffer cache areas like the key pool?

• To automatically adjust memory allocation.

• To enhance performance through manual control.

• To store temporary files.

• To replace the standard buffer cache.