Self-Solve Knowledge Search

Minimize Maximize
Migrating QC 9.x to QC 10
Title :
Migrating QC 9.x to QC 10
Document ID :
KM905016
Product - Version:
quality center 10.00 ;
OS :
Updated :
Wed Apr 09 12:14:18 GMT 2014
Summary :
Migrating Quality Center version 9.0 or 9.2 to Quality Center 10
There is a required process in order to migrate Quality Center (QC) 9.x to QC 10. Below there is the necessary information:
Standard process to upgrade to QC 10:
If Version Control is enabled on QC 9.x projects, after the migration process is needed to install the recent QC 10 patch and follow the instructions described on the patch 8 readme file (under the “Migrating Legacy Version Control Data” section). 
HP Quality Center 10 Installation Guide must be checked starting on page 20 in order to verify the supported environment for QC10
IN CASE BPT (Business Process Testing) module on QC 10 will not be used, you can use the same QC 9.x license to install QC 10. Otherwise, it is needed to get a QC 10 license from ‘licenses’ team, by opening a ticket routed to them.
Steps to upgrade:
1.       Repository on database is no longer supported; check your projects’ repositories are stored on file system, before migrating to QC 10
2.       Deactivate the projects on QC 9.x (using the “Deactivate project” button from Site Admin) before doing step 4 (take the backup to be restored on the new database).
3.       If QC 10 will be installed on the same server where QC 9.x resides, it is needed to uninstall first QC 9.x. Uninstalling QC 9.x does not delete any information on QC.
4.       QC databases/schemas (site admin schema and project schemas) and repository folder (default repository path: <system drive>/Program Files/Mercury Interactive/repository/qc) used by your QC 9.x system must be backed-up. This step is necessary no matter whether you will use other database or not on QC 10, as there is needed to have them as a copy of the info just in case needed.
5.       Restore databases/schemas from prior point on the new database server if you will use other database server for QC 10. This step is not necessary if you will use the same database server on QC 10.
For Oracle database, jump to step 8.
6.       If using SQL as database, there on the Installation Guide for QC 10, step 19, page 72, you need to choose between SQL Authentication and Windows Authentication. SQL Authentication is recommended. If SQL Authentication will be used with QC 10, it is necessary to create the “td” user on the database. Please refer to the “CREATING THE TD USER” document in order to create it on SQL: http://support.openview.hp.com/selfsolve/document/KM916912
If you know what is the password you had for this user on source database server, set the same while creating the user on the new database server. Otherwise, note the used password, as you will need to set the same on step 8c. 
7.       If using SQL as database and if used SQL authentication on prior step, then it is needed to run a couple of queries against every project schema and against the site admin schema once they have been restored on the database. This is in order to make the “td” user the owner of the tables on the new database:
 
EXEC sp_change_users_login 'Report'
EXEC sp_change_users_login 'Update_One', 'td', 'td';
 
8.       Install QC 10 pointing to the database that this version will use.
 
a.       On step 20 on page 73 in the “HP Quality Center 10 Installation Guide”, you have to set the database “Server name”, the user and password of the database administrator.
b.      Then, on step 21, page 74; you have to enter the Site Admin schema name of the site admin schema you just restored on step 5. This way, the installer will know that you want to use a prior site admin schema.
c.        For the Site Administration database schema password on step 21, page 74 on the attached QC 10 Installation Guide, use the same password you set while creating the td user on step 6 (if using SQL). If using Oracle, set on this field the password for the Site Admin schema restored on step 5. 
d.      Then on step 22, page 76, you will have two options. As you already have a database backup from step 4, you can use first option.
 
·         Upgrade the existing schema: will upgrade the restored database server (recommended)
·         Upgrade a copy of the existing schema.
 
9.       If you are using a new repository folder or server, copy your repository folder (don’t copy the “sa” folder) from you QC 9.x app server to the QC 10 app server. Once that QC10 is installed all project folders must be pasted from the QC 9.x server to the QC 10 repository. You can choose any domain on QC 10 server to store the projects, or create a new one from site admin. Once you have chosen the domain where you will store the projects on QC 10, you have to go to QC 10 Site Admin application, on “Projects” tab, and click over this domain that you chose. On the right of the window you will find the domain “Physical Directory” where you have to paste your project folders.
 
10.   Edit the dbid.xml file for every project if necessary. It is necessary if the path for the repository has changed from the QC 9.x server to the QC 10 server, or if the database server name has changed. What you have to check on this dbid.xml file is:
 
a.       <DBSERVER_NAME> (Database server name) where the database server has changed.
b.      <DB_CONNSTR_FORMAT> (where the database server name appears too, and has to be changed).
c.       <PHYSICAL_DIRECTORY> has to be checked too, because the drive (C: or D: or…) could be different between the servers. Check the domain too on <PHYSICAL_DIRECTORY> tab and do it the same that the project has on file system on QC 9.x server, that is the same that you saw on steep 9.
d.      For the <DB_USER_PASS>, create a dummy empty project (QC 10 Site Admin – Site Projects tab – New Project) and set this tab with the <DB_USER_PASS> info you will find on the dummy project. If you kept the same password for the ‘td’ user from source database server, you will find that it is not necessary to edit this tab, as it already has the right password.
 
11.   Log on Site Admin for QC 10.
12.   You need to restore every project, using the “Restore Project” button on Site Admin for QC 10, before to be able to upgrade them. If the projects are already there on Site Projects tab, right click and choose 'remove project' before being able to restore them using fresh edited dbid.xml file (step 10)
13.   Upgrade every project using the “Maintain project” button on Site Admin for QC 10. The maintain button has three options: Verify Project, Repair Project, Upgrade Project. These options needs to be applied on that order, starting with the verify option. The first two options (verify and repair) will run an “upgrade assessment tool”, made to prepare the database to be upgraded to QC 10.
Notes:
There is a document: "HP Quality Center Upgrade Preparation Guide” where you can find troubleshooting information and guidelines about possible problems that the Verify tool might encounter, as well as recommended solutions for repairing the problems.
After verifying, repairing and upgrading the projects, you can log on and start working on your new QC version.
On QC 9.x Site Admin, add the SHOW_REPOSITORY_OVER_DB parameter to Site Configuration with a Y (yes) value. On Site Project tab, Project Details tab, see the 'Repository on DB' information (YES/NO).
If your projects are stored on database (if value from prior step is YES), you need to have at least patch 11 for QC 9.2, or patch 26 for QC 9.0 in order to apply the instructions described under the “Tool for migrating the Project Repository from the Database to the File System” section on the QC 9.x patches readme file. In case you need this tool, open a ticket with us asking for latest patch for your QC version.
If you have some questions about the process to migrate your QC 9.x projects from database to file system or face some issue while applying this process, please open a support case with your questions to give you better assistance managing just one issue per ticket.