I don't think there is a way to do this. You cannot divide the
tablespace snapshot values by the number of containers to get a per
container value because, which containers are accessed and how
frequently ultimately depends on what data is accessed from the
database (e.g. a where clause may limit access to elements from only 2
out of 5 containers).
If your containers are on different devices, maybe an OS level IO
metric will give you some idea of how much IO is occuring on each
device.
eu****@profitlogic.com (Eugene) wrote in message news:<95**************************@posting.google. com>...
Is there a way to capture I/O statistics per tablespace container?
Or, as long as DB2 normaly stripes/rebalances data pages across
containers, the number of physical reads and/or writes from a
tablespace snapshot could just be devided by number of the
tablespace's containers to get a rough estimate?
Thanks,
-Eugene