We are still recoiling from a partially successful R6 server upgrade (more about that later). One of the surprises we hit was when we started R6 immediately after the upgrade. The console window came up, showed the version line and the copyright line then seemed to freeze for about 4 hours. Evidently, it tries to convert all the shared mail object databases to the new ODS which can take a long time. The CPUs were almost idle. The disks were busy. We could occasionally see the timestamp on one of the SCOS files changing.
We had about 12 Gb of SCOS files and it took 4 hours. I found some similar postings but no answers when I first searched this forum. The other people who posted did not state whether they were using shared mail. One guy said he thought it was hung so broke out of it and then downgraded back to R5. One said he let it run until the next day. Another said it took 20 minutes on a Sun box.
Anyway, I hope this will take one surprise out of your R6 upgrades. Sorry I didn’t post this sooner.
p.s. We were going from R5.0.12 to R6.0.2CF1.
Subject: Confirmed! (was LONG delay after upgrading to R6 ( Shared mail ! ))
Wish I’d seen this post prior to our upgrade from 5.0.10 to 6.5. You would think that would be something they would put in the KB or the redbook or SOMEWHERE!We are running shared mail with our active file a little over 1GB. We likewise saw the tag lines and then nothing. We did suspect shared mail but after not seeing any activity for two hours, killed it and restarted the server. At least when it restarted, it did show a little more believable activity w CPU and memory. It chugged away for about 4 hours and finally came up.
Glad to hear this (not that you were stuck for so long but that we aren’t facing a 4 hour stall on our app server upgrade).
Subject: Ouch…that was painful
Even running fixup on the SCOS database (a 2.5GB one) took 45min 
After the upgrade, the server came up and sat there for 2 hrs; it really needs a progress message that says that it’s upgrading the SCOS DBs to the new ODS. You can watch the timestamps on the files in the data directory to see what it’s doing and it’s mucking w/ the SCOS files.