ccmdb upgrade command

The upgrade program converts a database from Releases 7.0, 7.1, 7.1a, 7.2 or later to 7.2 or later release. This command does not support individual model installs.

Synopsis

ccmdb upgrade
        [/f model_file]
        [/m model1,model2,...]
        [/url server_url]
        [/l log_file] 
        [/w] 
        database_path1 database_path2 ...

Uses

You must be the CM Administrator to run this command. You must be logged on to the database server.

You must upgrade a database from a previous release before you use it with the 7.2 or later release.

The database to be upgraded must be on a 7.2 or later release database server. You can upgrade a previous server, or you can first pack or dump the database from the previous server that is running the previous release. Then, you can unpack or load the database into a 7.2 or later release server.

Options and arguments

database_path1 database_path2 ...
This argument specifies the list of databases to be upgraded. These paths must be UNC paths to databases on the server where you are logged on.
/f model_file
This option specifies the model package file name. If you do not specify the model file, the default model name CCM_HOME\packfiles\base.model is used. Use of non-standard models is not documented in this information center.
This option value must be a UNC path.
[/m model1,model2...]
This option specifies the list of model names to be installed. The model name is the same name as the model project name in the model database. The default models that are shipped are the base and modsup models.
Note: Each model in the model file must have a unique name.
If this option is not specified, ccmdb upgrade reads the models that are currently installed on each database and upgrades them.
If this option is specified, the new list is used to override the current models. The sequence of the models that are listed in this option is the sequence of the models to be installed in the target database. All the current models that are not in the specified list are removed. As a result, specifying the option /m base causes the database to be upgraded to a Rational® base model, removing all custom models present in a previous release.
/url server_url
This option specifies the CCM server that the upgraded databases must connect to. By default, upgraded databases are connected to the server on the default port of the database server host. The default port is the one you specified as the CCM server port during installation. It is saved in the $CCM_HOME/etc/system_info.txt file.
To start a session on a database, enter cmsynergy /s server_url.
Start with either http:// or https:// to ensure that the server_url is a valid URL for a compatible server.
/l log file
This option specifies the log file where the log messages related to this upgrade command are written.
/w
This option checks all database configuration files and controlled files of type ascii or its subtypes and converts the line endings from Windows to UNIX conventions or UNIX to Windows conversions. This process occurs during the upgrade. The conversion affects controlled files in the archive and cache only. No work areas are updated.
Note: Because this operation changes the contents of static, archived files, use with caution. Always retain the original pack file in case any problems are discovered.

Example

Upgrade the two databases \\elite\ccmdbs\production1 and \\elite\ccmdbs\testdb to the 7.2 or later release, using the default model file. Log on to elite as the CM Administrator, open a command-line utility, and then issue this command:

 ccmdb upgrade \\elite\ccmdbs\production1 \\elite\ccmdbs\testdb        

Feedback