BPT DB inconsistencies found issue in upgrade process

  • Questions
  • BPT DB inconsistencies found issue in upgrade process
Question ID: 107267
0
0

Hi All,

We are transferring data from HP QC 10 to HP ALM 11.52 in that process i performed Verify,repair and Upgrade actions on project in HP ALM 11.52 here Verify and repair completed successfully but in Upgrade process i am getting error in verify again and project corrupted automatically.

Attaching error please check and suggest me how can i solve this issue to complete this upgrade.
![alt text][1]

Regards,
Praveen

[1]: /storage/temp/513-after-upgrade-process-verify-error.png

Marked as spam
Posted by (Questions: 11, Answers: 7)
Asked on November 15, 2016 9:58 am
6 views
Answers (5)
0
Private answer

Have you tried to run the repair tool again? This reference says that the repair tool will repair the issue. I generally tell my clients to run the verify, then repair manually that which the tool can't correct with the repair option. After the manual repair, run the verify again and if no manual intervention is required then to run the repair tool. Once the repair tool is completed (it should report all issues repaired), I then recommend repeating the verify, repair sequence until the verify returns a clean report with no issues, as I have seen the repair option create a new issue that another verify then finds. Once the verify has come back clean, then perform the upgrade.

If the project is truly corrupted as yoou say then you will need to start again with a fresh repository and a freshly migrated project schema in the DB. If the upgrade just stopped/ failed but the project didn't corrupt, then you can try a few cycles of verify and repair to fix the issues. It may be that the BP_PARAMs (says 9 instances) may need to be removed prior to attempting the upgrade. You would need to remove them from the DB component more than likely. I would try the verify and repair again first before trying a new repository and project schema though.

Hope this helps,
Dan

Marked as spam
Posted by (Questions: 0, Answers: 721)
Answered on November 15, 2016 2:09 pm
0
Private answer

Thank you for your response @Dan!

Before starting Upgrade process I ran Verify, Repair again Verify tool on project repository after completion of verify and repair the result is '' **NO PROBLEMS FOUND**'' in verify xml file. Than I started Upgrade process but end of the result in upgrade process is '' **ALM-U10003: The verification process detects additional problems in the upgraded project. The project is corrupted''** it took almost 1 hour to complete.

Yes I copied new repository again for restoring project and we deleted all version history tables data because of unable to perform '' Undo checkout'' process on the source project but we did not delete any other tables data.

Is there any effect on the upgrade process if we delete all VC_* tables data ?

Regards,
Praveen

Marked as spam
Posted by (Questions: 11, Answers: 7)
Answered on November 15, 2016 3:21 pm
0
Private answer

No there shouldn't be and if you are unable to check in the entities then they will need to be cleared from the tables (the tables need to remain but the entities in each row need to be cleared) prior to the upgrade process or the repair occurring, as the repair tool can't fix checked out entities. The issue you are seeing is with BPT though from the error you posted and it looks like something with the BPT parameters are missing.

Marked as spam
Posted by (Questions: 0, Answers: 721)
Answered on November 15, 2016 3:26 pm
0
Private answer

Ok

Thank you for answers @Dan..!

I cleared all entities in each row from the tables and did not found any checkout problem in verify,the problem is with BPT parameters missing.

Dan is there any solution for retrieving these missing BPT parameters from repository or any other source manually ?

I will try again by performing 3 to 4 times verify and repair process.

Regards,
Praveen

Marked as spam
Posted by (Questions: 11, Answers: 7)
Answered on November 15, 2016 4:39 pm
0
Private answer

Did you try to upgrade with a new copy of project repository and database? As Dan has mentioned, your error shows it will be fixed by the repair tool. Ask DBA to drop existing project schema and then restore it with a fresh copy. Then upgrade again with that new db and a fresh copy of repository.

Marked as spam
Posted by (Questions: 4, Answers: 8)
Answered on November 16, 2016 5:55 pm