Quality Center 10 to ALM 11 upgrade error

  • Questions
  • Quality Center 10 to ALM 11 upgrade error
Question ID: 104961
1
0

I am trying to upgrade a very large project from QC 10 to ALM 11. The upgrade is failing at different spots every time we attempt it and is not consistent where it is failing. Some background on the project, it is >100GB repository size (I know it is too big, we are working on splitting it out into smaller projects) The error that we are getting is below:

15:35:36 Upgrade failed on flow step ‘com.mercury.td.saserver.maintenance.upgrade.SmartRepositoryMigrationUpgrader’.
You can resume upgrade from this step.

15:35:36 Exception occurred. ALM-E10011: Actual upgrade failed com.mercury.td.saserver.maintenance.upgrade.SmartRepositoryMigrationUpgrader

15:35:36 Error: Migration to optimized repository has been failed. You can resume the migration process by starting the process again.

15:35:36 Stack: com.mercury.td.saserver.maintenance.upgrade.SmartRepositoryMigrationUpgrader.run(SmartRepositoryMigrationUpgrader.java:55)

Server exception. Process stopped

15:35:36 Exception occurred.

Finished

Does anyone know what might be causing our upgrade to fail every time?

Marked as spam
Posted by (Questions: 91, Answers: 0)
Asked on April 11, 2013 6:58 pm
28 views
Answers (1)
3
Private answer

The first thing that I would suggest for an upgrade that continues to fail is to turn on performance monitors for the server machine, so that you can see what is occurring when the upgrade crashes. I would suggest anytime you perform an upgrade to set the Performance Monitor in windows and pay special attention to the memory usage during the upgrade process. The bigger the project the bigger the memory will need to be on the QC server machine to handle the upgrade.

9/10 times if an upgrade is failing at different spots every time during the process then it is some kind of lack of memory, whether JBOSS or regular system memory.

When the upgrade errors out, are you able to log back into the server directly after the event, or is the server muted?
If your server is muted then it could be due to the JBOSS heap size being too small when the upgrade is performed, sometimes on super large projects like yours I have seen the QC server muted for exceeding the JBOSS heap. Another thing to mention here is that you will also need to monitor performance on your database server machine as well, since both the database server and the QC server are both accessed during project upgrades from QC10 both of these machines need to have sufficient available memory when the upgrade process is being run.

Also make sure to run the verify and repair and manually fix any errors that require manual intervention before the upgrade process so that you are sure that the project is ready for the upgrade to v11.

Marked as spam
Posted by (Questions: 0, Answers: 340)
Answered on April 11, 2013 7:01 pm
I tried upgrading the project again, this time I had the performance monitor turned on. It turns out that during the upgrade procedure the machine was using between 9.2 and 9.9 gb of ram. Since this machine has only 10 gb of memory we upgraded the memory on the machine to 12 gb. Since we did this the upgrade completed. Thanks
( at April 11, 2013 8:56 pm)