SAP Note 434495 - DB6: Maintaining table statistics via transaction DB13

Component : CCMS/Database Monitors for DB2 Universal Database - DB2 Universal Database for Unix / NT

Solution : https://service.sap.com/sap/support/notes/434495 (SAP Service marketplace login required)

Summary :
When using SAP DBA planning calendar (transaction DB13) for database optimization via statistics updates, the necessity for job scheduling depends on the activation status of the system's automatic RUNSTATS on a DB2 system. If automatic RUNSTATS is inactive, explicit job scheduling is required through control table DBSTATC configurable via transaction DB21. This transaction, functional till SAP release 6.20, involves setting relevant table statistics, including object information (such as database object, type, owner, and database type) and statistics settings (such as active indicators and analysis methods). Specifically, active indicators 'N', 'R', or 'I' determine the processing suitability of tables, while analysis methods detail the types of statistics to be deployed. For the effective use of transaction DB21 settings in releases post-6.20, database commands might be necessary to apply desired configuration values, as direct settings via DB21 are constrained to certain releases.

Key words :
menu 'technical infrastructure -> method execution -> activate background dispatching', attirubte performance -> optimizer -> update threshold exceeded, sap schema database type = db6 statistics settings, update threshold exceeded alert, db2 update dbm cfg, usual ccms automatic functions, complete database-relevant area, index analysis methods            set, current check run detects, db2 updates dbm cfg

Related Notes :

984376DB6: Compatibility of online backup and other utilities
906071DB6: SQL0104N while executing R3szchk
891225DB6: SQL statement not coming back or poor performance
860724DB6: Configuration of the planning calendar for AutoRunstats
553621DB6: No history data in the application monitor (ST07)
536210DB6:Heavy parallel processing causes SQL errors
526822DB6: No statistics because of incorrect DBSTATC entries
524202DB6: dmdb6srp,dmdb6rts "Support for dbstatc-optio Vxxxx".
481685DB6: dmdb6srp and dmdb6rts ignore dbstatc-activ='I'
300828DB6: DBA Cockpit and Remote Monitoring for Releases < 6.10