Unable to upgrade ALM project because of checked out entities
Question ID: 106950
0
0

There is a project that is presenting a challenge to migrate from 1202 to 1250. The repair tool is indicating it is because there are checked out entities. I have checked Requirements, Components, Business Processes and Tests and cannot locate the item that is registering as checked out. The report from Repair fails to shine an additional light on this either.

Marked as spam
Posted by (Questions: 122, Answers: 3)
Asked on July 8, 2016 5:06 pm
180 views
Answers (2)
1
Private answer

Check the database for tables that begin with VC_ . These tables house the cache information for the versioned objects. It is likely that at least one of these tables still contains data. Each of these cache tables can be cleared (purged) without loosing data that is in the project. Once cleared, the repair tool should be able to continue.

Marked as spam
Posted by (Questions: 3, Answers: 168)
Answered on July 8, 2016 5:07 pm
0
Private answer

There is also a table called VersionControl that houses version control information also, and Defects can also be checked out, since you didn't mention those in the list of modules you have checked. As a side note I have seen before where entities were checked in but the VC tables referred to in the prior post also contained entries that weren't cleared when the check in was checked-in, reversed, or undone and clearing that table entry resolved the issue.

Marked as spam
Posted by (Questions: 0, Answers: 770)
Answered on July 8, 2016 5:23 pm
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

X
Scroll to Top