I issued "show alert" command and the result showed me that I need to
clean things up:

2011-04-23 18:28:38.255000 -04:00
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0

......

I executed "purge -age 1440 -type alert" but nothing happened. The
records in the alert file are still there from April the 23d. My
understanding is that this is supposed to purge from alert log all
records older than 1440 minutes (1 day)? This does work for cores and
traces.

--
http://mgogala.byethost5.com

On Fri, 02 Sep 2011 13:35:40 +0000, Mladen Gogala wrote:

Manual purge (using vi) of log.xml and alert.log works like a charm.
However, that's not what I expected from adrci. It seems that I will not
yet give up my logrotate configuration.



--
http://mgogala.byethost5.com

On Sep 2, 7:54Â*am, Mladen Gogala <gogala.mla... (AT) gmail (DOT) com> wrote:
That's not a bug... Bug 6800147: ADRCI PURGE COMMAND DOESN'T WORK WHEN
DELETE ALERTLOG USING AGE OPTION

‽

Even more entertaining: Bug 12426625: ORACLE 11.2.0.2 CONFIGURATION,
ADRCI "SET CONTROL" AND "PURGE" DO NOT WORK

jg
--
@home.com is bogus.
71830 upside down means "retard" in Polish.

On Fri, 02 Sep 2011 11:00:09 -0700, joel garry wrote:




Well, alert log can be safely rotated using logrotate, but log.xml will
require some parsing. The purge command had no effect on log.xml, either.
Thanks Larry for the pathologically eclectic rubbish lister.
--
http://mgogala.byethost5.com