"Terse" Database Log File

[Norman Biggar]

Is there any method of restricting the amount of information written to the database log file?

More specifically,
We are running with Stateless Appservers. Every time someone uses an AppServer it reconnects to the database using their USERID and Password. This produces an excessive amount of "Userid is now .... (708)" messages.

V9.1C Sun Sparc

 

[Olivier_Desmars]

Norman,

I have never heard of that kind of option, but it's obvious that it would be very nice if it would exists.

The 'must' would be to create a progress logfile analyzer which would filter the unwanted informations. A nice challenge

 

[toby.Harman]

I had a logfile parser in a previous life which proved very useful. The problem with logfiles is still that you cannot truncate them online (in a supported way!), which will mean that your appserver is going to cause you to re-start the database more frequently than you may want.

Logfiles are just text files, so an automated script which copies the logfile somewhere and then truncates it every night may be the solution. You can then search the logfile for "interesting" messages the next day!

One example would be (unix based)
grep -v "(708)" logfile > newlog