Re: Database with NOLOGGING everywhere
- From: "Roman Podshivalov" <roman.podshivalov@xxxxxxxxx>
- To: Michael.Kline@xxxxxxxxxxxx
- Date: Sun, 6 Apr 2008 14:34:33 -0400
Hi,
I hope you are using RMAN for backups....
In a configuration like that - even if you use HOT (online) backup your
chances to recover are still decent. You will not be able to recover changes
performed to the database during backup window, but all information up to
the beginning of the HOT backup will be there (in restored/recovered
database). However you will have to use DBMS_REPAIR package to skip blocks
modified during backup window if any. (see details -
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/repair.htm#ADMIN022).
If you use COLD backup when database in mounted state you should be able to
restore to backup point in time with no issues.
But in configuration like that you are pretty much missing the possibility
to roll forward your restored database for obvious reasons. So your
restore/recover strategy is based in fixed points in time when backups were
performed.
HTH
--romas
On Sun, Apr 6, 2008 at 2:09 PM, Kline.Michael <Michael.Kline@xxxxxxxxxxxx>
wrote:
> I've got a 1.08TB warehouse that is pretty much all "batch mode".
>
>
>
> Because of that "batching" they have almost 80-95% of the production
> tables set to NOLOGGING, including many at the tablespace level.
>
>
>
> We normally rely on shadow copies, but the database is archivelog.
>
>
>
> Given all the NOLOGGING, what could I possibly hope to "recover" if I ever
> had to use those archivelogs????
>
>
>
> The shadow copy is going to naturally be a COLD backup, I would think that
> would make the archivelogs practically useless.
>
>
>
> Mind you, I may be able to copy a datafile from the shadow copy, and then
> apply archive logs, but again, with all the NOLOGGING defined, what can I
> hope for in the recovery? I guess I can pick up the table creates and all,
> but the data would have to be all repopulated through the batch runs?
>
>
>
> I inherited this one.
>
>
>
> This is at 9.2.0.6, but when we do the next conversion, I think I'm going
> to push for a "more normal" archivelog + LOGGING configuration, RMAN backups
> and some shadow copy for other things that database has to do.
>
>
>
> Thoughts? Comments?
>
>
>
> Looking for someone who may have been caught in this situation and how you
> managed. That good old "Been there done that, ended up doing …" type
> thing. Been very fortunate thus far.
>
>
>
> Michael Kline
>
>
>
>
>
> LEGAL DISCLAIMER
> The information transmitted is intended solely for the individual or
> entity to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or other use
> of or taking action in reliance upon this information by persons or entities
> other than the intended recipient is prohibited. If you have received this
> email in error please contact the sender and delete the material from any
> computer.
>
> SunTrust and Seeing beyond money are federally registered service marks of
> SunTrust Banks, Inc.
> [ST:XCL]
>
Other related posts:
