If this is the case, the solution is to determine whether this should be a normal or off-normal transition and remove the incorrect row from the database. To determine whether this should be normal or off-normal examine the remaining lifecycle transitions and determine which is correct, keeping in mind that there must be one and only one normal path and the normal path cannot be split (i. e ., with a missing transition). Once the basic problem is corrected, the lifecycle may be edited again using Admin Console.
User gets the following error when trying to move change docs to secondary catalogue: 1019-DBIO: Database I/O error occurred. SQL -0304(18008) ORA - 00001 : unique constraint (SEC_CM_ATTR_UPD_HIST 1 ) violated
When upgrading from 10.1.2 to 10.1.3.3 the following error occurs SQL - 1 (11060d950) ORA - 00001 : unique constraint (PHIL.PRIVILEGE_SCOPE_ASSIGNMENTS_PK) violated Error detected in /upvcreg1/serena/dimensions/10.1/cm/dbms/upgrade/upgradedb_1013.sql, line 739
Create Change Document - 1019-DBIO: Database I/O error occurred SQL -0304(22023) ORA - 00001 : unique constraint (INTERMEDIATE.CM_IMPACTS_PK) violated 1226-One or more of hte objects you were trying to relate to the change document PAYROLL_HELD_8376722 is already related
