The following should be of assistance. http://support.openview.hp.com/selfsolve/document/KM1007069 I have it copied below.
I hope this helps.
John Scarpino, D.Sc.
Keep finding bugs!
Steps to Upgrade from QC 9.2 or QC 10.00 to ALM 11:
Pre-requisites:
- Check the following page for system requirements of ALM 11:
- Move the project repository from the Database (DB) to the File System (QC 9.2 only)
Note: Repository over DB is not supported in ALM11
Workarounds:
2. Install the latest QC patch for the QC 9.2 version which includes a tool to download the repository to the file system
- Before migration, deactivate all projects from the Site Administrator
Migration of QC 9.2 or QC 10.00 to ALM 11
- Backup the projects’ databases/schemas and Site administration database/schema (default name “qcsiteAdmin_db”) from the QC 9.x database server
- For SQL server:
- For Oracle Server:
- Backup the projects’ repositories from the QC 9.x or QC10.00 server. Each project has the location of the repository at the project properties in the Site Administration web site.
- Restore the project databases/schemas and the Site administration’s database/schema at the ALM 11 database server (if you are using a new database server)
Note: If upgrading QC, there’s no need to move projects databases/schemas however is important to take backups.
- Install ALM11, if you are using the same application server you must uninstall QC 9.2 or QC10.00
QC has 2 different databases, the project databases and the site admin database. When migrating, to keep users, user configurations, and site administration parameters you must install using the same database name that was used to restore the project in your DB server. Select “Upgrade a copy” or “Upgrade the existing schema” option during installation.
- Paste/Restore the repositories in the expected repository location in the new installation
- Restore the projects
a) Login Site Administrator and create a new empty project.
b) Go to the new empty project’s folder repository and make a copy of the dbid.xml file.
c) Remove your projects from the Site Administration (Reason: it has connections to the old database server). Do not delete the project because it will remove the project schema from the database server.
d) Go to the project’s folder and rename the existing “dbid.xml” file to “dbidold.xml”
e) Paste a copy of the “dbid.xml” file from the empty new project.
f) Edit the “dbid.xml” to match your project environment description as follow:
<?xml version="1.0" encoding="UTF-8" ?>
<ProjectDescription>
<PROJECT_NAME>** Put the project name **</PROJECT_NAME>
<DB_TYPE>XXXXX</DB_TYPE>
<DESCRIPTION>XXXXX</DESCRIPTION>
<DB_CONNSTR_FORMAT>XXXXX</DB_CONNSTR_FORMAT>
<DB_NATIVE_AUTHENTICATION>XXXXX</DB_NATIVE_AUTHENTICATION>
<DB_NAME>** Put the project schema name **</DB_NAME>
<DBSERVER_NAME>XXXXX</DBSERVER_NAME>
<DB_USER_PASS>XXXXX</DB_USER_PASS>
<PR_HAS_VCSDB>XXXXX</PR_HAS_VCSDB>
<PHYSICAL_DIRECTORY>** Put the correct path of the repository folder of this project**\</PHYSICAL_DIRECTORY>
<USERS_QUOTA>XXXXX</USERS_QUOTA>
<PR_IS_ACTIVE>XXXXX</PR_IS_ACTIVE>
<SAQ_IS_ACTIVE>XXXXX</SAQ_IS_ACTIVE>
<VM_REPOSITORY />
<PR_REPOSITORY_IN_DB>XXXXX</PR_REPOSITORY_IN_DB>
<PR_LANGUAGE>XXXXX</PR_LANGUAGE>
<PROJECT_UID>82a311c5-a440-4ecd-97a2-e97331a447XX</PROJECT_UID>
</ProjectDescription>
PROJECT_NAME: the name of the project, for example: NEW_PROJECT.
DB_NAME: the name shown in the database list, for example: NEW_PROJECT_DB
PHYSICAL_DIRECTORY: by default, this values is: <Drive>:\Program Files\Mercury\Quality Center\repository\qc\<Domain_Name>\<Project_Name_Folder>
PROJECT_UID: Keep the same amount of digits and modify the last two values to get a unique ID
PR_SMART_REPOSITORY_ENABLED should be changed from 'Y' to 'N'
Note: This step can be skipped if upgrading from existing qcsiteadmin_db as it already contains the project information.
7. From the site administrator restore projects using the “dbid.xml” file edited for all projects.
- Verify, repair and upgrade projects
- Right click on it and select “Maintain Project”
- Select Verify Project
- After verification finished, select Repair project
- After project repair, select Upgrade project
Notes:
- After upgrade the project you can not change its repository folder location, the reason of that is that there is a new feature in ALM that optimizes the project’s repository, there will be a job implementing this after upgrade the project for at least 1 day if the project is small and 5 days if the project is large.
Here is the information from the administrator guide (page 97):
After upgrading a project to ALM 11.00, ALM migrates the project repository directories to a new file structure in the default project repository location. If the migration process fails, you must fix the problems manually in the project repository. You can also configure the speed at which the migration is performed. For more information, see "Repository Migration" from Administrator Guide on page 120.
- Recommendation is to try on a Test server, then production
- After upgrade the project you can not change its repository folder location, the reason of that is that there is a new feature in ALM that optimizes the project’s repository, there will be a job implementing this after upgrade the project for at least 1 day if the project is small and 5 days if the project is large.
- Version Control Projects --> Upgrading Version Control
Upgrading Quality Center 10.00 version control enabled projects. Version
control enabled projects from Quality Center 10.00 cannot be upgraded to
ALM 11.00 while there are checked out entities. All entities must be checked
in in Quality Center 10.00.
Upgrading from legacy version control projects. To work with projects from
Quality Center 9.0 or Quality Center 9.2 that use version control, you must
first upgrade to Quality Center 10.00, migrate legacy version control data,
and then upgrade to ALM 11.00. For information on migrating legacy
version control data to Quality Center 10.00, see HP Software Self-solve
knowledge base article KM632120 (http://h20230.www2.hp.com/selfsolve/document/KM632120).
These documents may be useful:
Installation Guide ALM11.00_Installation.pdf
User Guide ALM11.00_User.pdf
Administrator Guide ALM11.00_Administrator.pdf
What is New ALM11.00_WhatsNew.pdf
Upgrade Best Practices ALM11.00_UpgradeBestPractices.pdf
