Perform the following steps for each UNIX production database to be upgraded.
- Log on as ccm_root.
$ su - ccm_root
- Save manual customizations.
The upgrade program automatically saves your previous pt and notify directories,
and your previous migration rules files.
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.
- Run the upgrade program.
ccm_root$ CCM_HOME=/usr/local/ccm72x; export CCM_HOME
ccm_root$ PATH=$CCM_HOME/bin:$PATH; export PATH
ccm_root$ ccmdb upgrade [-w] database_path_1 database_path_2 -l logfile
The database_path must
be supplied as an absolute path. You can specify any number of database_path 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.
You can unpack a Windows database on a UNIX installation. The ccmdb unpack command
on UNIX can read pack files
that are created on a Windows system.
The resulting database might have Windows-style ASCII data in important
files which must be updated. The command ccmdb upgrade has
an option, -w, which converts the database files
in addition to performing the upgrade. All database configuration
files and controlled files of type ascii or its subtypes
are examined and converted to UNIX ASCII
format. The conversion affects controlled files in the archive and
cache only, as no work areas are updated.
Note: Because
this operation changes the contents of static, archived files, use
with caution. Always retain the original database backup in case any
problems are discovered.
For more information
about the upgrade program, see Running the Rational Synergy upgrade program.
- 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.
- After the database upgrade is complete,
look through the logfile that you created in step 3 and the ccm_upgrade.log file
created by the ccmdb upgrade command. Locate any
error or warning messages that require further action.
- 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,
not copy back your saved versions.
- 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
- 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:
- Start a Rational Synergy CLI.
- Export the Release 7.2 or later type
by using the following command:
ccm typedef
-export type_name -to xml_file
- Compare the Release 7.2 or later type
to the corresponding type that is in the database_path/old_types directory.
You can do so by comparing XML files.
- If you must reapply changes, start a Rational Synergy CLI
on the upgraded database with Release 7.2 or later,
and run 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.
- Merge Task Attribute customizations.
Settings and possible values for some task
attributes are held in the pt directory of your databases.
After you have used these instructions to upgrade a
database from Release 7.0, 7.1, 7.1a, 7.2
or later to
Release 7.2 or later,
you have 2 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.
- Merge notify customizations.
After you have used these instructions to
upgrade a database from Release 7.0, 7.1, 7.1a, 7.2
or later to
Release 7.2 or later,
you have 2 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.
- Upgrade DCM settings.
For complete information about upgrading a DCM database,
see Upgrading Rational Synergy Distributed clusters.