Re: Manual Standby as alternative to dataguard
Date: Tue, 16 Jun 2009 20:59:45 +0200
What kind of problem does the business see with force logging? What transactions do you have that they require nologging on that is critical to the business?
That is, are you fighting a theoretical or real problem? Force logging is that because it is needed. You cannot invent data that is now written to the log files. Manual or not, you'll have the same need to have logging occur.
I think you are better off dealing with the actual issue, rather than something that seems to an opinion not based on hard data.
On Tue, Jun 16, 2009 at 8:41 PM, sanjeev m <sanjeevorcle_at_gmail.com> wrote:
> At our site we are having difficulty getting approval from business to
> enable force logging on database objects.
> We plan to implement DR using manual method ie (shipping archive logs to DR
> site through cronjob, performing manual recovery on mounted standby
> I understand without forcelogging all nologging transactions wont be
> recoverable. Is this true during recovery or after activating the standby?
> Is forcelogging a mandatory pre-requisite for implementing Dataguard? Has
> any of you have experience implementing Dataguard without force logging
> Will there be any issues during managed recovery if it encounters a
> nologging change? Wont we be hitting same issue if we are doing the recovery
> manually as opposed to MRP process?