Space: History - Tables and Indexes (DB2 UDB for UNIX and Windows)

Note

The following section is only valid for RFC-monitored systems.

You can access history data on tables and indexes by calling the DBA Cockpit and choosing Space ®History ®Tables and Indexes in the navigation frame of the DBA Cockpit.

A Set Selection Criteria dialog box appears in which you can limit the result set displayed according to the following criteria:

Field	Description
*Filters*
Tablespace Name	Name of the tablespace
Table or Index Name	Name of the table or index
Table or Index Size	Size of the table or index
*Display Options*
Sort by	Sorts the tables or indexes by Growth, Size or Name.
Maximum Number of Rows	Number of rows to be displayed

Example

To display the first hundred tables or indexes with the highest growth, choose Growth in the Display Options group box and enter 100 in the Maximum number of rows field.

When you have made your selections and chosen OK, the History – Table and Index screen appears with the following information:

Column	Description
Object Name	Name of the table or index
Object Type	Table or index
Tablespace Name	Tablespace to which the objects belong
Size (KB)	Size of the table or index
Changes Size (KB)	Average change of space used by table or indexes
REORG Check Date	Date of the last REORG check, for example, the date when RUNSTATS ran using program dmdb6srp.
REORG Check Time	Time of the last REORG check, for example, the time when RUNSTATS ran using program dmdb6srp.

If you want to display delta values between available measurements, select a row and choose This graphic is explained in the accompanying text Details. Alternatively, you can double-click the selected row. The table will be displayed again with the following difference: Columns with the heading Changes... are renamed with Delta...

If you want to change the selection criteria, choose This graphic is explained in the accompanying text Set Selection Criteria.

Caution

The values displayed on the History – Tables and Indexes screen are sometimes not correct. The reason is that these values are calculated based on DB2 system catalog information. To achieve good results, we recommend that you run RUNSTATS weekly.

If database tables contain VARCHAR or LOB columns, the specification of the size may be too small because the consumed space for VARCHAR and LOB columns can only be estimated.

History data is only retrieved for tables and indexes of schema SAPR3.

Caution

The date and time of the last REORGcheck and the last RUNSTATS should be the same. If this is not the case, you should update the statistics using the DBA Planning Calendar.