Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
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 Vss2vm conversion does not migrate all the revisions
PVCS Version Manager 8.3
CMS-XML Dim10: VM2Dim: Migrating Version Manager files to Dimensions
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.
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.
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"
CMS-XML VM: How to "migrate" from VM 6.5 to VM 6.6.
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.
CMS-XML Migration console fails to run twice the same PVCS import
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.
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 PVCS(J): Some double-byte characters cannot be used for file/folder/project names in File Server-based Project Databases
_normal"><font color="black" face="Verdana" size="2"><span style="font-size: 10pt;"><img src="http://knowledgebase.serena.com/library/KNOWLEDGEBASE/ Migrated /kbimages/5007748/1.GIF" border="0" /></span
CMS-XML VM: How to use a pre-generated SSL certificate that includes the private key with Tomcat in the PVCS Version Manager Web Application Server
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".
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs