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 2009 R2.02: Removing state from lifecycle does not clean up old transitions and causes unique constraint violations
An off-normal transition was also defined from A to D. In the Admin Console delete state C. The operation works. Then delete state B. No error is reported, but when you attempt to create an object using the lifecycle, for example a Request, an Oracle error is generated indicating a unique constraint violation on PENDING_ACTIONS_K1. Dimensions has correctly added the new normal transition from A=>D, but it has not deleted the original off-normal transition.
CMS-XML Dim12: SBM2DM Connector: Error: Could not start transition from state Development to state QA (-1) Transition '' is not valid for transitioning item number 2511 (item 34) in table 1006. [(:TSPrimaryItemStartTransition: Error starting transition Start transition failed.
The above error is occurring because there is a Restrict by Rule on the transition within SBM. If the rule is removed, the synchronization works.
CMS-XML Dim10: ORA-00001: unique constraint errors when creating items, baselines, or requests
For instance, if a Request lifecycle has been created with a transition which includes a role which has both Primary and Secondary roles. When this is done, the above error can occur when creating a new Request.
CMS-XML KM-Dim7: SQL-0304(22034) ORA-00001: unique constraint (PRODUCT>.PENDING_ACTIONS_K1) violated
Remove duplicate lifecycle entries for the same from/to transition
CMS-XML KM-Dim9: Reported Defect DEF94289: Unable to action change documents with leadership role and constraints disabled.
Create a chdoc type with a multi stage lifecycle (more than 2) Assign the role for the transition A - has leader and B has second Ensure that constraint is turned on and user B cannot action
CMS-XML Dim10: 1019 - DBIO: Oracle Error occurred SQL-0304 (22034) ORA-00001: Unique constraint (pcms.pending_actions_k1) violated.
One cause of this is incorrect data somewhere in the role assignments, object type definitions or lifecycle definitions. For example once in a while a control plan will indicate a transition from the same lifecycle state to the same other lifecycle state with one transition defined as NORMAL and a second defined as off-normal. In some instances, the problem can also be seen with the lifecycle of the Item Type or Request Type within Admin Console.
CMS-XML Dim2009R2: Restricted mode does not require authentication
Dim2009R2: Restricted mode does not require authentication
CMS-XML Dim9: How to restrict access to items in Dimensions 9
Dim9: How to restrict access to items in Dimensions 9
CMS-XML DimCM: AdminConsole: How to restrict users to READ ONLY access to AdminConsole
DimCM: AdminConsole: How to restrict users to READ ONLY access to AdminConsole
CMS-XML KM-Dim10: Restricting access by Design Parts. Related vs Owning DP
KM-Dim10: Restricting access by Design Parts. Related vs Owning DP
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs