Thanks for this! Appears that this set of tables is in versions as far back as 10.1.0.2...testing prior to the actual upgrade would seem to be important here :) On Fri, Feb 14, 2014 at 12:52 AM, Chris Dunscombe <cdunscombe@xxxxxxxxx>wrote: > Hi, > > The upgrade was from 11.2.0.3 but I expect it will effect any upgrade to > 11.2.0.4 and also any upgrade to 12c from a version prior to 11.2.0.4. > > Cheers, > > Chris > > > On Wednesday, 12 February 2014, 15:48, Hemant K Chitale < > hemantkchitale@xxxxxxxxx> wrote: > And we tell our customers / managers that upgrade duration is not > related to the volume (size of the database). Was this upgrade from 10.2 > or 11.2 ? > > Hemant K Chitale > http://hemantoracledba.blogspot.com > > On Feb 12, 2014 11:36 PM, "Chris Dunscombe" <cdunscombe@xxxxxxxxx> wrote: > > Hi all, > > Just in case you've not come across it there's a potential gotcha when > upgrading to 11.2.0.4. We hit it a couple of weeks ago and I believe it > affects all platforms. > > The issue is caused by the database upgrade script, catupgrd.sql, > partitioning the statistics history tables, wri$_optstat_histhead_history > etc. So if you've got a lot of data in these tables, either because you're > keeping a lot of history or the automatic purge job (runs in the > maintenance window) isn't clearing the data down, then the partitioning > can take many hours and hence the upgrade takes many hours. > > The exact time all depends on your hardware and the amount of data in > these history tables. Generally the biggest table is > wri$_optstat_histhead_history. > The 11.2.0.4 readme doesn't make any reference to this > > HTH > > Cheers, > > Chris > > > >