MVSFORUMS.com

[grimpeur]

We have a partitioned tablespace in DB2 z/OS v8 CM.
One particular partition is showing incorrect information in the EXTENTS field in SYSIBM.TABLESPACESTATS
A Re-Org was run on the partition so that a compression dictionary would be built, which was successful and we can see from the VSAM dataset that the physical number of extents has reduced somewhat as a result of the compression. Still, the value in realtime stats has not updated.

Any idea why this might be? I would have thought the re-org would have updated the extents value. Image Copy and normal Runstats have also run since the reorg. I don't know if it's significant, but SYSIBM.TABLESPACESTATS indicates that the partition has never been load/replaced (it is updated with SQL inserts etc).

Migration from DB2 v7 to v8 CM was after the reorg.

I've tried google/ibm sites but can't find detailed enough info regarding how realtime stats works.

Thanks.

[grimpeur]

Just to add, it is possible that there has been no insert/update activity since the reorg

[videlord]

is the RTS started in your DB2?
check the RTS database status.

[grimpeur]

Yes, RTS is working for other fields and other tablespaces - it is just this particular TS (in fact this a a few related ones) that have incorrect extents recorded.

[videlord]

is this row updated or not? e.g. the REORG timestamp, the totalrows?
All are wrong or only column extents?

[grimpeur]

Yes the row has been updated as indicated by UPDATESTATSTIME. Reorg, Copy and Stats timestamps, and Total Rows are also all up-to-date.

[videlord]

The extents should be the actual extents of the linear vsam data sets. (if multiple data sets for non-partitioned tablespace, it will use the extents of the last data sets)

if you make sure the the extents in RTS table is wrong, contact your IBM support, open PMR

P.S., if you want to reduce the extents, alter tablespace PRIQTY before REORG