If you elect to upgrade directly to 12.2 and you use area offsets you will need to convert the metadata in deployment areas to the new format using "dmmeta convert" in each offset directory before running "dmdba upgradedeploy". [3] Update an item that was deployed before the upgrade and attempt to deploy the new revision. Expected behaviour:
Start regedit and navigate to \HKEY_LOCAL_MACHINE\SOFTWARE\Serena\Dimensions\<version>\Install. Locate the key INSTALL_DemoProductDir and make sure it points to a valid location, e.g. C:\Serena\Dimensions 12 .1\CM\demo.
When performing an upgrade to Dimensions 14.3.3, the following error can occur: -- Upgrading CM_TYPICAL ($GENERIC:$GLOBAL)... Warning: Legacy data cache is not available.
Baselines and projects in schema fails to upgrade because of path conflicts between directories and directory items. Examples of Baselines upgrade Errors DBA3200088E Path conflict: Directory UID 5528454 conflicts with item 'TESTMAN:LIB-5279050.A-DAT' at 'etc/Utilities/TESTMM0001MYFILE/Lib/'.
After upgrading to VM 8.4.6, the File Server view in file browsers may no longer list certain Path Map entries compared to the same view from an older Version Manager client. This happens for Path Maps where the Publish PDBs option is not
Use the following steps to retain your Path Maps and VM I-Net Web Client servlet definitions when upgrading from PVCS VM 8.5.3 and older, or when moving to another machine. As of VM 8.6.1, Version Manager supports in-place upgrades from VM 8.6.0 and newer, but the instructions in this document can still be used to transfer data to another machine.
