Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Inheriting a "interesting" recovery process

Re: Inheriting a "interesting" recovery process

From: stephen booth <stephenbooth.uk_at_gmail.com>
Date: Fri, 4 Aug 2006 15:53:21 +0100
Message-ID: <687bf9c40608040753q25097c44gd38625da3e2e0f06@mail.gmail.com>


On 04/08/06, David Sharples <davidsharples_at_gmail.com> wrote:

> What does keeping the archive logs have to do with anything. Don't you keep
> all of them anyway?
>

I tend to keep the last 40 days (compress after 20 days then delete after 40), this is based on nightly backups. Unfortunately I've been in situations where the sysadmins have deleted the archived logs to clear space without checking with the DBAs that it was safe to do.

The problem is more management than technical. In some companies the DBAs are part of Infrastructure and so tend to have control of the Oracle Servers, if the sysadmins want to delete some files they have to talk to the DBAs first. In others the DBAs are part of Application Support and so are viewed as only having control of the application, if they try to specify backup strategies or say that certain files shouldn't be deleted they are ignored. I came accross one site where immediately after the hot backup the sysadmin would run a script clear out the archived logs destination directories (plus the bdump, udump and cdump directories) because he "was worried they might fill up the disk."

Stephen

-- 
It's better to ask a silly question than to make a silly assumption.

http://stephensorablog.blogspot.com/

 'nohup cd /; rm -rf * > /dev/null 2>&1 &'
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Aug 04 2006 - 09:53:21 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US