Arnaud,
You could always make the accounting log file a softlink to a more forgiving location...
It probably would also make sense to do some kind of regular log rotation with the file.
Ted
At 10:39 AM 5/4/2004, you wrote:
Ted,
Now I realise you where certainly right ! Unfortunately I disabled accounting some times ago, as it leaded us to server crash, because /usr was full. At that time I did not knew how to direct it anywhere else as it's standard path, and afterwards forgot to reactivate it : like allways higher priority tasks ... Add to this that unlike computers I'm working first in - last out, and you'll get a nice mess ! Cheers.
Arnaud
*********************************************************************** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ***********************************************************************
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ted Byrne Sent: Tuesday, 04 May, 2004 16:16 To: [EMAIL PROTECTED] Subject: Re: TSM DB growing, but number of files remains the same ...
Arnaud,
>I believe what I have to do now is to build some solid queries to >explore our activity log...
Unless I'm mistaken, I believe that you may have misread Richard's advice. (Correct me if I'm wrong, Richard.) His recommendation:
>I stress accounting log reporting because it is the very best, detailed
>handle on what your clients are throwing at the server
Accounting log records are comma-delimited records written to a flat file called dsmaccnt.log, assuming that you have accounting turned on. If you don't, I would recommend that you turn it on now...
The accounting log records give a very detailed, session-by-session picture of the activity between the server and clients. It will be easier to parse and process than what you can get out of the activity log.
Ted
