Why does rm_upgrade.bat terminated without error on Non-English environment?

Authors: Upgrade Troubleshooting Team
Build basis: CLM 3.x and later

A typical problem that rm_upgrade script can run into is on Non-English environment. The parameter -oldJTSContextRoot is set incorrectly for Non-English environment. This page is structured with instructions to resolve this particular issue.

Running qm_upgrade script

The rm_upgrade script upgrades Jazz Team Server version 3.0.1.x or 4.0.0.x to 4.0.1 or later. Here is an example on running rm_upgrade script on Windows and UNIX:

Example

Windows:

cd C:\Program Files\IBM\JazzTeamServer\Server\
upgrade\rm\rm_upgrade.bat -oldApplicationHome old_RM_install_dir\server\conf

UNIX:

cd opt/IBM/JazzTeamServer/Server/
./upgrade/rm/rm_upgrade.sh -oldApplicationHome old_RM_install_dir/server/conf

Symptom

The rm_upgrade.bat will be terminated without error message. The command window will then closed out immediately. However, there is no problem to run jts_upgrade.bat, ccm_upgrade.bat and qm_upgrade.bat. Only rm_upgrade.bat is failing in those upgrade scripts on Non-English Environment.

Resolution

The parameter -oldJTSContextRoot is set incorrectly for Non-English environment. You can resolve this issue by setting parameter -oldJTSContextRoot to jts.

A working example with correct parameters is shown below for Windows and UNIX.

Example

Windows:

cd C:\Program Files\IBM\JazzTeamServer\Server\
upgrade\rm\rm_upgrade.bat -oldApplicationHome old_RM_install_dir\server\conf -oldJTSContextRoot=jts -newJTSContextRoot=jts

UNIX:

cd opt/IBM/JazzTeamServer/Server/
./upgrade/rm/rm_upgrade.sh -oldApplicationHome old_RM_install_dir/server/conf -oldJTSContextRoot=jts -newJTSContextRoot=jts

Related topics: DeploymentTroubleshooting

External links:

Additional contributors:

 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.