Lets not forget also the benefit of archive log to
allow only restored of a subset of files in the event
of a recovery. In noarchivelog, if you lose one file,
you'll typically need to restore the lot. In
archivelog, you'll typically need to restore just the
one
hth
connor
--- Deshpande,
With some of the 9i new features available with 9i, perhaps ARCHIVELOG
is the way to go for the most part. Being able to recover a corrupted
block, while the datafile is still ONLINE and available well,
does kind of cut down on your downtime a bit, doesn't it? :-)
Same thing with running
CHAN Chor Ling Catherine (CSC) wrote:
Hi,
Pardon me if I am wrong, I thought the only reason for the database to be in
archive log mode is so that I can recover the database up to the time when
the database crushes.
You are right except for ONLY. Another reason is the desire to take
What about the ability to be able to do point in time recovery?
What about the ability to be able to make a copy of a database without
having
to shut it down?
What about the ability to recover specific datafiles without having to
shutdown the entire database.
What about the ability to recover
I can read your question 2 ways, so let me answer it both ways...
If you are asking if you can only do a cold backup when in noarchivelog
mode, you are correct.
However, in archivelog mode you can do cold or hot backup. The procedure is
a bit different in archivelog mode, because of the
You can call them whatever you like, nothing in the world will save the
clueless person you describe below :-).
You are correct in saying it is a training issue, I personally use hot and
cold but think offline and online are just fine as well. The issue is that
the
mode "archive vs
But my concern is this. Say a DBA has been doing cold, noarchivelog mode,
backups for a year. Then, he gets this great idea (or direction) to put the
database in archivelog mode, but to still do cold (or offline) backups, so
all he changes in his backup/recovery strategy is the backup of the
I agree with your definitionsbut the cold backup in archivelog mode is
fundamentally different from one done in noarchivelog more (with respect to
online redo logs and control files) if you are in archivelog mode and want
to be able to do point in time recovery.
Robert G. Freeman - Oracle8i
Just to add to the controversy, I often make the
argument to developers/users/managers/etc that
noarchivelog does not exist.
In my opinion, 'noarchivelog' is like waving a flag
saying I stand an excellent chance of losing a whole
lot of data one day.
Some years ago at a place I worked, some
Title: RE: Should we say COLD or HOT backup OR ARCHIVELOG or NOARCHIVELO
Robert,
Let me disagree with you.
Cold *backup* is the same in archivelog mode and in noarchivelog mode.
The *recovery* is (could be) different.
Consider the following. I make a cold backup of a production DB, and
I agree... cold can be the same, but recovery is different.
RF
Robert G. Freeman - Oracle8i OCP
Oracle DBA Technical Lead
CSX Midtier Database Administration
The Cigarette Smoking Man: Anyone who can appease a man's conscience can
take his freedom away from him.
-Original
Unless you're database is being used exclusively for Oracle Internet
Directory, in which case Oracle Corp says that traditional methods of DB
backup and recovery are not applicable in most cases.
And since we're running Oracle ASR, I plan on keeping the RDS in
NOARCHIVELOG mode. We're already
Connor - Good points, but obviously there are exceptions. We have a data
warehouse that we keep in NOARCHIVELOG mode. After the weekly load we do a
cold backup. However, lately there has been talk of some updates during the
week, so that may have to change.
Dennis Williams
DBA
Lifetouch, Inc.
Here is en exception:
I happen to administer a couple of data mart databases, that are loaded once
or twice a month. Both run in noarchive log mode. This is how these have
been set up when we started back in 1998. We take cold backups after the
data load, table/partition analyze. It takes 5
Hi,
Pardon me if I am wrong, I thought the only reason for the database to be in
archive log mode is so that I can recover the database up to the time when
the database crushes.
For example, we do cold backup nitely. If the database were to crush etc at
2pm, I would be able to recover my
No no.. You are correct.
In my case, since no changes are made to the database other than the data
loads, and there are no issues about recovering from the last cold backup
the downtime involved, we can live with noarchivelog mode. That's all.
Cold backups with noarchivelog mode are useless
16 matches
Mail list logo
