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: Upgrade of BASEDB fails with SQL-1(90018) ORA-00001: unique constraint (BASEDB.VRS_1_AC_PK) violated
Upgrade fails at upgrading vrs_1_arc_changes in $G:$G. DBI 0004527 E DBIO: Database I/O error occurred SQL-1(90018) ORA-00001: unique constraint (
CMS-XML Dim10: 1019 - DBIO: Oracle Error occurred SQL-0304 (22034) ORA-00001: Unique constraint (pcms.pending_actions_k1) violated.
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.
CMS-XML KM-Dim9: SQL: Create change sql-0304 ora-00001 unique constraint cm_catalogue_k2 violated
KM-Dim9: SQL : Create change sql -0304 ora - 00001 unique constraint cm_catalogue_k2 violated
CMS-XML KM-Dim7: SQL-0304(22034) ORA-00001: unique constraint (PRODUCT>.PENDING_ACTIONS_K1) violated
KM-Dim7: SQL -0304(22034) ORA - 00001 : unique constraint (PRODUCT>.PENDING_ACTIONS_K 1 ) violated
CMS-XML KM-Dim9: SQL-0304(3508) ORA-00001: unique constraint (CM.PART_ITEM_RELS_PK) violated
KM-Dim9: SQL -0304(3508) ORA - 00001 : unique constraint (CM.PART_ITEM_RELS_PK) violated
CMS-XML KM-Dim10: During database upgrade get error: SQL-1(01738B30) ORA-00001: unique constraint (MAST.GROUP_MEMBERS_PK) violated
KM-Dim10: During database upgrade get error: SQL - 1 (01738B30) ORA - 00001 : unique constraint (MAST.GROUP_MEMBERS_PK) violated
CMS-XML KM-Dim9: SQL Solution: ora-00001 constraint error on sec_cm_attr_upd_hist1 trying to move change docs to secondary catalogue
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
CMS-XML ORA-00001: unique constraint (xxxxxxxxx.PRIVILEGE_SCOPE_ASSIGNMENTS_PK) 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
CMS-XML KM-Dim9: Creating Change Document get error: 1019, ORA-00001 unique contraint on CM_IMPACTS_PK and 1226
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
CMS-XML Build failed with Internal SPI error - ORA-00001: unique constraint (CMSS.PK_BLD_BUILD_JOB_SOURCE_HISTOR) violated
Internal SPI error: Error: failed to update database. ( SQL - 1 (026B81D0)
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs