![]() But there is a typical pattern we came across. You still may ask yourself: Why is he writing so many words instead of explaining the root cause here? Please read on here in case you need to skip stats gathering (dictionary and/or fixed objects stats) during AutoUpgrade:Īs Daniel has proven now, with newer versions of AutoUpgrade, you indeed can skip fixups PRE and POST upgrade.Īnd actually with the most recent version of AutoUpgrade, we don’t do the Fixed Objects Stats gathering after upgrade anymore. But of courser in cases where the Fixed Objects Stats gathering takes hours, that is certainly acceptable by you I’d assume. It may take a bit longer compared to a case where stats have been refreshed beforehand. This is not complicated – and of course the upgrade will progress than without the stats gathering you’ve skipped. The first remedy in such cases is to skip the fixups AutoUpgrade does. 01:29:24.716 INFO Finished FIXUP - FixUpTrigger.executeFixUp ExecuteSql.quickSQL(ExecuteSql.java:571) = trace start =Įrr message: Process abort was requested for query. 01:29:24.696 WARNING This thread was interrupted while waiting for the following query to finish [DECLARE SYS.DBMS_STATS.GATHER_FIXED_OBJECTS_STATS In the cases I came across in the past months, AutoUpgrade failed in two cases as it ran into a timeout when it hit 12 hours! 13:30:21.831 INFO Executing SQL [DECLARE But when the stats gathering for fixed objects consumes now 30 minutes or an hour, or even more, than something is wrong. But based on experience, I’d say that everything between 1 and 5 minutes is pretty fine, even a few more minutes may be tolerable. It may be very relative what “long” means. Please see also Daniel’s blog post about how to gather fixed objects stats efficiently after the upgrade with AutoUpgrade. Thanks to Mike Hallas for his explanations and insights. Hence, we recommend for ages to refresh Fixed Objects Statistics a week or so after the upgrade. It requires the application to be up and running. But indeed, gathering statistics on fixed objects right after the upgrade doesn’t guarantee representative values for all fixed objects. This is usually representative as the database and the application(s) is/are operating for a while. We gather statistics on fixed objects before upgrade. And sometimes, when you refresh them, problems go away. Or rely on the ability and available resources of the automatic stats gathering job.įixed Objects Stats are collected when the database gets created. Hence, it is either your duty as a DBA to refresh them from time to time. Please be aware that the database does not track staleness Fixed Objects Statistics. Gathering stats makes only real sense when the database is warmed up, the application is running – and after several hours or even a few days, you trigger the stats collection. ![]() ![]() Photo by Ayse A on Unsplash Why “Fixed Objects Stats”?įixed objects are essentially X$ tables or structures.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |