When creating requests using PDIFF (Tracker migration ) it is sometimes not possible to enter/edit the detailed description. The command completes without errors and the history is updated but the description never arrives in dm_dbfiles.
Migrating Data from Version Manager to Dimensions CM or Express The steps shown below are guidelines and in addition to the PVCS Version Manager Migration Guide, dmcm_vm_migration.pdf. Please refer to the PVCS Version Manager Migration Guide for complete details.
Steps to migrate from Tracker PDIFF into Dimensions. The attached document explains the steps to take to migrate a PVCS Tracker PDIFF export into PVCS Dimensions.
If a VM archive has an access list on it, the DMU cannot migrate files from that archive even if the person performing the migration is permitted access by the access list. Attempting to migrate from an archive with an access list the DMU says it successfully generates the script, however the script is empty. The log file has the following in it: Error: Failed to generate log output Error: Failed to get PVCS VM archive header details for"V:\ARCHIVE\fxrs\brderr.h_v"
1) IF the customer installs VM 6.6 into EXACTLY the same directory and EXACTLY the Program Group, there may be a PVCS Version Manager 6.5 icon. This icon will launch VM 6.6. Simply delete the offending Program Group Item.
It is a database. This database stores info about already migrated items. If this step is skipped no items should be created if run migration next time.
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore C:\ pvcs \vm8630\vm\common\tomcat\conf\serena.keystore -destkeystore C:\ pvcs \vm8630\vm\common\tomcat\conf\serena.keystore -deststoretype pkcs12".
