Re: Recovery scenario

"ohno" <ohno_at_yahoo.com> wrote in message news:3A089F3B.CD127A8C_at_yahoo.com...
> Well, I'm holding....and your assumption is unfortunately wrong :-(.
> I'm in the process of re-defining the backup and recovery needs,
 practices,
> etc. as I've only been here two weeks.
> hahahaha.....poor finance guys.
> Anyhoo, I'm going to change the archive log mode aspect of this database,
 and
> just do hot backups......I don't feel like finance data should be
> trusted to cold backups -- non - archived.
>
> Thanks for the response tho -- I'll use this in the future -- great site
 BTW.
>

Ooops.

Well.... you could still go through the steps outlined below, and still look as if you want to do a 'recover database until cancel' -only, type the word cancel when it prompts for the first archive. It theoretically should still work -only rather faster than I anticipated, because you're not applying any redo at all.

The principle is that having blown away ALL datafiles, and replaced them with your backups, a resetlogs will force the Control Files and Redo Logs into synchronism at time 0. I can't see that the failure to apply any archives has any bearing on your ability to do that.

By the way: I don't recall if this is NT or Unix. If it's NT, then my cloning paper on the website won't be entirely accurate -you have to create a new service to support the clone (using ORADIM or ORADIM80, depending on your version). But the basic principles are the same.

Incidentally, if you put your database into archivelog mode, that doesn't mean you have to start doing hot backups. It remains far easier to do cold ones, and the sole determinant between hot and cold is whether the database has to be kept up and running all the time. If you've got a shutdown maintenance window, do yourself a favour and stick with cold backups.

The concept of finance data not being totally recoverable through lack of archives is, however, I agree, a bizarre one!

Take care, and have fun
Regards
HJR
>
> "Howard J. Rogers" wrote:
>
> > Hold on to your hat, as this isn't easy.
> >
> > First clone your production database (I'm assuming that you are in
> > archivelog mode, even if only doing cold backups. Forget everything
 else
> > from this point on if not). Steps on cloning the database are on the
 Backup
> > and Recovery page of my web site.
> >
> > Now blow away the datafiles of the clone, and restore from the cold
 backup
> > taken X days ago.
> >
> > Try and start up, and the thing should say that your files need medai
> > recovery. Recover database until cancel, and then cancel when
 appropriate
> > (ie, apply just so many archives as are required to get the clone to the
> > point your Finance Manager wants). Open with a resetlogs.
> >
> > Now you can export whatever tables etc you need.
> >
> > Take your new dump file back to your development type database, and
 import
> > appropriate tables and data.
> >
> > It's basically a TSPITR (tablespace point in time recovery). You might
 want
> > to search through the Oracle documentation on TSPITR before leaping in,
 but
> > it's a fairly standard way of recovering from User errors that go
 unreported
> > for days or weeks on end without having to roll your entire production
> > system days or weeks.
> >
> > And when all that's done, you might want to ask your Finance Manager
 what
> > the hell he wants to stuff you around like this for, and if he's going
 to be
> > doing this very often, maybe a second server might be a good idea... he
> > writes the cheques, after all. Have fun!
> >
> > Regards
> > HJR
> > --
> >
>
> --------------------------------------------------------------------------
 -
> > Opinions expressed are my own, and not those of Oracle Corporation
> > Oracle DBA Resources:

 http://www.geocities.com/howardjr2000
>
> --------------------------------------------------------------------------
 -
> >
> > "ohno" <ohno_at_yahoo.com> wrote in message
 news:3A083CCF.9D4F49F9_at_yahoo.com...
> > > Running Oracle 805 on Solaris 2.6.
> > >
> > > We have two instances on the same box -- one is a production instance,
> > > the
> > > other is a development type instance. They are both very similar in
> > > scope, but there
> > > are some minor differences (a couple of different tablespaces, etc.).
> > > Finance Manager just came and wants the data from the production
> > > instance
> > > restored from a few days ago to the development instance -- however,
> > > there isn't exports done, only cold backups (yeah, I know...but I just
> > > got here two weeks ago).
> > >
> > > So, there really isn't a way to do what he wants done that I can see,
> > > because restoring the cold backup from the production instance would
> > > only restore to
> > > the production instance, not development.
> > >
> > > YIKES!
> > >
> > > Suggestion?
> > >
>
Received on Tue Nov 07 2000 - 21:11:10 CST