Has anyone else experienced long upgrade times when moving to San Diego?

[gunnergraves]

My Team is working through the Upgrade process to San Diego.  The upgrade time in our sub-production instances has increased around 6 hours for Rome to 36 hours for San Diego.  We are worried that this will not be acceptable to our end users when we upgrade Production.  Curious if anyone else has experienced this and if they were able to find a work around to increase speed.  

Thanks,
Gunner

[gunnergraves]

Looking further, it appears to be related more specifically to these Fix Scripts.  

[Charles Allison]

For us the San Diego upgrade from Rome was just shy of 14 hours.  Family upgrades before seem to come in under 4 hours.  This one is definitely longer.  There were changes to sys_archive_log and task.  Those used the most time.  There were also plugin updates too that ate up some time.  36 hours is excessive.  I would involve support.  

[gunnergraves · Accepted solution]

We have been working with support to identify the root cause of these scripts taking so long.  We have a high number of records in our sys_ui_message table caused by an apparent bug in the auto-translation functionality we use.  As the table is reparented, it is causing the long run time for the upgrade.  Support is helping us to clean up this table and we are hoping this will help with some other performance related ghosts we have been chasing.