| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Incomplete Recovery
Actually, come to think of it, that happened to me on my last course -and completely stuffed up the, er, impressive demo I was doing at the time -it was the shutdown abort that did it... my script calls for an immediate, and I got a bit impatient.
Regards
HJR
<sybrandb_at_my-deja.com> wrote in message news:94mieg$u5s$1_at_nnrp1.deja.com...
> In article <3a6eabd6_at_news.iprimus.com.au>,
> "Howard J. Rogers" <howardjr_at_www.com> wrote:
> >
> > <sybrandb_at_my-deja.com> wrote in message news:94m6u4$lq8
$1_at_nnrp1.deja.com...
> > > In article <3a6e83f5_at_news.iprimus.com.au>,
> > > "Howard J. Rogers" <howardjr_at_www.com> wrote:
> > > >
> > > > Yes, well... best to learn about what's involved in an incomplete
recovery,
> > > > I suspect. For starters, you need to restore ALL datafiles from a
backup
> > > > taken before your test -but most definitely NOT the Controlfiles
or
Online
> > > > Redo Logs. The entire database is then rolled forward to a given
time, or
> > > > until it's cancelled, or until a given SCN. Then you can do an
open
> > > > resetlogs.
> > > >
> > > > The commonest error encountered when performing incomplete
recoveries
is
> > > > something along the lines of "Media recovery complete, but
attempt to
open
> > > > with a restlogs will generate the error 'File 1 needs more
recovery
to be
> > > > consistent'.... and every time, it's because the person doing the
recovery
> > > > has only restored the datafile they thought was relevant, not all
DBFs
> > > > without exception.
> > > >
> > > > Regards
> > > > HJR
> > > >
> > > > <si_bendovi_at_hotmail.com> wrote in message
> > > > news:3A6E69A6.14DEA570_at_hotmail.com...
> > > > > I am trying to have database running in backup mode to be
> > > > > able to 'rollback' all transactions after backup mode was
> > > > > started. Goal is to be able to put database to the same
> > > > > state as it was before certain test. But I could not make
> > > > > recovery done without complaining that system tablespace
> > > > > needs more recovery. I am putting all tablespaces into
> > > > > backup mode, running my tests and after that doing 'shutdown
> > > > > abort'.
> > > > >
> > > > > recover until change (last change from v$backup);
> > > > >
> > > > > finish with warning, that system tablespace needs more
> > > > > recovery. I could not figure out what it means more :-). Any
> > > > > idea? Of course 'alter database open resetlogs' fails.
> > > > >
> > > > > Stan
> > > > >
> > > >
> > > >
> > >
> > > Just ran into this one yesterday. Definitely DID restore *ALL*
> > > datafiles, yet ran into the error above.
> > > No logical explanation. Managed to get around it (error moved to the
> > > rollback tablespace), files seemed to have change timestamps
(original
> > > 'backup' was made with cp (without switches) controlfiles copied
last.
> > > Is there any explanation for this.
> > > Also can only shutdown this instance (8.1.5.0.0 on solaris ) by
using
> > > abort. There seems to be an application process which is constantly
> > > polling the database, and thus creating havoc.
> > >
> > > Regards,
> >
> > How did you copy the controlfiles? Not just a cp I hope (I'm
assuming the
> > backup is done hot), 'cos the controlfile needs to be backed up
consistently
> > as well -alter database backup controlfile to '/bing/bong/blah.bkp'
being
> > the only known way.
> >
> > Regards
> > HJR
> >
> > >
> > >
> > > --
> > > Sybrand Bakker, Oracle DBA
> > >
> > > All standard disclaimers apply
> > >
>
>
>
> >
 |
 |