Archives of the TeradataForum
Message Posted: Tue, 03 Jan 2006 @ 14:21:07 GMT
Well, I agree that TeradataManager puts out a lot of files into different directories and the installation and user guide is really, really sparse on explaining things or how to change configurations. Here's hoping that a newer version defaults to a simpler strategy or provides some information on how to change their defaults!
I believe that what you are seeing in that directory (C:\Documents and Settings\All Users\Application Data\NCR\TeradataManager\Databases\TD1) are the .ALS files, which contain some basic information regarding ALERTS triggered by your Alert Policies. (This is documented in the Teradata Manager User Guide, Chapter 3, Teradata Manager File Locations)
40K file size is the default for this type of file but I'm sure you can increase it's size somewhere in the registry, contact GSC to find out where to make the modification as the manual won't tell you! Or examine your alert policies and verify if you really need all of those alerts, obviously a site dependent situation. It would seem straightforward that you don't need those files after some period of time and a scheduled "maintenance" run could arbitrarily delete old files.
We've run TerMgr in server mode for several years now and really don't get too many files created that we can't manage manually; for example, only 2-3 of the .ALS files a month but that reflects the size of our site and the number of alerts we are sensitive to. The most difficult thing we found to keep straight was pretty much the same problem you're experiencing: all the different logs created in all the different directories and the different directories defaulted to for scripts we have run on a scheduled basis (Scheduled Tasks) and the scripts run as a result of an Alert Policy (in our situation, usually a BTEQ script).
Best of luck - hopes for a better new year/version!
Harold D. Kleven
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|