 |
 |
Archives of the TeradataForum
Message Posted: Sat, 17 Jan 2004 @ 15:51:32 GMT
| Subj: | | Re: Teradata Manager Services |
| |
| From: | | Harold D Kleven |
We have discovered that the TeradataManager / Administrate / Systems does, among other things, the authorization for the services routine to
monitor a particular system. This process must be taken while the TdMgr is receiving data directly from the DBMS, not running from a server itself
(localhost). While I was in the process of this discovery I also discovered that there is a potential for a "logon hang" for certain process of
TdMgr if both the userid and the role it is assigned have MONITOR privs. You should pick one strategy for assigning MONITOR priv (either by userid
or role) and not both! (it was causing "ghost" MONITOR sessions on one of our systems. Sessions could be seen from some views and not from others
but slowing chewed up all avail MONITOR session resources until we couldn't get any more! Then it was bring down services and TPA RESTART time.)
We got into that mess because we had MONITOR privs assigned by userid under 4.1.3 and we never took them off when we went to 5.0 and developed our
role strategy (a good strategy - partially implemented!).
| |
