Join / Log in
The IBM Db2 Automation Tool has introduced a new exception condition based on the catalog table SYSIBM.SYSSTATFEEDBACK. The SYSIBM.SYSTATFEEDBACK catalog table contains objects which are missing or have conflicting catalog statistics. With this new exception condition, you can save both time and resources by running a RUNSTATS utility on only the objects that require a refresh. Once the RUNSTATS utility has been executed, the row for that object will be removed from the SYSSTATFEEDBACK table.
Below is a screen shot of the new SYSSTATFEEDBACK exception condition you will see when creating an Automation Tool Exception profile. All you have to do is select the SYSSTATFEEDBACK condition under the “RUNSTATS recommendation for missing or conflicting catalog statistics” grouping to activate this condition. Then, before creating a RUNSTATS job during a build process, each object will first be checked to see if the object has a row present in the SYSIBM.SYSSTATFEEDBACK catalog table. If a row is found, a RUNSTATS job will be created for the object. If the object does not have a row present in the SYSIBM.SYSSTATFEEDBACK catalog table, processing will be skipped for that object.