Will that adversely affect the system performance or DASD utilization?
No, QDBFSTCCOL runs on a very decent level, i.e. when adding or removing a
large amount of records, the statitsics may not be immediately up to date,
but this is in either way better than if the statistics are never updated.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
-----Ursprüngliche Nachricht-----
Von: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Maassel, John R.
Gesendet: Monday, 07.11 2016 20:30
An: MIDRANGE-L@xxxxxxxxxxxx
Betreff: Statistics collection
We upgraded from 6.1 to 7.2 over the weekend.
We started getting reports that some ETL jobs weren't finishing in the
normal amount of time. I'm attributing this to the new SQE and optimizer and
have been helping rewrite queries. While troubleshooting this, we found that
there aren't statistics on most of the tables involved, and the ones that
have stats are stale. Poking around in system values, I found that
QDBFSTCCOL is set to *NONE, which I think means that it isn't automatically
refreshing stats when the optimizer thinks it's needed. I think it's been
like that for a long time. Since the tables are rather large (~3 billion
records in one) I think the lack of statistics is probably a major factor.
Is that accurate?
I'm proposing that we set that system value to *ALL. Will that adversely
affect the system performance or DASD utilization? Should we do this during
a slow time (right after an IPL, for example) or can this be changed on the
fly?
Thanks,
--
John Maassel
Lead Programmer/Analyst - Food Products & Corporate Systems
________________________________
Notice from Bob Evans Farms: This e-mail message, including any attachments,
may contain confidential information that is intended only for the person or
entity to which it is addressed. Any unauthorized review, use, disclosure or
distribution is strictly prohibited. If you are not the intended recipient,
please contact the sender by reply e-mail and destroy all copies of the
original message and any attachments.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
