Archives of the TeradataForum
Message Posted: Fri, 16 Apr 2004 @ 15:55:51 GMT
You've hit the cause of this problem squarely on the head. This scenario often happens when your application runs through a middle-tier and it is that middle-tier that logs on to Teradata - often staying logged on for days at a time.
A few solutions come to mind (and may be you need to use a combination of the them)
1) tailor your Access Logging. rules so that you don't log so many sql requests. I accept this may not be feasible depending on your reasons for logging the requests for.
2) if you're on V2R5 then try using the Query log. Again this is dependeont on release of Teradata and your requirements.
3) What a number of sites have done is to create another "acclogtbl" table in a separate database and change the PI. On a regular basis copy the contents of dbc.acclogtbl to your own and then purge dbc.acclogtbl.
Ward Analytics Ltd: Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|