We are looking into the possibility of starting to use RUNSTATS profiles in our subsystems. We were surprised to find hundreds (in some subsystems) and thousands (in other subsystems) of RUNSTATS profiles already existing in the SYSTABLES_PROFILES catalog table, where RUNSTATS profiles are stored. It turns out that when we went to Db2 v12, the new STATFDBK_PROFILE zparm was automatically creating and updating these profiles whenever SYSSTATFEEDBACK was being updated.
I have a couple of questions:
1) Are you routinely using RUNSTATS profiles in your shop?2) If so, how has this new behavior that comes with Db2 v12 (the default for the STATFDBK_PROFILE zparm is "YES") affected your use of RUNSTATS profiles? Have you turned the zparm off so that you can have more control of the contents of your profiles? Or are you good with collecting more and more statistics based off of what the feedback table is recommending?
UPS6756, #1544403 Oleander Drive, Suite CWilmington, NC 28403 Phone: (910) 660-8649Fax: (910) 523-5504