ORA-00001 UNIQUE CONSTRAINT ERROR ON SYS.WRH$_SQLTEXT_PK?

/u01/app/oracle/admin/bill02/bdump/bill02_m000_10074.trc
Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.1.0
System name: SunOS
Node name: bill02
Release: 5.9
Version: Generic_117171-17
Machine: sun4u
Instance name: bill02
Redo thread mounted by this instance: 1
Oracle process number: 55
Unix process pid: 10074, image: oracle@bill02 (m000)
*** 2005-10-27 02:03:14.682
*** ACTION NAME:(Auto-Flush Slave Action) 2005-10-27 02:03:14.667
*** MODULE NAME:(MMON_SLAVE) 2005-10-27 02:03:14.667
*** SERVICE NAME:(SYS$BACKGROUND) 2005-10-27 02:03:14.667
*** SESSION ID:(519.24807) 2005-10-27 02:03:14.667
*** KEWROCISTMTEXEC - encountered error: (ORA-00001: unique constraint (SYS.WRH$_SQLTEXT_PK) violated
*** SQLSTR: total-len=570, dump-len=240,
STR={INSERT INTO wrh$_sqltext (sql_id, dbid, sql_text, command_type, snap_id, ref_count) SELECT /*+ ordered use_nl(s1) index(s1) */ sie.sqlid_kewrsie, :dbid, s1.sql_fulltext, }
*** KEWRAFM1: Error=13509 encountered by kewrfteh
How to fix?
Thanks!

Have you tried searching Metalink? A unique constraint violation on a SYS table by MMON will almost certainly require Oracle Support's assistance to resolve. Something rather deep inside Oracle has done something wrrong.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Similar Messages

ORA-00001: unique constraint error..

Hi There,
We were trying to do an insert when we started having ORA-00001: unique constraint error.. to speed our testing we decided to disable all the constraints on the table; however we still having the same issue.
How can we resolve this please.
SQL> select constraint_name,constraint_type,status from dba_constraints where table_name='MEMBER_LATEST';
CONSTRAINT_NAME                C STATUS
MEMBER_LATEST_PK               P DISABLED
SYS_C0017577                   C DISABLED
SYS_C0017576                   C DISABLED
SYS_C0017575                   C DISABLED
SYS_C0017574                   C DISABLED
SYS_C0017573                   C DISABLED
SYS_C0017572                   C DISABLED
SYS_C0017571                   C DISABLED
SYS_C0017570                   C DISABLED
MEMBER_LATEST_FK               R DISABLED
10 rows selected.
SQL>
SQL>
SQL>     INSERT INTO MEMBER_LATEST (DIS_ID, TIMESTAMP, LAST_NAME, FIRST_NAME, MIDDLE_NAME, DIS_COUNT)
2    SELECT DIS_ID, 'TEST', LAST_NAME, FIRST_NAME, MIDDLE_NAME, 0
3    FROM MV_DIS_MEM, MV_DIS_COUNT
4    WHERE MV_DIS_MEM.P_CODE = MV_DIS_COUNT.P_CODE
5    ORDER BY 1,3,4;
    INSERT INTO MEMSCH.MEMBER_LATEST (DIS_ID, TIMESTAMP, LAST_NAME, FIRST_NAME,
ERROR at line 1:
ORA-00001: unique constraint (MEMSCH.MEMBER_LATEST_PK) violated
SQL>Anything else we can do please?
Thanks

rsar001 wrote:
but isn't the unique index constraint part of the disabled constraints on the table as shown above?Not if index used by PK was created separately prior to PK:
SQL> create table emp1 as select * from emp;
Table created.
SQL> alter table emp1
2 add constraint emp1_pk
3 primary key(empno);
Table altered.
SQL> insert into emp1 select * from emp;
insert into emp1 select * from emp
ERROR at line 1:
ORA-00001: unique constraint (SCOTT.EMP1_PK) violated
SQL> alter table emp1 disable primary key;
Table altered.
SQL> insert into emp1 select * from emp;
14 rows created.
SQL> rollback;
Rollback complete.
SQL> alter table emp1 drop primary key;
Table altered.
SQL> create unique index emp1_pk on emp1(empno);
Index created.
SQL> alter table emp1
2 add constraint emp1_pk
3 primary key(empno)
4 using index emp1_pk;
Table altered.
SQL> insert into emp1 select * from emp;
insert into emp1 select * from emp
ERROR at line 1:
ORA-00001: unique constraint (SCOTT.EMP1_PK) violated
SQL> alter table emp1 disable primary key;
Table altered.
SQL> insert into emp1 select * from emp;
insert into emp1 select * from emp
ERROR at line 1:
ORA-00001: unique constraint (SCOTT.EMP1_PK) violated
SQL> But by dropping index you are simply delaying the issue. Yes, you will be able to insert, but what's then? You will not be able to recreate PK - same violation error will be raised.
SY.

ORA-00001 - Unique Constraint error in Oracle forms 6i

Hi,
I am using Forms 6i. I have an issue while inserting records into a custom table. Below is the functionality.
When I check the check box, and press the 'APPROVE' button, the record gets inserted into the custom table. But while inserting I am getting 'ora-00001-unique constraint violated error'.
But the custom table doesn't have any data in it. (So the inserting record should not be a duplicate record).
Any suggestions would be of great help.
Thanks
Deepti

Is it a sql statement that is performing the insert, or are you using the native data block DML functionality in your form? Secondly have you identified candidate columns that could be causing your issue?
If you are using sql statement have you debugged to comfirm that you are not firing the same block of code more that once, and that if it is required to execute multiple times are you incrementing the sequence values that should be unique.
Regards
Q

How to handle ORA-00001: unique constraint in EXCEPTION block?

Hi,
Is there a specific exception thats raised when ORA-00001: unique constraint error occurs?

SQL> create table test(id number primary key);
Table created.
SQL> set serverout on
SQL> declare
2   ex exception;
3   pragma exception_init(ex,-1);
4 begin
5   insert into test values(1);
6 exception
7   when ex then
8    dbms_output.put_line('dup');
9   when others then
10    raise;
11 end;
12 /
dup
PL/SQL procedure successfully completed.
<br>
<a href ="http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14261/errors.htm#LNPLS00703">Predefied exceptions </a>

Users getting APP-FND-01934:ora-00001 unique constraint

users getting APP-FND-01934:ora-00001 unique constraint(ENI.ENI_OLTP_ITEM_STAR_U3) violated in package ENI_ITEMS_STAR_PKG Procedure INsERT_ITEMS_IN_STAR on Master ITEM's in 11i EBS.

Please see these MOS Docs.
APP-FND-01934 ORA-00001 Error Occurs When Creating Items [ID 1072935.1]
APP-FND-01934 ORA-00001: Unique Constraint Error at Master Items [ID 465008.1]
ORA-02291: Integrity Constraint (GMI.IC_LOTS_MST_IC_ITEM_MST_B_FK) Violated [ID 302368.1]
Thanks,
Hussein

Import error: ORA-00001:unique constraint (FLOWS_030100.WWV_FLOW_FLOW_PK)

Hi community,
I got an awful application import error.
ORA-20001: GET_BLOCK Error. ORA-20001: GET_STMT error. ORA-20001: Execution of the statement was unsuccessful. ORA-00001: unique constraint (FLOWS_030100.WWV_FLOW_FLOW_PK) violated &lt;pre&gt;--application/create_application &amp;lt;br&amp;gt; &amp;lt;br&amp;gt;begin &amp;lt;br&amp;gt; &amp;lt;br&amp;gt;wwv_flow_api.create_flow( &amp;lt;br&amp;gt; p_id =&amp;gt; 381, &amp;lt;br&amp;gt; p_display_id=&amp;gt; 381, &amp;lt;br&amp
Error installing application.What did I do?
Developed some in my test environment (APP ID 381) and made a normal export like 100 times before. When I tried to import that application in APP ID 380 the error occurred.
More information:
Both applications are in the same workspace.
APEX 3.1.2
Oracle XE
I tried a bit around:
Import in another workspace > same error
Restart OAS try to import> same error
Deletion of APP 380 and the try to import > same error
Import of an older version > successfully no errors
Try to make a new export of APP ID 381 > same error on import
Don't want to delete app 381! :O
Seems like something inside of the application/export is wrong.

Hi Scott,
the query returns
select grantee from dba_role_privs where granted_role='APEX_ADMINISTRATOR_ROLE';
GRANTEE
SYSI tried to install the export in another apex database environment. New error occurred.
ORA-20001: GET_BLOCK Error.
ORA-20001: Execution of the statement was unsuccessful.
ORA-02291: integrity constraint
(FLOWS_030100.WWV_FLOW_SEC_SCHEMES_FK) violated - parent key not found <pre>begin
--application/shared_components/security/authorization/t_users
wwv_flow_api.create_security_scheme( p_id =&gt; 18109134549712168 + wwv_flow_api.g_id_offset, p_flow_id =&gt;
wwv_flow.g_flow_id, p_name=&gt;'T_USERS', p_scheme_type=&gt;'EXISTS', p_scheme=&gt;'select cI looked in the export file for the error part and found some interesting code. See:
prompt ...authorization schemes
begin
--application/shared_components/security/authorization/t_users
wwv_flow_api.create_security_scheme(
p_id => 18109134549712168 + wwv_flow_api.g_id_offset,
p_flow_id => wwv_flow.g_flow_id,
p_name=>'T_USERS',
p_scheme_type=>'EXISTS',
p_scheme=>'select count(*) from v_mze_appl '||chr(10)||
'where NAME like UPPER(:P101_USERNAME)'||chr(10)||
'and ROLE IN (''APEX_MZE_ADMIN'',''APEX_MZE_USERS'')'||chr(10)||
p_caching=>'BY_USER_BY_PAGE_VIEW',
p_error_message=>'Sie haben keine Berechtigungen für diese Seite');
--application/shared_components/security/authorization/t_auswertung
wwv_flow_api.create_security_scheme(
p_id => 42071873141249964 + wwv_flow_api.g_id_offset,
p_flow_id => wwv_flow.g_flow_id,
p_name=>'T_AUSWERTUNG',
p_scheme_type=>'EXISTS',
p_scheme=>'select count(*) from v_mze_appl '||chr(10)||
'where NAME like UPPER(:P101_USERNAME)'||chr(10)||
'and ROLE IN (''APEX_MZE_ADMIN'',''APEX_MZE_REPORT'')'||chr(10)||
p_caching=>'BY_USER_BY_PAGE_VIEW',
p_error_message=>'No rights for the page');
--application/shared_components/security/authorization/t_berechtigungen
wwv_flow_api.create_security_scheme(
p_id => 42072157819264447 + wwv_flow_api.g_id_offset,
p_flow_id => wwv_flow.g_flow_id,
p_name=>'T_BERECHTIGUNGEN',
p_scheme_type=>'EXISTS',
p_scheme=>'select count(*) from v_mze_appl '||chr(10)||
'where NAME like UPPER(:P101_USERNAME)'||chr(10)||
'and ROLE IN (''APEX_MZE_ADMIN'',''APEX_MZE_BERECHTIGUNGEN'')'||chr(10)||
p_caching=>'BY_USER_BY_PAGE_VIEW',
p_error_message=>'No rights for the page');
--application/shared_components/security/authorization/t_kategorien
wwv_flow_api.create_security_scheme(
p_id => 42072262321265732 + wwv_flow_api.g_id_offset,
p_flow_id => wwv_flow.g_flow_id,
p_name=>'T_KATEGORIEN',
p_scheme_type=>'EXISTS',
p_scheme=>'select count(*) from v_mze_appl '||chr(10)||
'where NAME like UPPER(:P101_USERNAME)'||chr(10)||
'and ROLE IN (''APEX_MZE_ADMIN'',''APEX_MZE_KATEGORIEN'')',
p_caching=>'BY_USER_BY_PAGE_VIEW',
p_error_message=>'No rights for the page');
end;
/Looks like the p_id for T_USERS is wrong. Exactly what the error tries to describe too. How could that happen and how can I solve that issue? I will try and save the t_users group again and will create a new export.
King regards,
Tobias
Edited by: Tobias Arnhold on Mar 2, 2009 8:23 AM

Error while adding Image: ORA-00001: unique constraint

Dear all,
I have an error while adding images to MDM I can´t explain. I want to add 7231 images. About 6983 run fine. The rest throws this error.
Error: Service 'SRM_MDM_CATALOG', Schema 'SRMMDMCATALOG2_m000', ERROR CODE=1 ||| ORA-00001: unique constraint (SRMMDMCATALOG2_M000.IDATA_6_DATAID) violated
Last CMD: INSERT INTO A2i_Data_6 (PermanentId, DataId, DataGroupId, Description_L3, CodeName, Name_L3) VALUES (:1, :2, :3, :4, :5, :6)
Name=PermanentId; Type=9; Value=1641157; ArraySize=0; NullInd=0;
Name=DataId; Type=5; Value=426458; ArraySize=0; NullInd=0;
Name=DataGroupId; Type=4; Value=9; ArraySize=0; NullInd=0;
Name=Description_L3; Type=2; Value=; ArraySize=0; NullInd=0;
Name=CodeName; Type=2; Value=207603_Img8078_gif; ArraySize=0; NullInd=0;
Name=Name_L3; Type=2; Value=207603_Img8078.gif; ArraySize=0; NullInd=0;
Error: Service 'SRM_MDM_CATALOG', Schema 'SRMMDMCATALOG2_m000', ERROR CODE=1 ||| ORA-00001: unique constraint (SRMMDMCATALOG2_M000.IDATA_6_DATAID) violated
Last CMD: INSERT INTO A2i_Data_6 (PermanentId, DataId, DataGroupId, Description_L3, CodeName, Name_L3) VALUES (:1, :2, :3, :4, :5, :6)
Name=PermanentId; Type=9; Value=1641157; ArraySize=0; NullInd=0;
Name=DataId; Type=5; Value=426458; ArraySize=0; NullInd=0;
Name=DataGroupId; Type=4; Value=9; ArraySize=0; NullInd=0;
Name=Description_L3; Type=2; Value=; ArraySize=0; NullInd=0;
Name=CodeName; Type=2; Value=207603_Img8085_gif; ArraySize=0; NullInd=0;
Name=Name_L3; Type=2; Value=207603_Img8085.gif; ArraySize=0; NullInd=0;
I checked all data. There is no such dataset in the database. Can anybody give me a hint how to avoid this error.
One thing I wonder: The PermanentId is allways the same but I can´t do anything here.
BR
Roman
Edited by: Roman Becker on Jan 13, 2009 12:59 AM

Hi Ritam,
For such issues, can you please create a new thread or directly email the author rather than dragging back up a very old thread, it is unlikely that the resolution would be the same as the database/application/etc releases would most probably be very different.
For now I will close this thread as unanswered.
SAP SRM Moderators.

(Error) ORA-00001: unique constraint (WHSE_DBA.PK_DELPHI_TRANS_FACT) violat

I have a stored proc which runs every night. The stored proc is giving a unique constraint violation.
(Error) ORA-00001: unique constraint (WHSE_DBA.PK_DELPHI_TRANS_FACT) violated.
Any idea about how to debug this.

I want to create an error table on the stored proc shown below. I know I have to add something in the exceptions. Can anyone give me the commands and where to add it.
CREATE OR REPLACE PROCEDURE WHSE_DBA.DM_LD_DELPHI_TRANS_FACT
IS
-- VARIABLE DECLARATIONS
LAST_LOAD_DATE                   DATE;
INSERTCOUNT                 NUMBER:=0;
-- LOGGING VARIABLES AND CONSTANTS
TARGETTABLE                 CONSTANT VARCHAR2(20):='DELPHI_TRANS_FACT';
MSGUNKNOWNERR               CONSTANT VARCHAR2(20):='Error';
NBRIGNOREERR                CONSTANT NUMBER:=12541;
DEFDATE                     CONSTANT DATE:='01-OCT-2006';
ERRDESCRIPTION              VARCHAR2(255);
V_DELPHI_TRANS_TOTAL           NUMBER;
V_DELPHI_TRANS_FACT_TOTAL   NUMBER;
BEGIN
-- LOOK UP LAST LOADED RECORD
SELECT NVL(MAX(SNAPSHOT_DATE),DEFDATE)
INTO LAST_LOAD_DATE
FROM DELPHI_TRANS_FACT;
-- * LOAD ALL DIMENSION TABLES
-- BUDGET_YR_DIMENSION
INSERT INTO BUDGET_YR_DIMENSION (BUDGET_YEAR, SNAPSHOT_DATE)
(SELECT DISTINCT BUD_YR, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM BUDGET_YR_DIMENSION
WHERE BUDGET_YEAR=OUTER.BUD_YR));
-- EFF_DATE_DIMENSION
INSERT INTO EFF_DATE_DIMENSION (PAID_FIS_YEAR, PAID_QTR, EFFECTIVE_DATE, SNAPSHOT_DATE)
(SELECT DISTINCT CVT_DATE_TO_FISCAL_YEAR(EFF_DT), PD_QTR, EFF_DT, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM EFF_DATE_DIMENSION
WHERE EFFECTIVE_DATE=OUTER.EFF_DT));
-- PROC_DATE_DIMENSION
INSERT INTO PROC_DATE_DIMENSION (PROCESS_DATE, SNAPSHOT_DATE)
(SELECT DISTINCT PROC_DT, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM PROC_DATE_DIMENSION
WHERE PROCESS_DATE=OUTER.PROC_DT));
-- ORG_DIMENSION
INSERT INTO ORG_DIMENSION (ORG,COST_CTR,SNAPSHOT_DATE)
(SELECT DISTINCT ORG, CC_CD, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM ORG_DIMENSION
WHERE ORG=OUTER.ORG));
-- BPAC DIMENSION
INSERT INTO BPAC_DIMENSION (BPAC, AFC_CD, PE_CODE, SNAPSHOT_DATE)
(SELECT DISTINCT BPAC, AFC_CD, PE, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM BPAC_DIMENSION
WHERE BPAC=OUTER.BPAC));
-- FUND DIMENSION
INSERT INTO FUND_DIMENSION (FUND,APPROP_CD,LIM_CD,SNAPSHOT_DATE)
(SELECT DISTINCT FUND, APPROP_CD, APPLIM_CD, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM FUND_DIMENSION
WHERE FUND=OUTER.FUND));
-- OBJ_CD_DIMENSION
INSERT INTO OBJ_CD_DIMENSION (OBJ_CD,SNAPSHOT_DATE)
(SELECT DISTINCT OC_CD, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM OBJ_CD_DIMENSION
WHERE OBJ_CD=OUTER.OC_CD));
-- GLA DIMENSION
INSERT INTO GLA_DIMENSION (GLA_CD,SNAPSHOT_DATE)
(SELECT DISTINCT GLA, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM GLA_DIMENSION
WHERE GLA_CD=OUTER.GLA));
-- PROJECT_TASK_DIMENSION
INSERT INTO PROJECT_TASK_DIMENSION (PROJECT_NO,TASK_NO,SNAPSHOT_DATE)
(SELECT DISTINCT PROJ_NBR, TASK_NBR, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM PROJECT_TASK_DIMENSION
WHERE PROJECT_NO=OUTER.PROJ_NBR
AND TASK_NO=OUTER.TASK_NBR));
-- TRANS_DESC_DIMENSION
INSERT INTO TRANS_DESC_DIMENSION (DESCRIPTION,SNAPSHOT_DATE)
(SELECT DISTINCT DESCR, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM TRANS_DESC_DIMENSION
WHERE DESCRIPTION=OUTER.DESCR
AND OUTER.DESCR IS NOT NULL));
-- SUPPLIER_DIMENSION
INSERT INTO SUPPLIER_DIMENSION (SUPPLIER_NAME, SNAPSHOT_DATE)
(SELECT DISTINCT VENDOR_NAME, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM SUPPLIER_DIMENSION
WHERE SUPPLIER_NAME=OUTER.VENDOR_NAME));
-- DELPHI_INV_DIMENSION
INSERT INTO DELPHI_INV_DIMENSION (INVOICE_NO, SNAPSHOT_DATE)
(SELECT DISTINCT INV_NO, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM DELPHI_INV_DIMENSION
WHERE INVOICE_NO=OUTER.INV_NO));
-- DELPHI_PO_DIMENSION
INSERT INTO DELPHI_PO_DIMENSION (PO_NO, SNAPSHOT_DATE)
(SELECT DISTINCT PO_NO, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM DELPHI_PO_DIMENSION
WHERE PO_NO=OUTER.PO_NO));
-- TEMPORARILY DISABLE KEY FOR FASTER LOADING
DB_MISC.PRO_EXE_DDL('ALTER TABLE DELPHI_TRANS_FACT DISABLE CONSTRAINT PK_DELPH_TRANS_FACT');
    -- MOVE DATA INTO TABLE
     INSERT INTO DELPHI_TRANS_FACT (BPAC_KEY, ORG_KEY, FUND_KEY, OBJ_CD_KEY, GLA_KEY,
     EFF_DATE_KEY, PROC_DATE_KEY, PROJECT_TASK_KEY, BUDGET_YR_KEY, DELPHI_TRANS_DESC_KEY,
     BALANCE, COMMIT_AMT, UDO_AMT, AEU_AMT, AEP_AMT, OBLIGATION_AMT, SNAPSHOT_DATE,
     SUPPLIER_KEY, DELPHI_INV_KEY, DELPHI_PO_KEY)
     (SELECT BPAC_KEY, ORG_KEY, FUND_KEY, OBJ_CD_KEY, GLA_KEY, EFF_DATE_KEY, PROC_DATE_KEY,
     PROJECT_TASK_KEY, BUDGET_YR_KEY, TRANS_DESC_KEY, SUM(BAL), SUM(COMMIT_AMT), SUM(UDO_AMT),
     SUM(AEU_AMT), SUM(AEP_AMT), SUM(OBLIGATION_AMT), MAX(SYSDATE), SUPPLIER_KEY, DELPHI_INV_KEY,
     DELPHI_PO_KEY
     FROM BPAC_DIMENSION, ORG_DIMENSION, FUND_DIMENSION, OBJ_CD_DIMENSION, GLA_DIMENSION,
    EFF_DATE_DIMENSION, PROC_DATE_DIMENSION, PROJECT_TASK_DIMENSION, BUDGET_YR_DIMENSION,
     TRANS_DESC_DIMENSION, DELPHI_TRANS,     SUPPLIER_DIMENSION, DELPHI_INV_DIMENSION, DELPHI_PO_DIMENSION
     WHERE DELPHI_TRANS.SNAPSHOT_DATE>LAST_LOAD_DATE
     -- JOIN WITH BPAC_DIMENSION
    AND DELPHI_TRANS.BPAC=BPAC_DIMENSION.BPAC
     -- JOIN WITH ORG_DIMENSION
     AND DELPHI_TRANS.ORG = ORG_DIMENSION.ORG
     -- JOIN WITH FUND_DIMENSION
     AND DELPHI_TRANS.FUND = FUND_DIMENSION.FUND
     -- JOIN WITH OBJ_CD_DIMENSION
     AND DELPHI_TRANS.OC_CD=OBJ_CD_DIMENSION.OBJ_CD
     -- JOIN WITH GLA_DIMENSION
     AND DELPHI_TRANS.GLA=GLA_DIMENSION.GLA_CD
     -- JOIN WITH EFF_DATE_DIMENSION
     AND DELPHI_TRANS.EFF_DT=EFF_DATE_DIMENSION.EFFECTIVE_DATE
     -- JOIN WITH PROC_DATE_DIMENSION
     AND DELPHI_TRANS.PROC_DT=PROC_DATE_DIMENSION.PROCESS_DATE
     -- JOIN WITH PROJECT_TASK_DIMENSION
     AND (DELPHI_TRANS.PROJ_NBR=PROJECT_TASK_DIMENSION.PROJECT_NO
     AND DELPHI_TRANS.TASK_NBR=PROJECT_TASK_DIMENSION.TASK_NO)
     -- JOIN WITH BUDGET_YR_DIMENSION
     AND DELPHI_TRANS.BUD_YR=BUDGET_YR_DIMENSION.BUDGET_YEAR
     -- JOIN WITH TRANS_DESC_DIMENSION
     AND DELPHI_TRANS.DESCR=TRANS_DESC_DIMENSION.DESCRIPTION
     -- JOIN WITH SUPPLIER_DIMENSION
     AND DELPHI_TRANS.VENDOR_NAME=SUPPLIER_DIMENSION.SUPPLIER_NAME
     -- JOIN WITH DELPHI_PO_DIMENSION
     AND DELPHI_TRANS.PO_NO=DELPHI_PO_DIMENSION.PO_NO
     -- JOIN WITH DELPHI_INV_DIMENSION
     AND DELPHI_TRANS.INV_NO=DELPHI_INV_DIMENSION.INVOICE_NO
     GROUP BY BPAC_KEY, ORG_KEY, FUND_KEY, OBJ_CD_KEY, GLA_KEY, EFF_DATE_KEY, PROC_DATE_KEY,
     PROJECT_TASK_KEY, BUDGET_YR_KEY,TRANS_DESC_KEY, SUPPLIER_KEY, DELPHI_INV_KEY, DELPHI_PO_KEY);
-- COUNT AFFECTED RECORDS
INSERTCOUNT:=0+SQL%ROWCOUNT;
-- RE-ENABLE KEY CONSTRAINT
DB_MISC.PRO_EXE_DDL('ALTER TABLE DELPHI_TRANS_FACT ENABLE VALIDATE CONSTRAINT PK_DELPH_TRANS_FACT');
-- STORE RESULTS OF OPERATION
IF INSERTCOUNT>0 THEN
DB_MISC.LOGFAILURE_EX('none', 'none', INSERTCOUNT||' new records loaded successfully.', TARGETTABLE, 'DM_LD_DELPHI_TRANS_FACT', FALSE);
END IF;
--- COMPARE BALANCE TOTAL FROM DELPHI_TRANS TABLE AND DELPHI_TRANS_FACT TABLE
SELECT SUM(BAL) INTO V_DELPHI_TRANS_TOTAL
FROM DELPHI_TRANS ;
SELECT SUM(BALANCE) INTO V_DELPHI_TRANS_FACT_TOTAL
FROM DELPHI_TRANS_FACT ;
VALIDATE_LOAD(V_DELPHI_TRANS_TOTAL,V_DELPHI_TRANS_FACT_TOTAL);
-- EXCEPTION HANDLING ROUTINES * * * * * * * * * * * * * * * * * * * * * *
EXCEPTION
    WHEN OTHERS THEN
      ROLLBACK;
      IF SQLCODE!=NBRIGNOREERR THEN
        ERRDESCRIPTION:=SQLERRM;
        -- CALL ROUTINE TO PROCESS ERROR
        DB_MISC.LOGFAILURE_EX('none', 'none', ERRDESCRIPTION, TARGETTABLE, 'DM_LD_DELPHI_TRANS_FACT', TRUE);
        COMMIT;
      END IF;
-- END EXCEPTION HANDLING ROUTINES * * * * * * * * * * * * * * * * * * * * * *
END

ASCP erroring out with ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITI

Here is log
=====================================================
18-AUG 11:06:25 : ======================================== 18-AUG
11:06:25 : Error in PROCEDURE=LOAD_SETUP_TRANSITION, TABLE=MSC_SETUP_TRANSITIONS 18-AUG 11:06:27 : COLUMN=ORGANIZATION_CODE,
VALUE=TST:M1 18-AUG 11:06:27 : COLUMN=RESOURCE_ID, VALUE=14 18-AUG
11:06:27 : COLUMN=FROM_SETUP_ID, VALUE=1 18-AUG 11:06:27 :
COLUMN=TO_SETUP_ID, VALUE=2 18-AUG 11:06:27 : ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITIONS_U1) violated 18-AUG 11:06:27 :
======================================== 18-AUG 11:06:27 : Error in PROCEDURE=LOAD_SETUP_TRANSITION, TABLE=MSC_SETUP_TRANSITIONS 18-AUG
11:06:27 : COLUMN=ORGANIZATION_CODE, VALUE=TST:M1 18-AUG 11:06:27 :
COLUMN=RESOURCE_ID, VALUE=14 18-AUG 11:06:27 : COLUMN=FROM_SETUP_ID,
VALUE=2 18-AUG 11:06:28 : COLUMN=TO_SETUP_ID, VALUE=1 18-AUG 11:06:28 :
ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITIONS_U1) violated 18-AUG 11:06:28 : ======================================== 18-AUG
11:06:28 : Error in PROCEDURE=LOAD_SETUP_TRANSITION, TABLE=MSC_SETUP_TRANSITIONS 18-AUG 11:06:28 : COLUMN=ORGANIZATION_CODE,
VALUE=TST:M1 18-AUG 11:06:28 : COLUMN=RESOURCE_ID, VALUE=16 18-AUG
11:06:28 : COLUMN=FROM_SETUP_ID, VALUE=1 18-AUG 11:06:28 :
COLUMN=TO_SETUP_ID, VALUE=2 18-AUG 11:06:28 : ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITIONS_U1) violated 18-AUG 11:06:28 :
======================================== 18-AUG 11:06:28 : Error in PROCEDURE=LOAD_SETUP_TRANSITION, TABLE=MSC_SETUP_TRANSITIONS 18-AUG
11:06:28 : COLUMN=ORGANIZATION_CODE, VALUE=TST:M1 18-AUG 11:06:28 :
COLUMN=RESOURCE_ID, VALUE=16 18-AUG 11:06:28 : COLUMN=FROM_SETUP_ID,
VALUE=2 18-AUG 11:06:28 : COLUMN=TO_SETUP_ID, VALUE=1 18-AUG 11:06:28 :
ORA-00001: unique constraint (MSC.MSC_SETUP_TRANSITIONS_U1) violated 18-AUG 11:06:28 : Total resource transition = 167 18-AUG 11:06:28 : .1 minutes elapsed.
18-AUG 11:06:30 : Procedure MSC_CL_RPO_ODS_LOAD.LOAD_IRO_DEMAND;
started. 18-AUG 11:06:31 : <<LOAD_IRO_DEMAND>> 18-AUG 11:06:31 :
<<CURSOR>>INSERT /*+ APPEND */ INTO DEMANDS_TST( PLAN_ID, DEMAND_ID, DISPOSITION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, USING_ASSEMBLY_ITEM_ID, USING_ASSEMBLY_DEMAND_DATE, USING_REQUIREMENT_QUANTITY, QUANTITY_PER_ASSEMBLY, ISSUED_QUANTITY, ASSEMBLY_DEMAND_COMP_DATE, DEMAND_TYPE, ORIGINATION_TYPE, SOURCE_ORGANIZATION_ID, RESERVATION_ID, OP_SEQ_NUM, DEMAND_CLASS, REPETITIVE_SCHEDULE_ID, SR_INSTANCE_ID, PROJECT_ID, TASK_ID, PLANNING_GROUP, UNIT_NUMBER, ORDER_NUMBER, REPAIR_LINE_ID, WIP_ENTITY_ID, WIP_ENTITY_NAME, WIP_STATUS_CODE, WIP_SUPPLY_TYPE, ASSET_ITEM_ID, ASSET_SERIAL_NUMBER, COMPONENT_SCALING_TYPE, COMPONENT_YIELD_FACTOR,null,null, REFRESH_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY)SELECT -1, MSC_DEMANDS_S.nextval, NVL(ms.TRANSACTION_ID,-1) DISPOSITION_ID, t1.INVENTORY_ITEM_ID, msd.ORGANIZATION_ID, t2.INVENTORY_ITEM_ID USING_ASSEMBLY_ITEM_ID, nvl(msd.USING_ASSEMBLY_DEMAND_DATE,ms.new_schedule_date),
msd.USING_REQUIREMENT_QUANTITY, msd.QUANTITY_PER_ASSEMBLY, msd.QUANTITY_ISSUED, msd.ASSEMBLY_DEMAND_COMP_DATE, msd.DEMAND_TYPE, msd.ORIGINATION_TYPE, msd.SOURCE_ORGANIZATION_ID, msd.RESERVATION_ID, msd.OPERATION_SEQ_NUM, msd.DEMAND_CLASS, msd.REPETITIVE_SCHEDULE_ID, msd.SR_INSTANCE_ID, msd.PROJECT_ID, msd.TASK_ID, msd.PLANNING_GROUP, msd.END_ITEM_UNIT_NUMBER,
REPLACE(REPLACE(substr(msd.ORDER_NUMBER,1,62),:v_chr10),:v_chr13)
ORDER_NUMBER, REPAIR_LINE_ID , msd.WIP_ENTITY_ID, msd.WIP_ENTITY_NAME, msd.WIP_STATUS_CODE, msd.WIP_SUPPLY_TYPE, t3.inventory_item_id ASSET_ITEM_ID, msd.ASSET_SERIAL_NUMBER, msd.COMPONENT_SCALING_TYPE, msd.COMPONENT_YIELD_FACTOR,null,null, :v_last_collection_id, :v_current_date, :v_current_user, :v_current_date, :v_current_user FROM MSC_ITEM_ID_LID t1, MSC_ITEM_ID_LID t2, MSC_ITEM_ID_LID t3,SUPPLIES_TST ms, MSC_ST_DEMANDS msd WHERE msd.SR_INSTANCE_ID= 21 AND msd.ORIGINATION_TYPE = 77 AND msd.DELETED_FLAG= 2 AND t1.SR_INVENTORY_ITEM_ID= msd.inventory_item_id AND t1.sr_instance_id= msd.SR_INSTANCE_ID AND t2.SR_INVENTORY_ITEM_ID= msd.using_assembly_item_id AND t2.sr_instance_id= msd.SR_INSTANCE_ID AND t3.SR_INVENTORY_ITEM_ID (+)= msd.ASSET_ITEM_ID AND t3.sr_instance_id (+) = msd.SR_INSTANCE_ID AND ms.sr_instance_id= msd.SR_INSTANCE_ID AND ms.ORGANIZATION_ID= msd.ORGANIZATION_ID AND ms.DISPOSITION_ID= msd.repair_line_id AND ms.plan_id=-1 AND ms.ORDER_TYPE= 75 18-AUG
11:06:31 : ORA-01747: invalid user.table.column, table.column, or column specification 18-AUG 11:06:31 : .1 minutes elapsed.
===================================================
any help is appreciated. Just got this Bug 8661320, ref with no help. Its on R12 12.1.1

Sundeep,
No similar errors are reported in Metalink, so I would suggest you log a SR.
Regards,
Hussein

Regarding ORA-00001: unique constraint violation error

Hi ,
This is Venkat. I am new to OWB.
When I run the mapping I am getting the ORA-00001: unique constraint violation error.
My loading type is Update/Insert.
My target table Primarykey is combination of 3 keys.
Please give me the suggestions. It is very urgent.
Thanks,
Venkat

1) If you can disable/drop the indexes on the table, you can load the data and then do a SQL query grouping by the PK/UI to show which rows have a count > 1 i.e. the duplicates.
2) If you can't alter the target table, perhaps create a dummy copy of the table without pk/indexes and load to that and then do above query.
3) Run the mapping via the debugger and set a breakpoint just before your target table and examine the data to see if you can spot the duplicates.
4) Put a deduplicator into the mapping (just before target table), this may allow you to load data but doesn't solve the real problem as to why you have duplicates.
Si

Error import 4.1.1 ORA-00001: unique constraint (FLOWS_030100.WWV_FLOW_FLOW

In 4.1.0 and 4.1.1 (on APEX.ORACLE.COM also) when importing and installing an application, we have the following error :
ORA-20001: GET_BLOCK Error. ORA-20001: GET_STMT error. ORA-20001: Execution of the statement was unsuccessful. ORA-00001: unique constraint (FLOWS_030100.WWV_FLOW_FLOW_PK) violated
This is the same error as in :
Import error: ORA-00001:unique constraint (FLOWS_030100.WWV_FLOW_FLOW_PK)
(opened a new thread because the other one is marked as answered)
Solution :
- Check the export file and check the wwv_flow_api.create_flow parameters. In our case we saw that p_vpd had a lot of text.
So here is what we did :
- Remove text from Security / Database Session / Initialization PL/SQL Code (VPD)
- export application
- import application
- put text back in Security.
(This VPD code will be implemented in a package so the problem should go away.)
But this seems to be a problem with a parameter being too long in the wwv_flow_api.create_flow procedure.
Francis.

Hi
I am getting same error while importing shared component file.
ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-00001: unique constraint (APEX_030200.WWV_FLOW_MENU_TEMP_IDX2) violated
*<pre>begin begin*
wwv_flow_api.create_menu_template ( p_id=&gt; 94480251996632657 + wwv_flow_api.g_id_offset,
p_flow_id=&gt; wwv_flow.g_flow_id, p_name=&gt;'Breadcrumb Menu', p_before_first=&gt;'', p_current_page_option=&gt;'&lt;a href=&quot;#LINK#&quot; class=&quot;t20Current&quot;&gt;#
If this is because of long parameter then how to find which parameter is too long?

ORA-00001 - unique constraint violation when upgrading 10g EUL

Hi,
I am trying to upgrade my Discoverer 4i to Discoverer 10g.
When I log into 10g, it prompts me to upgrade the EUL. After making the right back up of my 4i EUL, I continue with the upgrade.
During the upgrade, I am hit with this error:
Database error: ORA-00001 unique constraint (EUL_HRMS.EUL5_FOL_UK_1) violated.
I understand that this happens when user tries to insert an already existing value into a column defined as unique. However, I am not sure on how to resolve it.
Can anyone please advice.
Thanks in advance!
Regards,
Harpreet Sidhu

Hi Rod,
I've run the queries and these are the results. Each query returned one row.
1. SELECT FROM EUL_HRMS.EUL5_DOC_FOLDERS*
FOL_ID     100057
FOL_NAME     ROOT
FOL_DEVELOPER_KEY     ROOT
FOL_DESCRIPTION
FOL_EU_ID     100000
FOL_PARENT_ID
FOL_USER_PROP2
FOL_USER_PROP1
FOL_ELEMENT_STATE     0
FOL_CREATED_BY     EUL_HRMS
FOL_CREATED_DATE     19-Jun-09
FOL_UPDATED_BY     EUL_HRMS
FOL_UPDATED_DATE     19-Jun-09
NOTM     0
2. SELECT EU_ID, EU_SECURITY_MODEL, EU_USE_PUB_PRIVS, EU_ROLE_FLAG
FROM EUL_HRMS.EUL5_EUL_USERS
WHERE EU_USERNAME = 'PUBLIC'
EU_ID     3000
EU_SECURITY_MODEL     0
EU_USE_PUB_PRIVS     1
EU_ROLE_FLAG     0
Thanks!

ORA-00001: unique constraint

Hi,
I disabled the primary key of the table to which I insert the data like this :
INSERT INTO TABLE_X
select * from table_1 UNION ALL
select * from table_2 ;
but I receive this error :
ORA-00001: unique constraint TABLE_X.PK violated
Why ? It is already disabled.
thank you.
Message was edited by:
user522961
Message was edited by:
user522961
Message was edited by:
user522961

Is it possible you kept the index when disabling the primary key?
YAS@11G>create table t as select object_id from all_objects where rownum<=10;
Table created.
YAS@11G>alter table t add constraint PK_T primary key(object_id);
Table altered.
YAS@11G>alter table t disable constraint pk_t;
Table altered.
YAS@11G>insert into t select * from t;
10 rows created.
YAS@11G>rollback;
Rollback complete.
YAS@11G>alter table t enable constraint pk_t;
Table altered.
YAS@11G>alter table t disable constraint pk_t keep index;
Table altered.
YAS@11G>insert into t select * from t;
insert into t select * from t
ERROR at line 1:
ORA-00001: unique constraint (YAS.PK_T) violated

ORA-00001: unique constraint @ impdp with table_exists_action=truncate

Hi everybody
I can't understand why my data pump import execution with parameter TABLE_EXISTS_ACTION=TRUNCATE returned ORA-00001 (unique constraint violation), while importing schema tables from a remote database where the source tables have the same unique constraints as the corresponding ones on the target database.
Now my question is "If the table would be truncated, why I get unique constraint violation when inserting records from a table where the same unique constraint is validated?
Here are the used parameter file content and the impdp logfile.
parfile
{code}
DIRECTORY=IMPEXP_LOG_COLL2
CONTENT=DATA_ONLY
NETWORK_LINK=PRODUCTION
PARALLEL=1
TABLE_EXISTS_ACTION=TRUNCATE
EXCLUDE=STATISTICS
{code}
logfile
{code}
Import: Release 10.2.0.1.0 - Production on Gioved� 22 Ottobre, 2009 15:33:44
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connesso a: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
FLASHBACK automatically enabled to preserve database integrity.
Starting "IMPEXP"."PROVA_REFRESH_DBCOLL": impexp/********@dbcoll SCHEMAS=test_pump LOGFILE=test_pump.log parfile=refresh_dbcoll.par JOB_NAME=prova_refresh_dbcoll
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 523 MB
ORA-31693: Table data object "TEST_PUMP"."X10000000_TRIGGER" failed to load/unload and is being skipped due to error:
ORA-00001: unique constraint (TEST_PUMP.SYS_C00726627) violated
ORA-31693: Table data object "TEST_PUMP"."X10000000_BASIC" failed to load/unload and is being skipped due to error:
ORA-00001: unique constraint (TEST_PUMP.SYS_C00726625) violated
Job "IMPEXP"."PROVA_REFRESH_DBCOLL" completed with 2 error(s) at 15:34:04
{code}
Thank you
Bye Alessandro

I forgot to read the last two lines of the documentation about TABLE_EXISTS_ACTION where it says:
"TRUNCATE cannot be used on clustered tables or over network links."
So it seems that it ignored the clause for the use of NETWORK_LINK and unreasonably opted for an APPEND action instead of throwing an error to highlight the conflicting parameters in the used configuration.
Bye Alessandro

ORA-00001: unique constraint (REMEDY.SYS_C001727

Hi: I have a simple table with a primary key (ENTRYID). All other fields are just fields with no constraints. When I try to insert records, for some records I get the above error. The table does not already have this record.
INSERT INTO REMEDY.VITALEXCEPTION (ENTRYID, CUSTID, DEVICENAME, INTERFACE, EXCEPTION, DURATION, TIME)
VALUES ('jvis2rspm01.S0/0/0_FMS:65999591 NA:3836400887 TERM:cmny83bbf/20351BDU1182798445', 'fxms', 'jvis2rspm01', 'S0/0/0_FMS:65999591 NA:3836400887 TERM:cmny83bbf/20351', 'BDU', 5476, 1182792934);
INSERT INTO REMEDY.VITALEXCEPTION (ENTRYID, CUSTID, DEVICENAME, INTERFACE, EXCEPTION, DURATION, TIME)
ERROR at line 1:
ORA-00001: unique constraint (REMEDY.SYS_C001727) violated
Could someone help.
Thanks
Ray

hi,
can you post the table structure?
I suspect that ENTRYID has lesser length than the actual value and in effect the value has been truncated for some reason.
The primary key value is too long, maybe creating a surrogate key would help.
J

ORA-00001 UNIQUE CONSTRAINT ERROR ON SYS.WRH$_SQLTEXT_PK?

Similar Messages

Maybe you are looking for