> being a dba is kinda fun. Once I actually got to start doing it, that
is.
Look Lisa, you keep that to yourself.
Under no circumstances should you *ever* let
a manager hear you say that.
JARed
"Koivu, Lisa"
<lisa.koivu@efair To: Multiple recipients of list
ORACLE-L <[EMAIL PROTECTED]>
field.com> cc:
Sent by: Subject: RE: rman restore & arclogs
[EMAIL PROTECTED]
12/03/01 11:31 AM
Please respond to
ORACLE-L
Thanks Tom. I did try removing the arclogs and then running a backup - no
complaints. The arclogs in question were still present in the catalog via
past backups. I'm guessing this is because the last scn of the last
backup was larger than the scn's included in the arclogs in question.
However, a crosscheck report caused failure for all those logs. Not a big
deal, but once this all goes into production I want to see all my reports &
lists sent to me every day with no "FAILURE" or anything of that nature in
it. Erring conservative is probably better anyway, unless i'm really tight
on disk.
Restoring is kinda fun :) I take that back, being a dba is kinda fun.
Once I actually got to start doing it, that is.
-----Original Message-----
From: Mercadante, Thomas F [SMTP:[EMAIL PROTECTED]]
Sent: Monday, December 03, 2001 1:56 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: rman restore & arclogs
Lisa,
I guess I'm lazy (or cautious) in that I would allow the first backup
to take this archive log files back to tape where they belong, rather
than determine (by running reports) which log files I may delete (by
hand).
The cautious part of me says that if Rman decided to back these
monkeys up within the first save set after the recovery, it may have
decided that it needs them for a future recovery. If you did remove
them by hand, Rman may complain that it was expecting them and did not
find them. Did you try this - remove one that was restored by the
recovery process and then tried a backup?
Depending on the kind of restore you do - a full, or a point in time
- the archivelog may be of no use anyway (a point in time makes them
invalid because you had to perform an "open db reset logs", while a
full restore could still use these again).
Glad you are at least experimenting with the tool before you put it in
production - it actually is fun to do a restore as it happens so
infrequently!
Good Luck!
Tom Mercadante
Oracle Certified Professional
-----Original Message-----
From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 03, 2001 10:30 AM
To: Multiple recipients of list ORACLE-L
Subject: rman restore & arclogs
Good morning all -
I've been practicing rman restores. It's a lot easier than I
originally thought. I've noticed that when you restore and the
arclogs are needed, it restores them. Which is expected.
However, when I take another backup, these arclogs are included
in the backup set. This is unnecessary in my opinion and makes
my backup files larger than they need to be.
Is it standard practice to just delete the arclogs that were
already in a backup set prior to taking the immediate backup
after a recovery? I can verify what arclogs are where in the
backup sets with a report.
Any comments are appreciated. Thanks
Lisa Koivu
Oracle Database Monkey
Fairfield Resorts, Inc.
954-935-4117
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
