<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%"> ---+!! RDNG 4.0 to 5.x Migration: Known Issues Authors: [[UpgradeTroubleshootingTeam][UpgradeTroubleshootingTeam]] <br> Build basis: CLM 5.x %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 topic discusses the migration of Rational Doors NG (formerly RRC) in 5.0, where it is separated from the JTS database. ---++ Troubleshooting During this step in the upgrade process, a log file will be created in the ../server directory of the Collaborative Lifecycle Management (CLM) application installation directory. ---++ Known Issues Below are some known issues which arise during the RDNG Migration in the upgrade process ---+++ "Roll-Forward pending" error in log files *Version:* Upgrade to 5.x, DB2 <br> *Error During Upgrade:* After restoring a copy of the JTS database for use as RM database, the log files are flooded with "Roll-Forward pending" errors when connecting to the database. <br> *Cause:* This error occurs because the backup of the JTS database was taken online. <br> *Resolution:* Run the following SQL command to resolve this error. <verbatim>db2 rollforward db RMDB to end of backup and complete</verbatim> If the above SQL still results in the "Roll-Forward pending" error in the log files, run the following command: <verbatim>db2 rollforward db RMDB to end of logs and complete</verbatim> ---+++ RM projects are listed "-Unresolved Context-" *Version:* Upgrade to 5.x <br> *Error During Upgrade:* After completing the upgrade, RDNG projects will display as "-Unresolved Context-". <br> *Cause:* The finalize application step was skipped. <br> *Resolution:* Run the Finalize Application command from repotools. The applicationId can be found in <RRC_Home>\server\rm_upgrade_rmUpgrade.log file. <verbatim>repotools-jts.bat -finalizeApplicationMigration checkOauthDomain=true applicationId=xxxxx newPublicUrl=https://<jazz>:9443/rm</verbatim> ---+++ Updating Project !BackLinks Fails *Version:* Upgrade to 5.x * Make sure the CLM server is up and running * Make sure the User credentials you enter has the 5.0 license assigned prior to completing this step. <br> If you have token license server setup, enable the trial licenses and assign a license to the user prior to completing this step. ---+++++!! Related topics: * For more upgrade troubleshooting topics, refer to [[UpgradeTroubleshooting][Upgrade Troubleshooting]]. ---+++++!! External links: * None ---+++++!! Additional contributors: Main.StephanieBagot <sticky></div></sticky>
This topic: Deployment
>
WebHome
>
DeploymentTroubleshooting
>
UpgradeTroubleshooting
>
CLMUpgradeTroubleshooting
>
RRCMigrationKnownIssues
History: r3 - 2015-05-26 - 20:44:51 - Main.dmmckinn
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
.