We are using UIM db2 probe on AIX. We found that there is a difference between measurement using our company internal tool and the probe metric - ts_used_pages_pct.
Below is a part of output from a db2 command:
$db2 list tablespaces show detail
... Tablespace ID = 1 Name = ***_32K Type = Database managed space Contents = All permanent data. Regular table space. State = 0x0000 Detailed explanation: Normal Total pages = 5912 Useable pages = 5856 Used pages = 4704 Free pages = 1152 High water mark (pages) = 4704 Page size (bytes) = 32768 Extent size (pages) = 32 Prefetch size (pages) = 32 Number of containers = 1...
Using our company internal tool we have: 80.33%, this is calculated from:
(Used pages) 4704 -------------------- = 80.33%(Useable pages) 5856
But when we check it on uim-db2 probe we have: 79,57%, this is calculated from:
(Used pages) 4704-------------------- = 79,57% (Total pages) 5912
Is there any option to change that metric to use our (safer) calculation?
CA Support suggest me to put this idea here.
Hello Michal, I have created an idea for this request for you. Please see https://communities.ca.com/ideas/235738440-is-there-any-option-to-change-db2-metric-tsusedpagespct-to-use-our-safer-calculation and vote for it.
The queries used to compute those values are hardcoded into the probe; it would take a feature request to have development investigate having those changed, which is probably why you were asked to come to the community forum. Unfortunately, this post is not an "idea" format; it's posted as a question, so development won't see this one. You would need to make a new post a use the "Idea" option (it will have a light bulb icon).
In the meantime, have you considered creating a custom checkpoint and deactivating our default checkpoint?
That's the way to go, as David said 'have you considered creating a custom checkpoint and deactivating our default checkpoint?'