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

Home -> Community -> Mailing Lists -> Oracle-L -> when it will need to delete the alert log file

when it will need to delete the alert log file

From: Dash, Saroj (CAP,CEF) <Saroj.Dash_at_gecapital.com>
Date: Sun, 27 May 2001 20:05:17 -0700
Message-ID: <F001.00310D26.20010527194021@fatcity.com>

Hello all,

What could be the size of alert log file,so that it will need to delete the file in sun solaris UNIX,8.0.5.

Regards,
Saroj.

-----OE'ffbfZ[fW-----
ol: Jared Still [mailto:jkstill_at_cybcon.com] '-M"Zz: Monday, May 28, 2001 PM 12:11
^: Multiple recipients of list ORACLE-L OE-: Re: Deleting the alert.log when the database is up

Interesting, I hadn't realized this behavior had changed.

Jared

On Sunday 27 May 2001 18:10, Reardon, Bruce (CALBBAY) wrote:
> Hi,
>
> For information.
>
> At various times there has been a lot of discussion about deleting the
> alert.log.
>
> Looking through Metalink I found the following note which describes the
> behaviour change between 7.3.4 and 805 and above.
>
> Hope it is of help.
>
> Regards,
> Bruce
>
>
> Doc ID: Note:122401.1
> Type: BULLETIN
> Status: PUBLISHED
> Content Type: TEXT/PLAIN
> Creation Date: 18-OCT-2000
> Last Revision Date: 14-MAY-2001
>
>
> Problem Description
> -------------------
>
> The Oracle background processes has an open file descriptor on the
> alert.log.
> When the database is up and running it continually holds this file
> descriptor
> open. This was not the case in 7.3.4, but is true for 8.0.5 to 8.1.7.
>
> This poses the question: What if the database is up and the alert.log
> gets too large. Do I have to shutdown the database to release the open
> file descriptor on the alert.log, then deal with the large alert.log?
>
>
> Solution Description
> --------------------
>
> You are able to copy the alert.log while the database is up and running.
>
> 1) Create an empty file:
> (example: touch nullfile.log)
>
> 2) Replace the old alert.log with the new empty file:
> (example: mv nullfile.log alert<sid>.log)
>
> The running database experiences no affects when doing this.
>
>
> Explanation
> -----------
>
> Having the continual open file descriptor on the alert.log is intended
> behaviour for the database.
>
>
> References
> ----------
>
> [BUG:1388186] OPEN FILE DESCRIPTORS HELD BY ORACLE BACKGROUND PROCESSES
> ON ALERT.LOG FILE
>
>
> Additional Search Words
> -----------------------
>
> delete alert

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jared Still
  INET: jkstill_at_cybcon.com

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: ListGuru_at_fatcity.com (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).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Dash, Saroj  (CAP,CEF)
  INET: Saroj.Dash_at_gecapital.com

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: ListGuru_at_fatcity.com (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).
Received on Sun May 27 2001 - 22:05:17 CDT

Original text of this message

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