When to Exclude Tablespaces from RUNSTATS, REORG and COPY (SAP Library

When to Exclude Tablespaces from RUNSTATS, REORG and COPY

You might want to exclude tablespaces from the process of updating statistics and raising alerts for several reasons.

DB2NORUN and DBSTATC

To exclude tablespaces from consideration in Update statistics for all SAP objects (RUNSTATS ALL) and RUNSTATS on objects needing new statistics (RUNSTATS ALERTS), do one of the following:

· Insert the tablespace name and database name into table DB2NORUN using transaction SE16.

· Insert the tablespace name and database name into table DB2NORUN manually using SPUFI.

· Table DBSTATC can also be used to exclude tables from RUNSTATS ALERTS. As soon as the ACTIVE flag in DBSTATC is set to N, no alert will be raised on this table. This implicitly excludes tables from RUNSTATS ALERTS.

Note

Setting the ACTIVE flag in table DBSTATC only covers RUNSTATS ALERTS. Excluding tablespaces from RUNSTATS ALL is only possible via DB2NORUN.

Caution

When the statistics for the excluded tablespace are not maintained, they continue to raise alerts. If you want to suppress this behavior, you must set the ACTIVE flag in DBSTATC to N for all tables within this excluded tablespace.

DSNACCOR Exception Table

SAP has exploited real time statistics and the stored procedure DSNACCOR since DB2 V7 (see CCMS Monitor Set in Monitoring and Performance in the SAP DBA Guide for DB2). The exception table of DSNACCOR will exclude any tablespace or indexspace in the subsystem for alerts on utility runs.

The DSNACCOR exception table replaces the tables DB2NORUN, DBSTATC, DB2REOTS, and DB2REOIX completely. While the old tables are still respected for compilation of jobs in DB13, you have the benefit of not receiving any unnecessary alerts in transaction RZ20, so it makes sense to port your entries in these tables to DSNACC.EXCEPT_TBL. In addition to this benefit, you are no longer restricted to objects within that special SAP system, which may be interesting if you run MCOD or have non-SAP objects - apart from the system catalog - in the subsystem.