Re: Rman Question

From: <>
Date: Tue, 2 Dec 2008 08:09:20 -0800 (PST)
Message-ID: <>

On Dec 2, 9:48 am, hpuxrac <> wrote:
> On Dec 1, 10:19 pm, wrote:
> > I need to restore a copy of our database on a different server.  I
> > have full backups going back 4 weeks plus cumulative backups.
> > I'm not sure where the problem happened.  So, I figure I can restore
> > the earilest copy, and if that is not it, restore the next full
> > backup......
> > Anyhow, I am looking for some decent documentation that will tell me
> > the best way to restore the database onto a new server as well as
> > choosing which incarnation of the database I want to restore.......
> Well the oracle rman documentation ( available free
> is one place ) is pretty comprehensive in this area.
> Just make sure that you are looking at documentation that matches the
> same version of oracle and same version of rman that you are going to
> be using.
> Robert Freeman among others has some pretty good books out in this
> area.
> It may be best to sit and read for a while before jumping in with a
> half formed plan of attack.
> If there are "specific" questions ... well fire away.  It makes many
> of us nervous though when people start throwing in terms like
> incarnation where it sounds like they might have some idea of recovery
> related concepts ... but also include questions about ( relatively )
> basic procedures like restoring on a different server.  Is there any
> reason you wouldn't want to restore the current incarnation in other
> words?

Thanks for all your help. We are running 10gR2. We do not know exactly when the error occurred, sometime within the last 2 weeks. So, we figure we restore a copy from 2 weeks ago and roll forward and start checking as we go........

What about getting the archive logs and mining them? Can that be done to tell us exactly when and how it happened?

As far as duplicating the database. Are you suggesting we duplicate it on a different server, then recover it the duplicated one?

Thanks! Received on Tue Dec 02 2008 - 10:09:20 CST

Original text of this message