I don't know if anyone mentioned Solaris. Running Sun/Sparc Solaris 6&7 and
Oracle 8.1.7.1. A cron job filed shell script does a cp only, no touch,
then mails the old log to the DBAs. It works the same way as it did a month
or two ago when we went from 8.0.5 to 8.1.7: next time Oracle needs to
write something, it creates a new file.
----- Original Message -----
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Wednesday, July 11, 2001 8:05 AM
> Okay folks, I *knew* I wasn't crazy! thanks to Anita for finding the post
> that Bruce sent to the list, that had the metalink doc in it
>
> There was also a bug filed on it (which was closed as "not a bug") bug#
> 1388186
>
> It was filed for Solaris so this might just mean that the "feature" is
> Solaris specific, since people here are saying that they haven't seen it
on
> other platforms.
>
> We are on Solaris, but our scripts are written such that we don't rename
the
> alert log so I haven't been able to prove it one way or another.
>
> Rachel
>
> 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.
>
>
>
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> --
> Author: Rachel Carmichael
> 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).
--
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).
