Upgrading databases

This section explains how to upgrade your Rational® Synergy databases to Release 7.2 or later when upgrading to a new server.

About this task

Database upgrade requirements

Before you can use your Release 7.0, 7.1, or 7.1a databases with Release 7.2 or later, you must upgrade the databases from these previous installations and install Release 7.2 or later.

About this task

Follow these steps to upgrade Rational Synergy 7.0, 7.1, or 7.1a base model databases. These are databases that have not been customized by using a model installation from a model database.

Databases customized by using the Type Definition window, or by modifying control files, are still considered base model databases. These databases must be upgraded by using these procedures.

To upgrade model databases and databases that have been customized by using a model installation, contact IBM® Rational Software Support.

Unpacking the previous databases

To prepare your databases for upgrade, complete one of the following tasks for each database that you are upgrading to either unpack or load a previous database.

About this task

If you followed the instructions in Creating a database server, your new server is empty.

Unpacking previous database

If you used ccmdb backup or ccmdb pack to pack your database from the previous release, unpack the database into this new server by using Release 7.2 or later.

Procedure

Run the ccmdb unpack command.
ccmdb unpack packfile /to unc_database_path [-s server]
Note: If the pack file came from a UNIX server, you must use the -w option with ccmdb upgrade, as described in Upgrading base model databases to 7.2 or later.

Upgrading base model databases to 7.2 or later

Perform the following steps for each Windows production database to be upgraded.

Procedure

  1. Log on to the server as the CM Administrator.
  2. Save manual customizations.

    The upgrade program automatically saves your previous pt and notify directories, and your previous Windows migrate.rul file.

    If you changed any database-specific configuration files, make a backup copy of the files to save those changes.

    If you stored any process images in the Rational Synergy installation, save the image files, and then copy them into the new Rational Synergy installation, or to some other location.

    If you stored the images in the Rational Synergy installation or hosted them in the Rational Synergy CCM server, update the web server to host the files from the new location, and then update the URLs in Rational Synergy to reference the new URL if it has changed.

  3. Run the upgrade program.
    ccmdb upgrade -l logfile database_path_1 database_path_2
    Note: The database_path must be supplied as a UNC path. You can specify any number of database_path UNC paths for a list of databases to be upgraded.

    The upgrade program can take anywhere from a few minutes for a small database to many hours for a large database.

  4. The upgrade program unprotects the databases. Reprotect the databases by using ccmdb protect database_path, until you have completed the following steps and test the result.
  5. After the database upgrade is complete, look through the logfile that you created in 3 and the ccm_upgrade.log file created by the ccmdb upgrade command. Locate any error or warning messages that require further action.
  6. Restore manual customizations.

    If you changed any database-specific configuration files, such as triggers, merge the changes you saved in 2 into the converted databases.

    Note: You must merge these files with the Release 7.2 or later versions. Do not copy back your saved versions.
  7. Save the following directories to a separate directory for future reference.

    The ccmdb upgrade program saves selected files from your database before installing the new 7.2 or later files. After ccmdb upgrade completes for the first item on a database, save these files elsewhere to prevent them from being overwritten by future upgrades. The saved files are located under the database path.

    Save the content of the following directories:
    • old_types
    • oldbin
    • oldpt
    • lib/oldnotify
    Save the content of the following files:
    • lib/Unix/migrate.old
    • lib/Windows/migrate.old
  8. Modify standard types.

    If you modified any standard types in the database since the previous model installation, they are automatically exported to the database_path\old_types directory. Compare any modified type with the corresponding Release 7.2 or later type as follows:

    1. Start a Rational Synergy CLI session in web mode.
    2. Export the Release 7.2 or later type with the following command:
      ccm typedef /export type_name /to xml_file
    3. Compare the type to the corresponding type that is in the
      database_path\old_types directory. You can do so by comparing XML files.
    4. If you must reapply changes, start a Release 7.2 or later Rational Synergy CLI session on the upgraded database. Use the ccm typedef -modify command to reapply the changes. Do not perform a type definition import of the standard type from a prior release into the upgraded database without examining and understanding all the differences. In doing so, other properties of the type definition might revert to their definition from a prior release. These properties might be incompatible with Release 7.2 or later.
  9. Merge Task Attribute customizations.

    Settings and possible values for some task attributes are held in the pt directory of your databases.

    After you have completed these tasks to upgrade a database from Release 7.0, 7.1, or 7.1a to Release 7.2 or later, you have two pt directories under that database. To complete the upgrade, you must reapply the changes you made in your previous release to the new database_path\pt directory. Your previous pt directory was saved in database_path\oldpt.

    Note: You must merge these files with the Release 7.2 or later versions, not copy back your saved versions.

    You must also remember to restore any changes you made to the task type, such as adding attributes to the source_attrs attribute.

  10. Merge notify customizations.

    After you have completed these tasks to upgrade a database from Release 7.0, 7.1, or 7.1a to Release 7.2 or later, you have two notify directories under that database. To complete the upgrade, you must reapply the changes you made in your previous release to the new database_path\lib\notify directory. Your previous notify directory was saved in database_path\lib\oldnotify.

    Note: You must merge these files with the Release 7.2 or later versions, not copy back your saved versions. You must perform this merge if you use Rational Change, because it requires modified notify scripts.
  11. Upgrade DCM settings.

Results

Your database is now upgraded to Release 7.2 or later.

Testing the database upgrade

You have completed the upgrade to your production database. To test the result, start a Rational Synergy session and perform a number of operations. This topic includes a short list of operations.

About this task

If the database was manually protected after the upgrade, you must unprotect it before you can start a session. To run your tests, unprotect the database and start a session. Then, immediately protect the database again so that developers do not start to use the database until you have confirmed that it is working correctly. Repeat these steps each time you start a session for testing or for the post-upgrade actions described in Performing post-upgrade steps. Test each upgraded database with the following steps:

Procedure

  1. Start a Rational Synergy session on the upgraded database. On the Windows taskbar, click Start > All Programs > IBM Rational > IBM Rational Tools > IBM Rational Synergy to open the Start Rational Synergy window.
  2. Work through the explorers and Work pane in Rational Synergy.
  3. Create a task and assign it to yourself.
  4. Create a project.
  5. Create one or more source objects in the new project.
  6. Check in one or more of those source objects.
  7. Check out one or more of the source objects you checked in.
  8. View the history of one or more of these source objects.
  9. Use an earlier version of one of the checked-out source objects.
  10. Update your project, and verify that the version you used is replaced.
  11. Make sure you can build your own product with your normal build scripts.
  12. Sync your work area with your database.

Feedback