CLMUpgradeScripts < Deployment

Engineering Lifecycle Management Wiki - Deployment

Community information and contribution guidelines

TWiki > Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > CLMUpgradeScripts

Revision 16 - 2015-05-27 - 16:58:04 - Main.sbagot

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! <img src="" alt="" width="50" height="50" align="right"/> Running the upgrade scripts
Authors: [[UpgradeTroubleshootingTeam][UpgradeTroubleshootingTeam]] <br>
Build basis: CLM 3.x and later
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>
This page discusses common issues which are occured when running the CLM Upgrade Scripts.
When running the upgrade script files to upgrade CLM applications, you might run into these common issues:

---++ CLM common upgrade questions

This section is currently in progress and will discuss running upgrade scripts in a distributed environment.
<!---
   * [[DistributedEnvironment][How do I run CLM upgrade scripts in a distributed environment?]]
   * [[DifferentArchitectures][How do I run the CLM upgrade script workaround for distributed deployments with different architecture (32-bit vs 64-bit)?]]<br> --->

---++ Known issues
Below are some common issues incurred when running the upgrade scripts prior to step 0:
---+++ Old Jazz Team Server version could not be determined
The Jazz Team Server upgrade script might fail with the following error:
<verbatim> CRJAZ2124E The old JTS version could not be determined. Verify that the oldJTSHome is pointed at the correct installation and specify the version using the old JTSVersion parameter. </verbatim>
For more information on this error navigate to [[OldJTSVersion][JTS Upgrade Script fails with "Old JTS version could not be determined" error]].
---+++RM_upgrade.bat terminated at startup
The RM_Upgrade.bat might be terminated at startup in non-English environments. For more information on this behavior, navigate to [[NonEnglishEnvironment][RM_Upgrade.bat is terminated in Non-English environments]].

---++ Additional steps in the upgrade script
AFter you have moved past step 0 of running the upgrade script, you might incur issues at the following steps:
   * [[UpdateConfigurationFiles][Update configuration files (CCM, QM, JTS)]]
   * [[AddDatabaseTables][Add database tables (CCM, QM, JTS)]] 
   * [[UpgradeDwSchema][Upgrade DW Schema (JTS)]]

---++ Troubleshooting
When the upgrade scripts run, each is executing a set of repotools commands. If the scripts fail, adding in [[http://www-01.ibm.com/support/docview.wss?uid=swg21322003][repotools trace]] can help identify why the script is failing.

---++ Where do I go from here?  
If you are unable to resolve your issue using the available online resources, please open a service request with IBM Rational Support. Refer to [[DataCollectionandSupportResources][Additional Troubleshooting Resources]] for further details.<br>

---+++++!! Related topics: 
   * [[DeploymentTroubleshooting][DeploymentTroubleshooting]]

---+++++!! External links:
   * None

---+++++!! Additional contributors: Main.WilliamChen, Main.BrettBohnn

---+++++!! Questions and comments:

<sticky></div></sticky>

Deployment.CLMUpgradeScripts moved from Deployment.CLMUpgradeScript on 2013-05-08 - 01:36 by Main.wbchen -

Copyright © by IBM and non-IBM 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.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.