Hi,
I have just found the email I posted earlier about this in the List
archives.
To find it search for "when it will need to delete the alert log
file"
I can't comment on the accuracy with respect to Unix as don't use it.
Under NT as others have said you can just rename the alert logfile and a new
one will be created.
The note summary is:
Deleting the alert.log when the database is up
Type: Note Doc ID: 122401.1
Modified Date: 14-MAY-2001
Status: PUBLISHED
Platform: Unix Generic issue
Product: Oracle Server - Enterprise Edition V7
Regards,
Bruce Reardon
"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.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"
-----Original Message-----
Sent: Wednesday, 11 July 2001 5:06
To: Multiple recipients of list ORACLE-L
dunno about NT, I do know that it changed on Unix.. as per a thread here in
the not too distant past. I believe Anita had posted something on it.. and
that it WAS a change from prior versions.
I am an Oracle on NT ignoramus :)
>From: "Mercadante, Thomas F" <[EMAIL PROTECTED]>
>Date: Tue, 10 Jul 2001 10:00:34 -0800
>
>In 816 on NT, you can rename it any time you want.
>
>is this changing in 817 Rachel?
>
>Tom Mercadante
>Oracle Certified Professional
>
>-----Original Message-----
>Sent: Tuesday, July 10, 2001 1:27 PM
>
>depends on the version of the database you are running.. it used to be that
>yes, you could just rename it and Oracle would open a new one of the
>original name when it needed to write to it.
>
>In 8.? and above, you can no longer just rename it, Oracle now maintains an
>open file pointer to it, similar to the way it handles the listener log
>file. So you will need to do the same sort of tricks to the alert log as
>you
>
>have to do to the listener log (make a copy then copy /dev/null to the
>original)
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Reardon, Bruce (CALBBAY)
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).
