Steps to Upgrade from QC10.XX to QC/ALM 11.XX

Steps to Upgrade from QC10.XX  to QC/ALM 11.XX

1.    Deactivate the project in Global QC 10.

2.    Copy the projects’ repositories from the QC10 server to the ALM Server. Each project has the location of the repository at the project properties in the Site Administration web site.

3.    The DB team will start Copying the project schemas from the old DB instance to the new DB instance.

4.    Once the DB Schema and Project Repository copy has been completed please proceed to restore the repositories in the expected repository location in the QC/ALM 11 instance.

5.    Restore the projects

1. Login Site Administrator
2. Go to the Domain and right click and select Restore project
3. Modify the dbid.xml to match your project environment description before restoring (Example Below).

<?xml version="1.0" encoding="UTF-8"?>

<ProjectDescription>

                        <PROJECT_NAME>PROJECT NAME</PROJECT_NAME>

                        <DB_TYPE>3</DB_TYPE>

                        <DESCRIPTION>(CLOB) Created on 2009-04-15 13:19:40</DESCRIPTION>

                        <DB_CONNSTR_FORMAT>jdbc:mercury:oracle:TNSNamesFile=/home/tgangula/ALM_installation/tnsnames.ora;TNSServerName=qcap11</DB_CONNSTR_FORMAT>

                        <DB_NATIVE_AUTHENTICATION>N</DB_NATIVE_AUTHENTICATION>

                        <DB_NAME>proj_prod17_db</DB_NAME>

                        <DBSERVER_NAME>sa_db_host</DBSERVER_NAME>

                        <DB_USER_PASS>QCC:xxBoKEvANZnaZS1Zcsohjqq9E9hJaeJ3Z1khW8jWhQs=</DB_USER_PASS>

                        <PR_HAS_VCSDB>N</PR_HAS_VCSDB>

                        <PHYSICAL_DIRECTORY>/nfs/apps11/repository/qc/NBCU_105/PROD17/</PHYSICAL_DIRECTORY>

                        <USERS_QUOTA>-1</USERS_QUOTA>

                        <PR_IS_ACTIVE>N</PR_IS_ACTIVE>

                        <SAQ_IS_ACTIVE>N</SAQ_IS_ACTIVE>

                        <VM_REPOSITORY></VM_REPOSITORY>

                        <PR_LANGUAGE>English</PR_LANGUAGE>

                        <PROJECT_TYPE>Standard</PROJECT_TYPE>

                        <IS_TEMPLATE>N</IS_TEMPLATE>

                        <PROJECT_UID>ea7d50f0-ef75-4ffd-9e00-8fc192518707</PROJECT_UID>

                        <PR_SMART_REPOSITORY_ENABLED>Y</PR_SMART_REPOSITORY_ENABLED>

                        <PR_IS_QPM_AUTO_CALC_ENABLED>Y</PR_IS_QPM_AUTO_CALC_ENABLED>

</ProjectDescription>

1. From the site administrator restore projects using the “dbid.xml” file edited for all projects.

2.    If the project has been successfully restored proceed for upgrade, if not please refer troubleshooting section at the end on the document.

3.    Verify, repair and upgrade projects:

1. Right click on the project and select “Maintain Project”
2. Select Verify Project
3. After verification finished, select Repair project
4. After project repair, select Upgrade project

4.    After the upgrade has finished successfully please go the logs and verify if the project has been upgraded successfully.

5.    Activate the project.

6.    Login in and perform a smoke test to verify if everything is ok.

7.    If there was any error in Step 6 please refer troubleshooting section at the end on the document.

Troubleshooting:

1.    If you encounter issue with respect DB Permissions issue

a.    Contact DBA and they will be adding space to db

2.    Extra Index Issue

a.    Drop all the extra indexes available from the respective Project Schema

b.    drop index SCHEMA_NAME_HEM_DB.HG_COVER_LWR_IDX

3.    Verification failed with manual repair required

a.    Disable text search and upgrade the project

4.    Smart repository warnings / errors

a.    Manual removal for those files listed in the warning report. The files will be in the repository.

5.    Project is corrupted

a.    Remove and restore the same project

6.    Manual repair

a.    Check Manual Repair Tab

7.    Unable to update/ Lack or rights over the DBID.

a.    Run: chmod 777 [over that folder]

8.    The projects got frozen under "Maintenance" state.

a.    We have to change the state in the DB and then bounce the QC services.