Scribd
Upload
168 views1 page

Fast Start MTTR Target

The FAST_START_MTTR_TARGET initialization parameter allows administrators to specify the expected time for instance or system crash recovery in seconds. This parameter internally sets other parameters to optimize recovery time to the specified target. The document notes that the FAST_START_IO_TARGET, LOG_CHECKPOINT_INTERVAL, and LOG_CHECKPOINT_TIMEOUT parameters should be disabled when using FAST_START_MTTR_TARGET to avoid interfering with the recovery time optimization.

Uploaded by

Praveen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
168 views1 page

Fast Start MTTR Target

The FAST_START_MTTR_TARGET initialization parameter allows administrators to specify the expected time for instance or system crash recovery in seconds. This parameter internally sets other parameters to optimize recovery time to the specified target. The document notes that the FAST_START_IO_TARGET, LOG_CHECKPOINT_INTERVAL, and LOG_CHECKPOINT_TIMEOUT parameters should be disabled when using FAST_START_MTTR_TARGET to avoid interfering with the recovery time optimization.

Uploaded by

Praveen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

The FAST_START_MTTR_TARGET initialization parameter simplifies the configuration

of recovery time from instance or system failure. This parameter lets you speci
fy the number of seconds crash or instance recovery is expected to take. The FAS
T_START_MTTR_TARGET is internally converted to a set of parameters that modify t
he operation of Oracle such that recovery time is as close to this estimate as p
ossible.
Note:
You should disable or remove the FAST_START_IO_TARGET, LOG_CHECKPOINT_INTERVAL,
and LOG_CHECKPOINT_TIMEOUT
initialization parameters when using FAST_START_MTTR_TARGET. Setting these param
eters to active values interferes with FAST_START_MTTR_TARGET, resulting in a di
fferent than expected value in the TARGET_MTTR column of the V$INSTANCE_RECOVERY
view.
Whenever you set FAST_START_MTTR_TARGET to a nonzero value, and while MTTR advis
ory is ON, Oracle Corporation recommends that you disable (set to 0) the followi
ng parameters:
LOG_CHECKPOINT_TIMEOUT
LOG_CHECKPOINT_INTERVAL
FAST_START_IO_TARGET
Because these initialization parameters either override FAST_START_MTTR_TARGET o
r potentially drive checkpoints more aggressively than FAST_START_MTTR_TARGET do
es, they can interfere with the simulation.
If I remove LOG_CHECKPOINT_TIMEOUT from pfile the parameter appears with the val
ue of 1800, so I set that to 0 in the pfile.

You might also like