Re: RECOVER DATABASE question again.

Hi, the problem that arises in your original method is that Oracle stops recording the occurrence of checkpoints in the headers of the online datafiles being backed up as a direct result of issuing the ALTER TABLESPACE BEGIN BACKUP statement.
When a datafile is restored, it has "knowledge" of the most recent datafile checkpoint that occurred before the online tablespace backup, not any that occurred during it. As a result, Oracle asks for the appropriate set of redo log files to apply should recovery be needed. After the datafile copy is completed, Oracle advances the file header to the current database checkpoint. This is done after the ALTER TABLESPACE END BACKUP statement is executed. In your case the datafile is now inconsistent, but the checkpoint info in the header file can also result in overlapping data from the redo log files that are applied during recovery.

Paul da Cruz

Connor McDonald wrote:
>
> Alexander Chupin wrote:
> >
> > Good day,
> >
> > We have database in archivelog mode.
> > Every weekend, when nobody work, our
> > operators copy database, redolog and
> > control fies to another server using
> > xcopy.exe command, without shutdown
> > server or other preparation for this
> > action (as alter tablespace xxx begin
> > backup,etc.).
> > Because it strategy of backup was
> > developed not by me, I'm interested
> > how I can to recover this instance
> > on the second server?
> > Now I tried the following.
> >
> > startup mount exclusive;
> > alter database recover database until cancel using backup controlfile;
> >
> > I received in trace file:
> >
> > ---------- begin of trace file --------------
> > Mon Jul 12 11:54:41 1999 -
> > alter database recover database until cancel using backup controlfile
> > Mon Jul 12 11:54:41 1999 - Media Recovery Start
> > WARNING! Recovering data file 1 from a fuzzy file. If not the current
> > file
> > it might be an online backup taken without entering the begin backup
> > command.
> > WARNING! Recovering data file 2 from a fuzzy file. If not the current
> > file
> > it might be an online backup taken without entering the begin backup
> > command.
> > WARNING! Recovering data file 3 from a fuzzy file. If not the current
> > file
> > [...]
> > WARNING! Recovering data file 36 from a fuzzy file. If not the
> > current file
> > it might be an online backup taken without entering the begin backup
> > command.
> > Media Recovery Log
> > ORA-279 signalled during: alter database recover database until
> > cancel using...
> > Mon Jul 12 12:31:06 1999 -
> > alter database recover database until cancel using backup controlfile
> > Mon Jul 12 12:31:06 1999 -
> > Media Recovery Start
> > ORA-275 signalled during: alter database recover database until
> > cancel using...
> > Mon Jul 12 12:32:10 1999 -
> > alter database recover cancel
> > Mon Jul 12 12:32:10 1999 -
> > Incomplete recovery done UNTIL CHANGE 1099617362232
> > Media Recovery Cancelled
> > Completed: alter database recover cancel
> > ---------- end of trace file --------------
> >
> > Production database now is operating Ok, while.
> > Can anybody tell me, what I must to do to recover
> > second database using archivelog file from
> > production database.
> > Is it available? Or I must send all files from second
> > server to nul.
> >
> > Thank you in advance.
> > WBR, Alexander.
>
> You have two options:
>
> hot backup -
> you MUST perform alter tablespace ??? begin backup and end backup for
> each tablespace whose files you copy
>
> cold backup -
> shut the database down and copy the files
>
> Anything else could leave you in a lot of bother
>
> Cheers
> --
> ===========================================
> Connor McDonald
> "These views mine, no-one elses etc etc"
> connor_mcdonald_at_yahoo.com
>
> "Some days you're the pigeon, and some days you're the statue."
Received on Wed Jul 21 1999 - 04:21:41 CDT