Which two will be the implications of these values in your database?

Examine the values for the following initialization parameters:
FAST_START_MTTR_TARGET=0
LOG_CHECKPOINT_INTERVAL=0
Which two will be the implications of these values in your database? (Choose two.)

Examine the values for the following initialization parameters:
FAST_START_MTTR_TARGET=0
LOG_CHECKPOINT_INTERVAL=0
Which two will be the implications of these values in your database? (Choose two.)

A.
The SGA advisor will be disabled

B.
The MTTR advisor will be disabled

C.
Automatic checkpoint tuning will be disabled

D.
Checkpoint information will not be written to the alert log file



Leave a Reply 4

Your email address will not be published. Required fields are marked *


Léon

Léon

Duplicate with Q8

Léon

Léon

and with Q80

jean

jean

FAST_START_MTTR_TARGET enables you to specify the number of seconds the database takes to perform crash recovery of a single instance.

When specified, FAST_START_MTTR_TARGET is overridden by LOG_CHECKPOINT_INTERVAL.

LOG_CHECKPOINT_INTERVAL specifies the frequency of checkpoints in terms of the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log. This number refers to physical operating system blocks, not database blocks.

Check-pointing is an important Oracle activity which records the highest system change number (SCN) so that all data blocks less than or equal to the SCN are known to be written out to the data files. If there is a failure and then subsequent cache recovery, only the redo records containing changes at SCN(s) higher than the checkpoint need to be applied during recovery.

Luz

Luz

Tuning – check the right amount of interval