Ahh! Thanks for the insights!
i'd love to get some more details on the other prereqs of the RT monitoring script too.
what does not function, if e.g. the stogroup is not created, etc.
In my case, the customer would behead me, if I sheepishly would run this script in his production database for 5000+ users. So every change, be it so insignificant as possible, has to be approved, go through chance control and so on.
So just implementing DMC on a admin pc and running it against prod is a no go.
Cheers
Roland
------------------------------
Roland Schock
Distinguished Engineer
ARS Computer und Consulting GmbH
Muenchen
------------------------------
Original Message:
Sent: Thu September 17, 2020 06:02 AM
From: KAI DING
Subject: Use administrative task scheduler (ATS)
Hi Rajesh,
ATS is a protection mechanism for event monitor, and is strongly recommended when possible.
Consider this scenario: If console is down unexpectedly, event monitor would still be working on the monitored DB. In such case, ATS is a good protection to help turn off event monitor automatically, so that protects DB from unnecessary data generation and performance downgrade.
ATS itself is a light-weight assistant for event monitor, and would not have much performance impact on DB.
I hope it answered your question. Please let me know. thanks.
------------------------------
KAI DING
Original Message:
Sent: Mon September 14, 2020 11:46 AM
From: Rajesh ChandraMohan
Subject: Use administrative task scheduler (ATS)
Hi Team,
Just wanted to understand the importance of ATS in event monitor profile. What if I don't use them and collect data? Will it have any performance impact on the monitoring database? Too many changes to monitoring database (introduing systools tablespace etc) might be restricted in production databases.
What is the limitation for not using ATS and its impact ? Can some one explain so I can check. For now I am testing without ATS.
------------------------------
Rajesh ChandraMohan
------------------------------
#Db2