Paul, I used to do this while my db is up and running but I have never deleted or renamed the log file. When the size of the log is more than say some megs then I used to open the file and cut the information say of few months back and paste in another file saving the original alert.log file. I am not sure if it can be renamed or deleted while the db/listener is up and running. On 6/10/05, Paul Vincent <Paul.Vincent@xxxxxxxxx> wrote: > > OK folks - please help me out with this old chestnut: > > When the listener log, and the database alert log, start to reach > unwieldy sizes, it's time to either delete the log, or - better - rename > it, so that Oracle will start a fresh one. But the question of whether > this can be done "on the fly", whilst the listener or database > (respectively) are still running, or whether you have to stop the > listener or shutdown the database instance before doing so, seems to > depend on which version of Oracle and which operating system are > running. > > So, by way of clarification, can anyone give a definitive answer to > these questions: > > Is it safe to delete or rename the listener log file whilst the listener > is still running, for Oracle 8i under Windows 2000 Server? And how about > deleting/renaming the database alert log file without shutting down the > instance, under the same configuration (8i, Windows 2k)? > > Same question for Oracle 9i under Win2k ? > > Same question for Oracle 8i under Solaris? > > Same question for Oracle 9i under Solaris? > > If there's a clear consensus on these answers, this would be a handy FAQ > answer! > > Regards, > > Paul > > > Paul Vincent > DBA > UCE Birmingham > paul.vincent@xxxxxxxxx > -- > //www.freelists.org/webpage/oracle-l > -- Thanks & Regards, T. Onkar Nath Ph : +91-9826728111(Cell) to_onkar@xxxxxxxxx onkarnath.tiwary@xxxxxxxxx -- //www.freelists.org/webpage/oracle-l