Migrate QC DB and repository seperately
Question ID: 104483
0
0

Hi,

We have the following scenario:

QCServerA: 40 licences (QC10 running on Windows Server 2003)
QCServerB: 40 licences (QC10 running on Windows Server 2008)

We need to move licences from QCServerA to QCServerB (side question: Is the only option available when moving licences to move ALL from A to B in one migration, or can you gradually migrate?…..and will these work on B without any config?)…..however, I digress. In order to achieve this we need to move projects from QCServerA to QCServer B but have the problem where QC cannot import (using the GUI) qc projects > 2GB in size. The suggestion (from HP themeselves before they closed our support call and didn’t provide detail) was to migrate the DB and repositories seperately for large projects.

Are you able to provide step-by-step detail on how this ‘seperate’ migration can be done?

Notes – Repository is file system based not in DB
QCServerA db is Oracle9i Enterprise Edition Release 9.2.0.8.0
QCServerB db is Oracle10g Enterprise Edition Release 10.2.0.5.0 – 64bi"

Thanks in advance
Matt

Marked as spam
Posted by (Questions: 1, Answers: 0)
Asked on March 20, 2012 10:19 pm
56 views
Answers (1)
0
Private answer

Hi Matt,
The steps to migrate from one DB and QC server to a different DB and server would generally be as follows (the only issue may be when going from the older DB version to the newer, your DB should handle that setup and movement):

Disclaimer
While this example may meet the needs of your organization, the sole responsibility for modification and maintenance of the tasks is yours and NOT that of the Support Organization.
The intent of the information provided here is for educational purposes only.
As such, the topics in this document are guidelines only, and NOT a comprehensive solution, as your own environment will be different.
The appropriate system technical resources for your enterprise should perform all customization activities.
Best Practice dictates NO direct changes to any production environment. It is imperative to perform and validate ALL modifications in a test environment. Use the results and knowledge garnered from the test environment experience to create a customized Production Deployment Plan for your environment.

Older QC Server; Preparing Project for Upgrade
1. Make sure all objects are checked in for the Project if version control is being used
2. Deactivate Project in Site Admin
3. Disable Versioning
4. Verify Project
5. If necessary Repair the project either manually or with the repair tool. The verify project report will specify what can be repaired with ''Repair Project'' and what needs to be repaired manually.
6. Make a note of the ''Project Directory'' example, C:Program FilesHPQuality CenterrepositoryqcDomainProject

Transfer Project To New QC Server
1. Have the DBA copy the Project schema from Old QC Database to need QC Database
2. Copy the Project File Repository noted from step 5 above to the new QC Server file repository. The
default location should be something like C:ProgramDataHPALMrepositoryqcDomain

Finishing the Process on the migrated to server:
1. Open dbid.xml file in the project folder with a text editor like notepad or notepad++
2. Change , ,
, values to reflect the ALM 11 Environment. For the
value opening a dbid.xml for another project will give you this value.
3. Open QC Site Admin
4. Click Restore Project
5. Point to the dbid.xml file location (the one that was just edited).
6. Select which Domain to restore into.
7. Click Restore
8. Click OK
9. Click Close
10. The Project should now be listed in the Site Projects Tree in Site admin
11. Verify the Project
12. Repair Project if necessary
13. Upgrade Project if moving from an older version to a newer version
14. Repeat steps 11 and 12 as needed
15. Activate Project*

*Notes
After the upgrade, although the QC server may report the upgrade as complete, there is still a background process running to transform the file repository if an upgrade was performed (from one version to another). While the project is still usable, during this process, you will not be able to back up the project until this process finishes.

I hope this helps.

Marked as spam
Posted by (Questions: 0, Answers: 770)
Answered on March 21, 2012 3:27 pm
EyeOnTesting

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

X
Scroll to Top