Re: Incomplete Recovery

Cold backup takes too long. What I was trying is to save time to restore (copy) files. I found by making tablespace files read only that checkpoint is made to file even when in backup mode. Error of CKPT process was:

• SESSION ID:(5.1) 2001.01.24.23.02.56.041 ORA-01110: data file 2: 'C:\SW\ORANT\DATABASE\USR1ORCL.ORA' ORA-01114: IO error writing block to file 2 (block # 1) ORA-27072: skgfdisp: I/O error OSD-04008: WriteFile() failure, unable to write to file O/S-Error: (OS 5) Access is denied.

Since there is possible to do incomplete recovery to change only after file is copied, I have to all the time recover to the last change, which I am trying to avoid. I have no idea how Oracle handle consistency of those tablespace files in case copy takes very long time!? I was thinking files are not touched by server, but they having headers updated even in backup mode!
I guess solution to this maid be what Jeremiah wrote:

alter database recover database using backup controlfile until cancel; (apply no logs)
alter database recover cancel;
alter database open resetlogs;

I was using just command 'recover database' in server manager.

Thanks,

    Stan

Brian Peasland wrote:

> Stan,
>
> I must be missing something here...
>
> To me the easiest way to revert to a state right before your test is to
> perform a cold backup of that system before you do the test. After the
> test, just restore everything from your cold backup. No worrying about
> complete/incomplete recovery and all that.
>
> HTH,
> Brian
>
>
> si_bendovi_at_hotmail.com wrote:
> >
> > 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
>
> --
> ========================================
> Brian Peasland
> Raytheons Systems at
> USGS EROS Data Center
> These opinions are my own and do not
> necessarily reflect the opinions of my
> company!
> ========================================
Received on Wed Jan 24 2001 - 23:58:16 CST