Idea Details

Is there any option to change db2 metric (ts_used_pages_pct) to use our (safer) calculation?

Last activity 05-29-2019 07:27 PM
Britta Hoffner's profile image
02-15-2018 07:26 AM

created Idea for the below question so that Product Managment can review this and consider for a future release.

Is there any option to change db2 metric (ts_used_pages_pct) to use our (safer) calculation?

Question asked by @MichalKoscinski82325361 on Feb 13, 2018
Latest reply on Feb 15, 2018 by Marshall Leite

Hi,

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.