Upgrading from 8.3 to 10.1.1 - upgrade stuck?

[teverard]

Not seamless at all.  We have had nothing but issues at every turn.  Now it looks like I might not be able to upgrade at all.  We have quite a large content store (200gb) and our dev and qa environments just do not come close in size.  Because of the disparity I had a copy pf the production content store created in the QA environment so that we could test the upgrade prior to actually doing it to get timings for a production downtime, as we have external clients that access our production to pick up reports and need to communicate to them appropriately. 

I verified that this was a good copy by bringing it up on one of our qa servers.  It is a perfect duplicate.

Well we started the upgrade at 3:19 pm EST yesterday and the log has not been written to after this line shortly after start at 3:25. 

CM-SYS-2215 A Content Manager internal PRECACHEINITACTIONS task started.

This step took less than a minute in dev every upgrade I attempted (several), but that content store is only 3.5 gb - the total upgrade took a 1/2 hour.   Cognos assured me that the upgrade does not touch any output during this process, which is at least 80% of our 200gb production store.  We are not upgrading the reports at this point either(left default), so I do not understand what could be taking so long.  I have been searching the net, but no luck yet finding similar stories.  So I thought I would post this here.  At minimum future upgraders will see this experience.  I will have to wait till Monday to engage IBM, and I am just going to let the upgrade go this weekend to see if it ever does complete even if it does appear stuck.  I remember people saying at IOD that this part can take a really long time and to just let it go even if it looks stuck.  This timing is ridiculous and not acceptable for our production environment, but it would be nice to see it successful.  That fact that is has written no lines since this step sure looks like it just died.

[teverard]

This is for future googlers. Java too small for this size content store.  Raised it to 4gb (64-bit) got us pass this issue. 

No memory errors.  No dump files.  Just Oracle queries indicating they are waiting on the client and CM Service just never starts.