Solution : https://service.sap.com/sap/support/notes/181286 (SAP Service marketplace login required)
Summary :
When scheduling 'Update statistics for all R/3 objects' (RUNSTATS_ALL) or 'RUNSTATS on obj. needing new statistics' (RUNSTATS_ALR) in SAP's DB13 DBA calendar, a job is automatically generated for all or specific R/3 tablespaces requiring updates, without an option to exclude tablespaces individually. To overcome this, ensure the correct transport imports as per R/3 Release are done (Note 101217), and manually maintain a DB2NORUN table (as of Release 4.6A) to exclude specific tablespaces from RUNSTATS jobs systematically. This solution helps in maintaining optimal database statistics management in environments like DB2 MVS or OS390.
Key words :
additional key words db2 mvs, explicitly exclude individual tablespaces, dba planning calendar, prerequisites solution make, generated runstats jobs, explicitly excluded, runstats job, runstats_alert jobs, successfully imported, updated regularly
Related Notes :
| 132424 | DB2-z/OS: Optimizing access to the TRFC Tables |
| 116698 | DB2/390: Optimizing Access to Tables VBHDR, VBMOD, VBDATA |
| 113008 | DB2/390: Maintaining Catalog Statistics |
| 103707 | DB2/390: Transports for 4.0B |
| 101303 | DB2/390: Transports for 3.1I |
| 101217 | DB2 z/OS: Overview of transports and corrections |
| 83335 | DB2/390: Deadlocks, bad performance on cluster tables |
| 13719 | Preliminary transports to customers (note for customers) |