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  
  Results
CMS-XML KM-Dim7: "1173-Error. Item UID <> doesn not exist."
This problem is caused by an entry in the table cm_impacts for a non-existent item_uid, most likely that of an item that was related. This can be confirmed this by using following SQL: Select affected_uid from cm_impacts
CMS-XML KM-Dim7: How to delete a Design Part if it has Related Change Documents that Cannot be un related.
the design part they are still related then you will need to carry out the following SQL scripts to find and delete the relationship from the cm_impacts tables. sqlplus <basedb>/<password>
CMS-XML Dim10: TT2Dim: Dimensions Connector for TeamTrack fails with ORA-01795 error if more than 1000 design parts are selected
Could not get list of new and updated Dimensions items SELECT distinct ch_doc_id INTO :O1.S.128 FROM cm_catalogue cmc, cm_attributes cma, cm_impacts im, part_catalogue pc, part_spec_catalogue psc WHERE cmc.ch_uid = cma.ch_uid AND (cma.attr_42 IS NULL OR LENGTH(cma.attr_42) = 0) AND (cma.attr_45
CMS-XML Dim CM 2009 R1.01: Browsing a change request causes error - Request uid does not exist
BC "QLARIUS_CR_1" /FILENAME="C:\DOCUME~1\pcaruana\LOCALS~1\Temp\pt10581.HTM" Browse Request - COR0005621E Error: Request uid 4216286 does not exist The object CM_IMPACTS has not been updated to remove the deleted Change Request reference.
CMS-XML KM-Dim9: Pdiff dump of change docs, get error: Unable to retrieve object data, Unable to dump chdoc relationships, Dump failed for object UID
select substr(cmc.ch_doc_id, 1, 35) "Ch Doc ID", cmc.ch_uid, cmi.affect_uid from cm_impacts cmi, cm_catalogue cmc
CMS-XML KM-Dim7: Interpreting the Compare Baseline Report, Summary Section
ยท "ch doc count" is the number of ch docs with an impact on design parts in the baseline and also related to items numbered above. The first ch doc count comes from entries in the cm_impacts table, and the second ch doc count uses this and count the ch docs which are also related to items in the baseline. Second Summary Section
CMS-XML KM-Dim10: The delta file for item does not exist in library
item_sets (item_uid) cm_impacts (affect_uid and impact_type = 'I') release_history(item_uid) (unlikely any release would have succeeded anyway)

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs