1.   Upgrade from CLM 4.0.6 (including DM 4.0.6) to CLM 5.0.2 (including DM 5.0.2).

2.   Upgrade from CLM 5.0.2 (latest iFix015) including DM 5.0.2 (latest iFix11) to CLM 6.0.2 including DM 6.0.2.

Considering that there is no interactive guide, that includes DM migration form 4.0.6 to 5.0.2, while migrating CLM 4.0.6 to 5.0.2 (only CCM,RM,QM applications are mentioned), the question is what’s are the correct steps for upgrade path when upgrading from CLM 4.0.6 (including DM 4.0.6) to CLM 5.0.2 (including DM 5.0.2) ?

Our envoirment is WAS 8.5.5.9 on Windows Server 2012 R2 and Oracle Database 11.2.0.3 on Oracle Linux 6.5.

After executing first few steps of upgrade path, one have to upgrade all applications with repotools, beginning from JTS ending on DM and VVC (I suppose the upgrade order is correct). The next step is to deploy all applications on WAS Server and run deployed applications. Now is the tricky question, what is the order of next repotools commands to run ? Should one execute VVC: repotools-vvc.bat -vvc_online_migrationCommand  then repotools-dm.bat -migration_dm_runUpgradeManager  commands and after they are done, upload 5.0.2 licenses and run RDNG repotools-rm.bat –rmUpdateProjectBacklinksOnline command or the license upload and then running of RDNG repotools-rm.bat –rmUpdateProjectBacklinksOnline command should be executed before running VVC and DM repotools commands ?

Personally I executed RDNG repotools-rm.bat –rmUpdateProjectBacklinksOnline command after running VVC and DM repotools commands ending with theoretically working CLM 5.0.2 (including DM 5.0.2) envoirment. Strange thing is that STAR ETL Job is failing (with error: java.sql.SQLSyntaxErrorException: ORA-00904: "TOTAL_REQUIREMENTS_BY_REFID": invalid identifier), all other ETL Jobs are succeeded and the only applications that have some diagnostics warnings is DM.        

Could someone please advise the correct order of running the repotools commands and advice why STAR ETL Job is failing and DM diagnostics warnings occurred after upgrade (I assume that mentioned problems may by connected with wrong order of repotools command execution) ?

Regards

Tomasz Goraziński