Home » Server Options » Data Guard » dataguard best practise (oracle 10g ,hp-ux)
icon7.gif  dataguard best practise [message #481700] Fri, 05 November 2010 06:14 Go to next message
dbaoracleinin
Messages: 19
Registered: November 2010
Location: abc
Junior Member
Guys

What is best practise for dataguard according to your experience
do u think archive lag target should be mandatory to be set in dataguard setup or there is other options also
if there are other options then what is best

what is preferred to be set archive lag target or fast_start_mttr(by disabling archive lag target) in oracle 10g


Thanks
Re: dataguard best practise [message #481712 is a reply to message #481700] Fri, 05 November 2010 08:23 Go to previous messageGo to next message
John Watson
Messages: 4793
Registered: January 2010
Location: Global Village
Senior Member
I think you may need to research these parameters!

archive_lag_target can be used to force log switches. fast_start_mttr_target can limit the instance recovery time following instance failure. Under what circumstances (if any) would these parameters be relevant to Data Guard? Why would you consider them together?

I hope that gives you a couple of pointers for research.
Re: dataguard best practise [message #481713 is a reply to message #481712] Fri, 05 November 2010 08:30 Go to previous messageGo to next message
dbaoracleinin
Messages: 19
Registered: November 2010
Location: abc
Junior Member
Hi

I think u misunderstood the question, i dont mean to use both the parameters i know fast_start_mttr makes sense once archive lag target disables(0) , i want to know in dataguard scenerio which can be used

thanks
Re: dataguard best practise [message #481714 is a reply to message #481712] Fri, 05 November 2010 08:31 Go to previous messageGo to next message
dbaoracleinin
Messages: 19
Registered: November 2010
Location: abc
Junior Member
to ask in other way does setting up dataguard is it necessary to set archive lag target or its optional and what is other alternatives

thanks
Re: dataguard best practise [message #481715 is a reply to message #481713] Fri, 05 November 2010 08:34 Go to previous messageGo to next message
John Watson
Messages: 4793
Registered: January 2010
Location: Global Village
Senior Member
dbaoracleinin wrote on Fri, 05 November 2010 08:30

i know fast_start_mttr makes sense once archive lag target disables

In that case, you know something I don't! You need to to do some research.
Re: dataguard best practise [message #481718 is a reply to message #481715] Fri, 05 November 2010 10:26 Go to previous messageGo to next message
dbaoracleinin
Messages: 19
Registered: November 2010
Location: abc
Junior Member
Hello John



fast_start_mttr work after disabling lag archive target
i mean it will be useful also recommended by oracle and general practise ,both can be enabled though

thanks
Re: dataguard best practise [message #481720 is a reply to message #481718] Fri, 05 November 2010 11:05 Go to previous message
John Watson
Messages: 4793
Registered: January 2010
Location: Global Village
Senior Member
I guess I wasn't clear enough. Neither of those parameters is relevant to Data Guard.
Previous Topic: Data Guard Compression
Next Topic: Changing dbname,sid,data/control file locations
Goto Forum:
  


Current Time: Sun Nov 23 16:26:41 CST 2014

Total time taken to generate the page: 0.04702 seconds