Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML DIM CM: Unable to update Detailed Description for requests migrated from PVCS Tracker
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.
CMS-XML KM-Dim7: How to migrate from Tracker PDIFF into Dimensions.
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.
Version: 11.0 PVCS Dimensions Version: PVCS Dimensions 7.0 SP2.1 Oracle Version: Oracle
CMS-XML KM-Dim10: Reported Defects DEF93687: Issue Fixed in Dimensions 10.1.1: VM2DM: VM 8.1 -> DIM 9.1.x migration not working properly in Korean OS platform
The main error message is “Warning: Archive C:\ pvcs \ Migration \suite\CaseStudyOne\data\chess\ will not be transfered - Item not found for specification "MIGSAMPLE:WANNAPLAY JAVA.AAAA-SRC".
CMS-XML KM-Dim7: Data Migration Utility hangs after second (MCX) login when executed from remote v2.7 Client.
The Dimensions server in use must have both CD1 and CD2 software components installed on the server. That is, the server components and the client components are required on a Windows server. The client CD (that is CD2) contains the PVCS TeamLink, Make and MCX relay binaries required for Data Migration Utility to be used remotely.
PDF Serena Dimensions CM Visual Studio Projects Migration Guide
Serena, TeamTrack, StarTool, PVCS , Collage, Comparex, Dimensions, Serena Dimensions, Mashup Composer, Mashup Exchange, Prototype Composer, Mariner and ChangeMan are registered trademarks of Serena Software, Inc. The Serena logo, Version Manager, Meritage and Mover are trademarks of Serena Software, Inc. All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
CMS-XML Dim10: VM2Dim: Migrating Version Manager files to Dimensions
g. Disk Space Requirements - Data Migration i. Recommended disk space is 5x the PVCS Version Manager project database size ii. Minimum disk space is 3x the PVCS Version Manager project database size
HTML How to Migrate Dimensions from one UNIX server to another
SQL> alter tablespace PCMS_DATA add datafile '/usr/ pvcs /oracle/dbs/PCMS_DATA_EXTRA1.DBF' size 2000M;
CMS-XML Migration console fails to run twice the same PVCS import
the first migration may fail for some reason (ex: incorrect baseline choice in the migration settings), then when the migration process is run twice on the same target project, then the second time it fails and does not import item revisions into Dimensions. workaround : when the folder %programdata%\Serena\MigrationConsole is deleted, a migration can be run twice successfully (after deleting the baseline and the items in Dimensions of course)
CMS-XML KM-Dim7: DMU: Error: Failed to get PVCS VM archive header details for
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"
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs