Please read Rama Velpuri's book
on Oracle Datbase backup and recovery
for an elaborate explanation with specific
examples.
Regards
Willy
either doing a recover until time, or doing recover until cancel - if you
don't know how many archived logs you actually have.
This is documented in the documentation under the title Incomplete Recovery.
I strongly suggest if you actually need to do this that you read carefully
through this documentation. As Howard Rogers is fond of saying this is
exactly the reason for the introduction for 5 way multiplexing of archived
logs in 8i. A good DBA *should* never lose an archived redo log. (I bet we
all have though <g>).
HTH
--
Niall Litchfield
Oracle DBA
Audit Commission UK
Quote:> if i lose some archive logs what can i restore back too?
> hypoteticly if i have 20 files and lose 15 file would i only be able to
> restore up to the 14 file? how does this work?
If I do a full backup of the database each night, after shutting it down
first. Do I need to keep backups of the archive logs before yesterdays?
If a disaster were to happen during the day, surely the only archive logs
needed would be from today?
Am I correct in my assumtion or am I missing something?
Jason
> either doing a recover until time, or doing recover until cancel - if you
> don't know how many archived logs you actually have.
> This is documented in the documentation under the title Incomplete
Recovery.
> I strongly suggest if you actually need to do this that you read carefully
> through this documentation. As Howard Rogers is fond of saying this is
> exactly the reason for the introduction for 5 way multiplexing of archived
> logs in 8i. A good DBA *should* never lose an archived redo log. (I bet we
> all have though <g>).
> HTH
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> > if i lose some archive logs what can i restore back too?
> > hypoteticly if i have 20 files and lose 15 file would i only be able to
> > restore up to the 14 file? how does this work?
1. Export the entire database every night. - this gives a logical backup for
cases like hardware failure.
2. Backup the database every night
3. Don't delete archives for 4 days.
we also import the export to our DR site daily as well.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
> If I do a full backup of the database each night, after shutting it down
> first. Do I need to keep backups of the archive logs before yesterdays?
> If a disaster were to happen during the day, surely the only archive logs
> needed would be from today?
> Am I correct in my assumtion or am I missing something?
> Jason
> > You can recover from your last good backup until the first gap in your
> > archived redo logs. This means
> > either doing a recover until time, or doing recover until cancel - if
you
> > don't know how many archived logs you actually have.
> > This is documented in the documentation under the title Incomplete
> Recovery.
> > I strongly suggest if you actually need to do this that you read
carefully
> > through this documentation. As Howard Rogers is fond of saying this is
> > exactly the reason for the introduction for 5 way multiplexing of
archived
> > logs in 8i. A good DBA *should* never lose an archived redo log. (I bet
we
> > all have though <g>).
> > HTH
> > --
> > Niall Litchfield
> > Oracle DBA
> > Audit Commission UK
> > > if i lose some archive logs what can i restore back too?
> > > hypoteticly if i have 20 files and lose 15 file would i only be able
to
> > > restore up to the 14 file? how does this work?
I like the idea of exporting the database but how long does the export take,
and how big is your database? (rough approximation)
We are running BaaN and it has a lot of tables approx 2500 per system, and
we have three systems in the database (live, test and standard) so all up
there are some 7500 tables. The tablespace holding the data is approx 11Gb
and the one holding the indexes is approx 10Gb.
I have a feeling this could take a long time to export?
Sorry if my questions are annoying and basic, but I'm still waiting for the
"guys with the checkbooks" (finance managers) to approve my Oracle
raining - glad I'm not holding my breath ;-)
Jason
> 1. Export the entire database every night. - this gives a logical backup
for
> cases like hardware failure.
> 2. Backup the database every night
> 3. Don't delete archives for 4 days.
> we also import the export to our DR site daily as well.
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> > Just another question regarding archive logs
> > If I do a full backup of the database each night, after shutting it down
> > first. Do I need to keep backups of the archive logs before yesterdays?
> > If a disaster were to happen during the day, surely the only archive
logs
> > needed would be from today?
> > Am I correct in my assumtion or am I missing something?
> > Jason
> > > You can recover from your last good backup until the first gap in your
> > > archived redo logs. This means
> > > either doing a recover until time, or doing recover until cancel - if
> you
> > > don't know how many archived logs you actually have.
> > > This is documented in the documentation under the title Incomplete
> > Recovery.
> > > I strongly suggest if you actually need to do this that you read
> carefully
> > > through this documentation. As Howard Rogers is fond of saying this is
> > > exactly the reason for the introduction for 5 way multiplexing of
> archived
> > > logs in 8i. A good DBA *should* never lose an archived redo log. (I
bet
> we
> > > all have though <g>).
> > > HTH
> > > --
> > > Niall Litchfield
> > > Oracle DBA
> > > Audit Commission UK
> > > > if i lose some archive logs what can i restore back too?
> > > > hypoteticly if i have 20 files and lose 15 file would i only be able
> to
> > > > restore up to the 14 file? how does this work?
Hey paranoia is good for you - how else would I know that they're all out toQuote:> I keep each backup for a week, i.e. one for each day of the week. This
also
> includes the volume where the archive logs are stored. so at any given
point
> I have full backups and associated archive logs for the last six days.
Also
> I have 3 monthly tapes, also full system backups. I have always thought
this
> would be enough, but then I am new to Oracle so I now have a touch of
> paranoia creeping in after your last post 8-).
We're not as large as you, but a direct export takes somewhere between 30Quote:> I like the idea of exporting the database but how long does the export
take,
> and how big is your database? (rough approximation)
Not at all, they are sensible questions from someone who obviouslyQuote:> Sorry if my questions are annoying and basic, but I'm still waiting for
the
> "guys with the checkbooks" (finance managers) to approve my Oracle
> raining - glad I'm not holding my breath ;-)
As far as the guys with the checkbooks go ask them to consider what the cost
of a days downtime for the entire system is if you have to spend that long
working out how to restore and what data they will have and what if any they
have lost during downtime. Then consider the cost of Oracle training.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
Thanks for your help, I find it is much more informative talking to someone
who is "out there doing it" rather than trolling through some crusty old
manual 8-)
Cheers
Jason
> Hey paranoia is good for you - how else would I know that they're all out
to
> get me <g>. I guess what I was getting at is if you actually delete the
> archive logs that are older than 1 day (using an os script or whatever) in
> order to preserve space, then if last nights backup didn't work or the
tape
> is unreadable the fact that you have tapes for the previous week is
> irrelevant. On our system I have to have three bad tapes before I'm in
> trouble.
> > I like the idea of exporting the database but how long does the export
> take,
> > and how big is your database? (rough approximation)
> We're not as large as you, but a direct export takes somewhere between 30
> minutes and an hour to produce a roughly 3.5Gb dump file.This is on a 3
year
> old NT box. Of course compressing and then copying this file across a WAN
> link for DR takes some time. Suck it and see would be my advice.
> > Sorry if my questions are annoying and basic, but I'm still waiting for
> the
> > "guys with the checkbooks" (finance managers) to approve my Oracle
> > raining - glad I'm not holding my breath ;-)
> Not at all, they are sensible questions from someone who obviously
> undertsands the kind of things he needs to consider. Annoying questions
are
> of the 'What are the default Oracle passwords - I can't be bothered to
read
> the manual' variety.
> As far as the guys with the checkbooks go ask them to consider what the
cost
> of a days downtime for the entire system is if you have to spend that long
> working out how to restore and what data they will have and what if any
they
> have lost during downtime. Then consider the cost of Oracle training.
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
1. Multiple archive log processes archiving same log file
Hi
We have notice that Oracle starts multiple archive writer even if
log_archive_max_processes = 1.
We understand the need for more than this limit if the system is very
heavily loaded. What we do not understand is why the archive writer
ARC1/ARC2 tries to
archive the same archive file (seq#) as ARCH0.
It would only make sense if they tried to copy a new or different
archive log file!
Can anyone give us an explanation to this phenomena?
(We are running Oracle 8.1.7.2 on Win NT sp 4)
2. PDoxWin 4.5, Help with 2 page form.
3. archive question --- too many archive logs generated during data load
4. ODBC access to VAX RMS files
5. How to check the corruption in online redo logs and archived logs
6. Summing two tables into a single cross tab file
7. Log Miner : Performance problem querying archived logs
8. Table v$log and archived log files ?
10. Reducing the Size of Archive Logs
12. HOW TO?? Archive Log Data and Email It