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 Dim10 - Trying to update a baselined item's path results in "Failed to add item in path x because it already exists in path y."
In Dimensions CM 10.1.2 and earlier you were able to update an items path in a revised baseline by using relating the items as In Response To a request and then using the request to create the revised baseline. If you try the same thing in Dimensions 10.1.3 you get the error saying failed to add item in path x because it already exists in path y.
CMS-XML KM-Dim10: The published view pcms_item_history returns misleading results if a product has archived items.
However this view joins the item_action_history table with the item_revision_history table. In the item_revision_history table the letter 'A' is a valid type, for archived item revisions. This results in misleading results when querying the view.
CMS-XML Dim9: General Client Issues: Delete item results in error
Trying to delete an item via the desktop client sometimes resulted in a pop-up window with warning symbol and "Delete Item :". Clicking OK, did not result in the item being deleted.
CMS-XML KM-Dim9: File Get hangs on the Results dialog; Add Item Results dialog flashes but fails.
When trying to Get File through Web Client, the results dialog hangs. When trying to Add Item through Web Client, the Results dialog flashes and disappears, but item is not added.
CMS-XML DIM10: DS2DM Migration creates items with File Length 0
- go into Dimensions and display the File Length property of any of the imported items Expected Result The File Lenght should be reported correctly
CMS-XML Dim CM: Attempting to rename an item generates DBI4502580E SQL-7(13081) ERROR: relation "bl_cust_items" does not exist
Attempting to rename an item with a PostgreSQL database results in the following error: DBI4404527E DBIO: Database I/O error occurredDBI4502580E SQL-7(13081) ERROR: relation "bl_cust_items" does not exist PCM0005126E Error: Unable to update the item id, please see errors.
CMS-XML KM-Dim12.1.1: Reported Bug: Removing an item from a project with a subproject results in error
COR3200609E Base PVN not found in project UID 12847538 when updating with change 'Uid(12847567) ProjectUid(12847538) ObjClass( ITEM ) ObjSpecUid(11143828) ObjUid(-1) ChangeType(REMOVE) OldPath() NewPath() StageSeq( 0 ) OldParentUid(-1) NewParentUid(-1) Logical(false) CheckControlPath(true)' After removing the subproject the RIWS command was successful:
CMS-XML Dim CM 2009 R2: COR3200180E Failed to remove item from trying to create revised baseline
3) A revised baseline is taken with the updates from Request A; Expected Result : - Revised baseline contains new item and a warning is displayed that the second item was not part of the original baseline.
CMS-XML Dim CM 14.1.x: MDHNCL4501155E Error: Failed to write metadata for file "//DIMADM.PDEV.DIM.DEV2.URTLIB(GL0UNEX)"(rc = 5 msg = Verb DimPutRecord had outcome rc-rea: 5-11;
A problem was reported writing metadata files during a deployment on Mainframe. The same set of items was successfully deployed to two other areas:
CMS-XML Dim10: VM2DIM: Warning:8005:Shared Archive is shared by the following items to be migrated: -or- Warning:8005:TestPdb
), each shared instance of an item is treated as a separate entity, and a separate Dimensions item will exist for each instance. For example, if a single Version Manager file is shared across three PDB locations being migrated, the resulting Dimensions repository will contain three separate items with the file contents .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs