I thought it would be good to be a little proactive and handle any
issues before they became a problem. Your right, I should just forget
about monitoring things and play computer games until I get a call the
database is down or a tablespace filled up. Just Kidding!!! I could
ignore all the messages about the old database, but the log was
filling up so fast and growing large that I didn't want to have to
weed through the garbage to determine what was important. It's easier
if a log has an old date on it and hasn't changed recently then I
pretty much assume I don't even need to bother opening it.
Daniel Morgan <damorgan_at_exxesolutions.com> wrote in message news:<3F157469.4715D1B9_at_exxesolutions.com>...
>
> I think you should follow Oracle's advice.
>
> Instead of dealing with errors in a log file? So what? Deal with errors affecting clients and servers? What is not working properly and what is the error message received in SQL*Plus?
>
> If nothing's broke ... don't try to fix it.
Received on Thu Jul 17 2003 - 10:24:02 CDT
