Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 05 Dec 2005 @ 23:54:17 GMT


     
  <Prev Next>   <<First <Prev
Next>
Last>>
 


Subj:   Re: SESSION DISCONNECTS
 
From:   Robert D Meunier

Teradata Manager allows you to abort sessions that have been idle for a given amount of time. In the V2R6 documentation you can look in the Teradata Manager manual in Chapter 14 Using Alerts to Monitor Your System:

Using Alerts for Session Management

The built-in actions <Abort Session> and <Lower Priority> can be used to perform automatic session management on your Teradata system.

Example 1

For example, if you want to abort sessions that sit idle for more than 30 minutes, do the following:

1 In the Alert Policy Editor, go to the Sessions tab.

2 Select the Idle for (Minutes) event.

3 Change the Above value to 30, and select <Abort Session> from the drop-down combo box.


These settings cause a session to be aborted when all of the following are true:

. The session has been idle for more than 30 minutes, and

. The session is running in the DBC/SQL partition, and

. The UserName of the session is not on the Exceptions list.


You can set it up to exclude specific users, so you might be able to get the person that set up the Alert to change it to exclude you from the list.


Robert Meunier



     
  <Prev Next>   <<First <Prev
Next>
Last>>
 
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023