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

Home -> Community -> Usenet -> c.d.o.server -> Mangement of alert and listener logs - best practice?

Mangement of alert and listener logs - best practice?

From: Ed Stevens <nospam_at_noway.nohow>
Date: Thu, 20 Mar 2003 13:22:43 -0600
Message-ID: <ei4k7v41m32i4flrkhbqrjlhutva39d60p@4ax.com>


How do you guys handle your alrt.log and listener.log files, to contain their growth without losing too much history?

Early on on in our Oracle "experience" -- we started with 7.2 on NT 3.11. This seemed to have a lot of stability issues and I ended up writing a batch file to stop and start the databases on a weekly basis. As an aside, I built into the shutdown script some code to rename the just closed alert and listener logs, retaining several 'generations' of these files.

Now that I'm moving into the *nix world and there is no need to routinely bounce the databases, I'm wondering about what to do about these logs. I don't want to let them go and grow forever, but don't know how I might go about keeping them down to a reasonable, stable size and at the same time keep a reasonable amount of history. I particularly don't like the idea of just chopping them off at the top and potentially losing any msgs related to the latest startup, which could be several weeks (or hopefully, months) old. Or am I being too cautious in that regard?

SELECT experienced_advice
FROM newsgroup_participants
WHERE experience LIKE '%NIX'; Received on Thu Mar 20 2003 - 13:22:43 CST

Original text of this message

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