Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    3
  • Subscribers subscribers
    9
  • Views views
    414
  • Users 0 members are here
Related
Options

Unable to trace ALM/repository directory for 17.1 or 24.1 versions. Having problems migrating from 17.1 to 24.1. Need help.

Anand Mahadevan

Hi All,

Am very new to QC, and we have an existing QC instance with 17.1 version. And I am working on upgrading Microfocus 17.1 to Open text 24.1. Am basically upgrading on the same machine. Am unable to take a backup of ALM/repository directories to restore projects after upgrade. 

These are the steps am following: 

1. Take backup of 17.1 by doing these two:

a. SQL Server > DB > Project > tasks > backup. 

b. ALMQC SiteAdmin page > Projects > Export to project file. 

2. Uninstall the 17.1 version.

3. Install 24.1 version with "Upgrade a copy of the existing schema" option. 

4. Am stuck at upgrading the projects now. If I access the old projects or upgrade them via UI - it says schema version is different, so its failing. 

24.1 installer doc talks about dbid.xml file, and I cannot trace where it is. 

Any help would be really appreciated. Thank you.

  • Verified Answer

    +1

    Can you attach a screenshot of the error.   Something doesn't line up in your description of the steps.

    If you did an in-place upgrade, and the project DBs are still on the same SQL server, then the Verify Project, Repair Project and Upgrade Project tasks should function.  Can you confirm whether you ran the verify project task against these projects and whether they ran without errors.

    The dbid.xml file is stored under each project's repository folder on the file server. It would only be relevant to this situation if you had moved the projects (db or repository) to a different server or location.  If that isn't the case, then the dbid.xml file should be fine as is.

    Machine Data Systems, Opentext business and technology alliance partner

    Follow Us on LinkedIN for the latest news, live webinars and more

  • 0 in reply to 

    Thank you for the quick response @Milan. 

    I actually did not specify few details like OS Upgrade, SQL Server Upgrade, etc. 
    I had my ALMQC running in Windows Server 2012, and I had to upgrade that to supported versions for 24.1. As part of that that process, I kind of messed up with the DB. And my upgrade was picking the older versions of Microfocus DB. 

    So, when I verified/repaired/upgraded projects in the UI, it showed me an error saying there is a schema difference between the projects. And that was the problem. So, I had to re-do it, and things went fine after that. 

    Thanks for your help anyway. Appreciate it.

  • 0 in reply to 

    No problem, glad that it worked out.

    Machine Data Systems, Opentext business and technology alliance partner

    Follow Us on LinkedIN for the latest news, live webinars and more

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.