Recently We have activated DSM DB monitoring for the one of mission critical Prod DB server and could see some of objects got created in the monitored DB
We observed heavy logging in the monitored DB and upon investigation we found that there are lots of inserts happening against DSM specific tables.
In 16+ hours, around 370 million inserts on ACTIVITY & ACTIVITY_STMT tables. In 10 mins of interval, It’s trying to insert around 1.8 million of rows on each table. So, We suspect that DSM contributes for logging overhead here.
PFB the case number for details about this issue and response from IBM
Case number : TS001622518
We would like to share the idea of moving all the operations specific to DSM Data collection (which are contributing heavy logging) from monitored database to monitoring database(Repository) Database or any other workaround. Ideally it should not have any impact to production (monitored) database.
Why is it useful?
|Who would benefit from this IDEA?|
How should it work?
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions