Re: [SOLVED] missing alert.log mystery (it's not what you think)

From: Wolfgang Breitling <breitliw_at_centrexcc.com>
Date: Mon, 16 May 2011 17:44:25 -0600
Message-Id: <58775BF2-A4C1-4D4C-B698-632C0945983A_at_centrexcc.com>

I have for years renamed the alert log on a weekly basis, and eventually gzipped it, in order to keep it reasonably sized. Oracle just starts a new alert log. Granted, I haven't done a direct bzip on it but that should be no different - except maybe, if the bzip takes a while and oracle tries to write to it while it is open by bzip. I haven't verified on 11.1.0.7 but on 11.2.0.2 that rename still works and Oracle creates a new alert log with the original name ( alert_instance.log ) so I am pretty confident it does also work for 11.1.0.7. In contrast to. e.g. the listener log, which you must not rename. There I do a cp to a new file followed by cp /dev/null > listener.log.

On 2011-05-16, at 1:50 PM, Charles Schultz wrote:

> On May 6th, the original alert_TEMDEV.log was bzipped and removed by a cron job. Usually we check to see if it is open by another process (ie, fuser), but somehow the stars must have been aligned or something. Anyway, we had an orphaned inode.
>

--
http://www.freelists.org/webpage/oracle-l

Received on Mon May 16 2011 - 18:44:25 CDT