>> ... seconds to elapse before performing a crash recovery?

Setting this parameter is not telling Oracle how long you want to wait
before actually beginning the recovery process, just how long you are
willing to let the recovery process take.

This parameter is used to set the Mean Time to Recovery. You set this
parameter to tell Oracle how much time you are willing to allow a
recovery to take. If you are willing to allow the recovery of a crashed
database to take an hour before it is back up and running again, then
you would set this parameter to 3600 (seconds). Oracle will then work
its magic to set checkpoints, etc., to make sure, should your database
crash and burn, that it will not take you more than 1 hour to recover it
(less copying files off of tape drives, etc, of course ... as Oracle
cannot determine the time it takes to do that).






Randy Netz
Oracle DBA
816-860-3921 (work)
816-686-1639 (cell)

-----Original Message-----
From: MCCCLAYTON
[mailto:oracledba-ezmlmshield-x23069335.[Email address protected]
Sent: Wednesday, December 29, 2004 10:03 AM
To: LazyDBA Discussion
Subject: FAST_START_MTTR_TARGET

I've been looking Metalink on this parameter for a 9i database, and I
have a question for the Oracle DBA Continuim. What's the advantage of
setting this parameter for 'X' amount of seconds to elapse before
performing a crash recovery? I would think that the faster the recovery
the better, Right? Therefore, leaving the parameter set to 0.


Mark


--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html


Oracle LazyDBA home page