Archives of the TeradataForum
Message Posted: Thu, 21 Mar 2002 @ 08:37:10 GMT
Assuming that you have accesslogging active on the TCRM user ids then it would be fairly accurate to use the combination of the sessionid,logdate,logtime to identify what SQL has been sent in the time frame that you are experiencing excessive resource utilisation.
AccessLog would have multiple entries for the user,session,logon date and logontime combinations-partly due to logging level applied on the user and as you have said that the userid and session id can be logged on for 7 days. However, each request sent will be distinguishable by the logdate and the logtime, and the other combinations mentioned. You could then find the latest query recorded in accesslog for that sessionid and this is very likely to be the query you are concerned about-unless it has just finished and the next query has started! and then it is a question of reading the log entries between two time frames to find the likely cause.
Alternatively, I understand that DBQM/TBQM can capture the sql requests-I do not know if you have this at your site.
Hope this helps.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|