Multiple choice technology databases

Which three initialization parameters are no longer needed when FAST_START_MTTR_TARGET is defined? (Choose three)

  1. TARGET_REDO_BLKS

  2. FAST_START_IO_TARGET

  3. LOG_CHECKPOINT_TIMEOUT

  4. RECOVERY_ESTIMATED_IOS

  5. LOG_FILE_SIZE_REDO_BLKS

  6. LOG_CHECKPOINT_INTERVAL

Reveal answer Fill a bubble to check yourself
B,C,F Correct answer
Explanation

FAST_START_MTTR_TARGET automatically manages several parameters to achieve the desired Mean Time To Recovery. When set, Oracle no longer needs FAST_START_IO_TARGET (I/O limit for recovery), LOG_CHECKPOINT_TIMEOUT (time-based checkpoint frequency), or LOG_CHECKPOINT_INTERVAL (redo-based checkpoint frequency). Options A, D, and E are not valid Oracle parameters.

AI explanation

FAST_START_MTTR_TARGET lets you specify a target mean-time-to-recover (in seconds) and Oracle automatically tunes checkpointing to meet it, making several older manual checkpoint-tuning parameters obsolete: FAST_START_IO_TARGET (the older way to bound recovery I/Os), LOG_CHECKPOINT_INTERVAL (redo blocks between checkpoints), and LOG_CHECKPOINT_TIMEOUT (time between checkpoints) are all superseded — Oracle recommends not setting them alongside FAST_START_MTTR_TARGET. TARGET_REDO_BLKS, RECOVERY_ESTIMATED_IOS, and LOG_FILE_SIZE_REDO_BLKS are not real Oracle initialization parameters (distractors), so they can't be 'no longer needed' parameters.