Comments below.
HJR
--
--------------------------------------------------------------------------
Opinions expressed are my own, and not those of Oracle Corporation
Oracle DBA Resources: http://www.geocities.com/howardjr2000
--------------------------------------------------------------------------
"Dave A" <dave_and_vanna_at_hotmail.com> wrote in message
news:sveuurnfguv63c_at_corp.supernews.com...
> I'd hesitate to say that this wrong... OK, I will -it's wrong: :-)
>
> The database datafiles were in backup mode for a week. Daily backups
> continued to go as usual, but the files remained in backup mode the entire
> week.(They didn't know the files were in backup mode)
>
> Altering the datafiles out of backup mode during recovery isn't the issue.
> The issue is that SCN numbers are frozen while the files are in backup
mode.
> After the data loss and restore(of the files), Oracle wanted the archives
> since the beginning of when the files were put into backup mode. At this
> point the datafiles were not in backup mode. The problem was that from
> Oracle's perspective there had been a week long backup.
>
> --
> Dave A
>
OK, I see the problem. It is of course total bollocks, since as we both
know (and as Oracle should) the file is perfectly up-to-date (at least to
the point at which it was backed up). My error and misunderstanding, and
hence the usual profusion of apologies.
The trouble is of course that in *reality* the only required files are the
ones from the time it was backed up. The problem is simply that the control
file doesn't correctly identify the file as being in hot backup mode. I
wonder if there's a way to directly update the thing to make it correctly
realise the situation? Did you ring Oracle support? -and if so, what did
they say??
I'll have to make enquiries, because this is a crappy situation to find
yourself in.
Regards
HJR
>
> "Howard J. Rogers" <howardjr_at_www.com> wrote in message
> news:39f68c49_at_news.iprimus.com.au...
> >
> > "Dave A" <dave_and_vanna_at_hotmail.com> wrote in message
> > news:svcj7t935mb9e6_at_corp.supernews.com...
> > > Howard, what you say *should* be true, but it isn't always. Consider
a
real
> > > world example that has one company in dire straights right now. The
backup
> > > software correctly backs up the database (hotbackup), but does not
alter
the
> > > tablespaces out of backup mode.
> > >
> > > The tablespaces remain in backup mode for a week.
> > >
> > > The database crashes and a file is lost. The file is restored from
last
> > > night's backup. The needed archive logs will be those generated
immediately
> > > after the last backup prior to the tablespaces getting left in backup
mode(a
> > > week ago), not those generated immediately after the beginning of last
> > > night's backup.
> > >
> > > In this real world example, someone deleted an archive log (bunches of
em
> > > actually) that hadn't been backed up at all by mistake. They are
trying
to
> > > figure out how to recover with a gap in the archives. Good luck.
> > >
> > > Oracle doesn't actually need the archive logs from a week ago, it just
> > > thinks it does and will insist upon it's way.
> > >
> > > Dave A
> > >
> >
> > I'd hesitate to say that this wrong... OK, I will -it's wrong: have
they
> > tried 'alter database datafile X end backup'? That's all that's needed
to
> > persuade Oracle that the file doesn't really need recovery.
> >
> > It's covered in the Backup and Recovery course materials (available for
> > download from www.geocities.com/howardjr2000) in chapter 5, under the
> > heading 'failure during hot backup'.
> >
> > Regards
> > HJR
> >
> >
> > > --
> > > Dave A
> > >
> > >
> > > "Howard J. Rogers" <howardjr_at_www.com> wrote in message
> > > news:39f53cfb$1_at_news.iprimus.com.au...
> > > >
> > > > <oratune_at_aol.com> wrote in message
news:8t24f6$h83$1_at_nnrp1.deja.com...
> > > > > In article <8t23p1$gbl$1_at_nnrp1.deja.com>,
> > > > > woodsyj_at_my-deja.com wrote:
> > > > > > I have read that once you backup a database, you can delete the
archive
> > > > > > logs from the disk. How do you cooridinate this with Oracle.
Here
is
> > > > > > an example of what we have done. We have moved from a 3 disk
> > > > > > configuration to a 6 disk configuration. When we did this, we
moved
> > > > > > our archive log destination to another disk. We also moved all
> > > > > > existing arhived logs. When I tried to do a backup, Oracle was
still
> > > > > > looking for the files to exist in their original location.
Shouldn't
I
> > > > > > be able to just get rid of the older archives? How do I tell
Oracle
> > > > > > that they have moved or that they no longer exist on disk? Any
help
on
> > > > > > the subject would be greatly appreciated.
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Sent via Deja.com http://www.deja.com/
> > > > > > Before you buy.
> > > > > >
> > > > >
> > > > > That would apply to a cold backup, not a hot backup. You should
not
> > > > > delete archive logs generated just prior to a hot backup as you
may
> > > > > need these in the event of a crash.
> > > >
> > > > That's not true. Provided you have all archives from the moment you
started
> > > > the hot backup cycle, and assuming that backup cycle completed
successfully,
> > > > you *can* dispense with prior archives (if you are brave or foolish
enough).
> > > > You never need to supply archives from a time prior to what you just
> > > > restored.
> > > >
> > > > Regards
> > > > HJR
> > > >
> > > >
> > > >
> > > > If you had performed a cold backup
> > > > > all files would have been synchronized and there would be no need
for
> > > > > the archive logs prior to the backup.
> > > > >
> > > > >
> > > > > --
> > > > > David Fitzjarrell
> > > > > Oracle Certified DBA
> > > > >
> > > > >
> > > > > Sent via Deja.com http://www.deja.com/
> > > > > Before you buy.
> > > >
> > > >
> > >
> > >
> >
> >
>
>
Received on Thu Oct 26 2000 - 03:56:37 CDT
