Error encountered running upgrade scripts for CLM (4.0.5 to 5.0 M3)
When referring to the draft upgrade guide for CLM 5.0 M3 (beta) found here:
https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/roadmap_clm_upgrade.html
I ran the upgrade scripts for step 12. the JTS upgrade script succeeded. However, the CCM and QM upgrade scripts did not succeed. Instead, the following errors quoted below were encountered. I realize this was encountered for a beta release. However, the steps contained in the draft upgrade instructions are very similar to established upgrade procedures for prior releases. Has this issue been encountered before? And if so, does anybody know the resolution?
Thanks!
|
5 answers
Hi Gail,
By adding one user and one admin account to every project, I completed the CCM upgrade script successfully. However, the RQM script still throws these similar errors. I have attached the results below. Any additional ideas would be greatly appreciated. I am continuing to investigate on my end.
The only difference in the upgrade process followed this time was when I updated the statistics of four tables:
Could there be anything else that might be causing this issue?
Thanks,
Jacob Huang
Comments
Jacob Huang
commented Apr 02 '14, 10:35 a.m.
----- EDIT -----
There was one other difference with this upgrade. This time, we were upgrading directly from 4.0.0.1 instead of from 4.0.5.
|
HI Jacob -
The upgrade from 4.X to 5.X includes the separation of RM storage from the JTS. This requires that you make a copy of the JTS database to establish it as the new RM database and run a number of repotools commands. These repotools commands will be wrapped into a single script later in the release but as of Sprint 3, we are having everyone run them individually. We try to alert people to the latest information on the Upgrading tab of the Product Download pages. For example: Rational Team Concert 5.0M3 Upgrading Tab The InfoCenter has not yet been updated.
However, I am not sure this is the cause of the error you are seeing. Can you retry the upgrade and post again with the details? Thanks!
Gail Burati
|
Hi Gail,
I attempted to restart the the upgrade taking your suggestion to create a copy of the JTS database. This did not work. I continue to receive similar errors when running the CCM upgrade script. I have included a copy of the errors received in "Step 1" of the upgrade script below. I would be grateful for any suggestions pertaining to this issue in CCM.
|
Hi Jacob -
You are hitting repotools -addTables error upgrading - an issue with upgrading archived projects with no members. You can workaround this issue by adding a member or an admin to the archived projects. We hope to fix this issue soon - see Investigate an active migration fix for defect 262994.
Let me know if that solves your issue and if you hit anything else - thanks!
Gail
|
Hi Jacob -
I'm afraid I can't help with this one - the best thing will be for you to open a PMR, For information on creating a PMR see How do I create a PMR? Good Luck!
Gail
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.