Uniqueness constraint violation: service
Hi;
I upgrade to bpel 3.1.3.5.0; and after i cannot create a web service proxy from bpel process ! i always had this error "uniqueness constraint violation: service "
Any ideas
WSDLs were supplied by third party managing the web service I am attempting to generate the proxies for. I'm unsure of the method used to create the WSDL files.
Similar Messages
-
ORA-00001 Unique constraint Violation Error
We are upgrading our NW BW 7.01 java server to 7.3 and during the Downtime phase of the Installer, while running the Offline Migration, we are getting an error "EP-KM-BC: Unique Constraint Violation error: ORA-000001". Unknown Object# (12xxxxxx) does not exist. We have one CI and two DI. Any help would be greatly appreciated.
Hi Anil,
You need to clear the data from the table
1. SHD_AP_PROPVALUE
2. SHD_KMC_AP_PROP
3. SHD_AP_MC
Repeat the phase and also follow the sapnote
1873288 - RUN_OFFLINE_MIGRATION phase fails during SAP NetWeaver migration
Also paste the logs of RUN_OFFLINE_MIGRATION phase.
With Regards
Ashutosh Chaturvedi -
Unique Constraint Violation on Merge
I'm getting a unique constraint violation on the following but I don't understand why. I know there are duplicates on remote.customer_id but I'm doing a distinct on that column but still the error. In my local table, customer_id is the primary key so it must be unique. If I remove the primary key constraint altogether, the error goes away.
Can anyone tell me why both DISTINCT and UNIQUE fail to eliminate duplicates in this merge statement? I have confirmed that remote.customer_id is the source of the duplicates.
merge into CUSTOMER c
using (
select DISTINCT remote.customer_id,
remote.name_1,
remote.name_2,
remote.name_3,
remote.name_4,
remote.house_number_and_street,
remote.city,
remote.region,
remote.country_code,
remote.postal_code,
p.customer_id_of_bus_partner
from D_CUSTOMER@BW_LINK remote
left join D_CUSTOMER_PARTNER_FUNCTIONS@BW_LINK p
on p.customer_id = remote.customer_id
where p.partner_function_id = 'ZS'
) remote
on (c.customer_id = remote.customer_id)
when matched then
update set c.name_1 = remote.name_1,
c.name_2 = remote.name_2,
c.name_3 = remote.name_3,
c.name_4 = remote.name_4,
c.house_number_and_street = remote.house_number_and_street,
c.city = remote.city,
c.region = remote.region,
c.country_code = remote.country_code,
c.postal_code = remote.postal_code
when not matched then
insert (c.customer_id,
c.name_1,
c.name_2,
c.name_3,
c.name_4,
c.house_number_and_street,
c.city,
c.region,
c.country_code,
c.postal_code,
c.customer_id_of_bus_partner
values (remote.customer_id,
remote.name_1,
remote.name_2,
remote.name_3,
remote.name_4,
remote.house_number_and_street,
remote.city,
remote.region,
remote.country_code,
remote.postal_code,
remote.customer_id_of_bus_partner
LOG ERRORS INTO DML_ERROR_LOG ('Customer Merge') REJECT LIMIT 5;
Edited by: bjiggs on Mar 25, 2010 10:56 AMWhen you mentioned the following in previous post...
+unable to get a stable set of rows in the source tables+
...I suspected this :-)
This is EQUIVALENT to "Mutating Table trigger/function" error...
...in the sense that the the "target rows" which are
supposed to be changed (by this statement)
are FOUND/MATCHED in the "source result set" MULTIPLE TIMESThe main reason this error comes up is...
In the SOURCE result set, there are MORE than one ROW that MATCHED the TARGET result set.
In this scenario the row with PK=3 matches more than one SOURCE rows, which one is supposed to be used for updating?
Yes indeed, oracle is unable to get a stable set of rows in source tables.
However the PK=4 is not matched in the target result set, so the statement will attenpt to insert both rows resulting in UNIQUE contraint error.
This was the case with OP in this posts.
This can be seen in your example by commenting one of the rows in table S with PK=3.
sudhakar@ORCL>drop table D;
Table dropped.
sudhakar@ORCL>drop table S;
Table dropped.
sudhakar@ORCL>create table D ( pk number, a varchar2(10),
2 constraint d_pk primary key (pk));
Table created.
sudhakar@ORCL>
sudhakar@ORCL>insert into D values( 1, 'a');
1 row created.
sudhakar@ORCL>insert into D values( 2, 'a');
1 row created.
sudhakar@ORCL>insert into D values( 3, 'a');
1 row created.
sudhakar@ORCL>
sudhakar@ORCL>commit;
Commit complete.
sudhakar@ORCL>
sudhakar@ORCL>create table S ( pk number, a varchar2(10));
Table created.
sudhakar@ORCL>
sudhakar@ORCL>insert into S values( 1, 'b');
1 row created.
sudhakar@ORCL>insert into S values( 2, 'b');
1 row created.
sudhakar@ORCL>insert into S values( 3, 'b');
1 row created.
sudhakar@ORCL>--insert into S values( 3, 'b');
sudhakar@ORCL>insert into S values( 4, 's');
1 row created.
sudhakar@ORCL>insert into S values( 4, 't');
1 row created.
sudhakar@ORCL>
sudhakar@ORCL>commit;
Commit complete.
sudhakar@ORCL>
sudhakar@ORCL>
sudhakar@ORCL>merge into d
2 using s
3 on (d.pk = s.pk)
4 when matched then update
5 set d.a = s.a
6 when not matched then insert
7 (d.pk, d.a)
8 values (s.pk, s.a);
merge into d
ERROR at line 1:
ORA-00001: unique constraint (SUDHAKAR.D_PK) violated
sudhakar@ORCL>vr,
Sudhakar B. -
Unique constraint violation on version enabled table
hi!
we're facing a strange problem with a version enabled table that has an unique constraint on one column. if we rename an object stored in the table (the name-attribute of the object is the one that has a unique constraint on the respective column) and rename it back to the old name again, we get an ORA-00001 unique constraint violation on the execution of an update trigger.
if the constraint is simply applied as before to the now version enabled table, I understand that this happens, but shouldn't workspace manager take care of something like that when a table with unique constraints is version enabled? (the documentation also says that) because taking versioning into account it's not that we try to insert another object with the same name, it's the same object at another point in time now getting back it's old name.
we somewhat assume that to be a pretty standard scenario when using versioned data.
is this some kind of bug or do we just miss something important here?
more information:
- versioning is enabled on all tables with VIEW_WO_OVERWRITE and no valid time support
- database version is 10.2.0.1.0
- wm installation output:
ALLOW_CAPTURE_EVENTS OFF
ALLOW_MULTI_PARENT_WORKSPACES OFF
ALLOW_NESTED_TABLE_COLUMNS OFF
CR_WORKSPACE_MODE OPTIMISTIC_LOCKING
FIRE_TRIGGERS_FOR_NONDML_EVENTS ON
NONCR_WORKSPACE_MODE OPTIMISTIC_LOCKING
NUMBER_OF_COMPRESS_BATCHES 50
OWM_VERSION 10.2.0.1.0
UNDO_SPACE UNLIMITED
USE_TIMESTAMP_TYPE_FOR_HISTORY ON
- all operations are done on LIVE workspace
any help is appreciated.
EDIT: we found out the following: the table we are talking about is the only table where the unique constraint is left. so there must have been a problem during version enabling. on another oracle installation we did everything the same way and the unique constraint wasn't left there, so everything works fine.
regards,
Andreas Schilling
Message was edited by:
aschillinghi!
we're facing a strange problem with a version enabled table that has an unique constraint on one column. if we rename an object stored in the table (the name-attribute of the object is the one that has a unique constraint on the respective column) and rename it back to the old name again, we get an ORA-00001 unique constraint violation on the execution of an update trigger.
if the constraint is simply applied as before to the now version enabled table, I understand that this happens, but shouldn't workspace manager take care of something like that when a table with unique constraints is version enabled? (the documentation also says that) because taking versioning into account it's not that we try to insert another object with the same name, it's the same object at another point in time now getting back it's old name.
we somewhat assume that to be a pretty standard scenario when using versioned data.
is this some kind of bug or do we just miss something important here?
more information:
- versioning is enabled on all tables with VIEW_WO_OVERWRITE and no valid time support
- database version is 10.2.0.1.0
- wm installation output:
ALLOW_CAPTURE_EVENTS OFF
ALLOW_MULTI_PARENT_WORKSPACES OFF
ALLOW_NESTED_TABLE_COLUMNS OFF
CR_WORKSPACE_MODE OPTIMISTIC_LOCKING
FIRE_TRIGGERS_FOR_NONDML_EVENTS ON
NONCR_WORKSPACE_MODE OPTIMISTIC_LOCKING
NUMBER_OF_COMPRESS_BATCHES 50
OWM_VERSION 10.2.0.1.0
UNDO_SPACE UNLIMITED
USE_TIMESTAMP_TYPE_FOR_HISTORY ON
- all operations are done on LIVE workspace
any help is appreciated.
EDIT: we found out the following: the table we are talking about is the only table where the unique constraint is left. so there must have been a problem during version enabling. on another oracle installation we did everything the same way and the unique constraint wasn't left there, so everything works fine.
regards,
Andreas Schilling
Message was edited by:
aschilling -
Unique constraint violation error
Hello All,
I have a procedure called - FHM_DASHBOARD_PROC which inserts the data into a table called FHM_DASHBOARD_F fetching records from several tables. However, for a particular type of record, that data is not being inserted because of the Unique constraint violation
the procedure is:
create or replace
PROCEDURE FHM_DASHBOARD_PROC AS
DB_METRICS_CNT1Z number;
--V_PODNAME varchar2(10);
V_KI_CODE_DB_STATSZ varchar2(50);
V_ERRORSTRING varchar2(100);
--CURSOR PODNAME_CUR IS SELECT PODNAME,SHORTNAME FROM CRMODDEV.POD_DATA WHERE PODSTATUS_ID=1 AND PODTYPE_ID=1 ORDER BY PODNAME;
-- DB STATS
BEGIN
-- OPEN PODNAME_CUR;
-- LOOP
-- FETCH PODNAME_CUR INTO V_PODNAME,V_POD_SHORTNAME ;
-- EXIT WHEN PODNAME_CUR%NOTFOUND;
BEGIN
SELECT COUNT(*) INTO DB_METRICS_CNT1Z FROM FHM_DB_METRICS_F A, FHM_DB_D B where A.DBNAME=B.DBNAME and PODNAME=V_PODNAME AND DB_DATE=TRUNC(SYSDATE-1);
DBMS_OUTPUT.PUT_LINE('DB_METRICS_CNT1Z :'|| DB_METRICS_CNT1Z);
IF DB_METRICS_CNT1Z >0 THEN
DBMS_OUTPUT.PUT_LINE('DB STATS');
INSERT INTO FHM_DASHBOARD_F(PODNAME,DASH_DATE,KI_CODE,KI_VALUE,KI_STATUS)
(SELECT PODNAME, DASH_DATE AS CU_DATE, KI.KI_CODE, NVL(PF.KI_VALUE,0),
CASE
WHEN PF.KI_VALUE = ki.warning_threshold then 2
when PF.KI_VALUE=0 then 0
ELSE 1
END AS ALERT_STATUS
FROM
(SELECT PODNAME,DB_DATE AS DASH_DATE,decode(a.stats_last_status,'SUCCEEDED',1,'FAILED',2,'STOPPED',2,NULL,0) KI_VALUE from
FHM_DB_METRICS_F a,fhm_db_d b where a.dbname=b.dbname and podname='XYZ' and db_date=TRUNC(SYSDATE-1) and dbtype='OLTP')PF,
FHM_KEY_INDICATOR_D KI where PF.PODNAME=KI.POD_NAME AND KI.TIER_CODE=3 AND KI.KI_NAME='DB_STATS'
AND (PF.PODNAME,TRUNC(PF.DASH_DATE),KI.KI_CODE) NOT IN (SELECT PODNAME,DASH_DATE,KI_CODE FROM FHM_DASHBOARD_F));
COMMIT;
ELSE
SELECT KI_CODE INTO V_KI_CODE_DB_STATSZ FROM FHM_KEY_INDICATOR_D WHERE POD_NAME=V_PODNAME AND KI_NAME='DB_STATS';
DBMS_OUTPUT.PUT_LINE('V_KI_CODE_DB_STATSZ :'||V_KI_CODE_DB_STATSZ);
INSERT INTO FHM_DASHBOARD_F(PODNAME,DASH_DATE,KI_CODE,KI_VALUE,KI_STATUS) VALUES(V_PODNAME,TRUNC(SYSDATE-1),V_KI_CODE_DB_STATSZ,0,0);
COMMIT;
END IF;
EXCEPTION
WHEN OTHERS THEN
V_ERRORSTRING :='INSERT INTO FHM_DASHBOARD_F_ERROR_LOG(POD_NAME,KI_NAME,ERRORNO,ERRORMESSAGE,DATETIME) VALUES
('''||V_PODNAME||''',''DB_STATS'','''||SQLCODE||''','''||SQLERRM||''',SYSDATE)';
EXECUTE IMMEDIATE V_ERRORSTRING;
COMMIT;
END;
--END LOOP;
--CLOSE PODNAME_CUR;
END;
END FHM_DASHBOARD_PROC;and the table where the data is inserting is
CREATE TABLE "CRMODDEV"."FHM_DASHBOARD_F"
"PODNAME" VARCHAR2(25 BYTE) NOT NULL ENABLE,
"DASH_DATE" DATE,
"KI_CODE" NUMBER NOT NULL ENABLE,
"KI_VALUE" NUMBER,
"KI_STATUS" NUMBER,
CONSTRAINT "FHM_DASHBOARD_F_DATE_PK" PRIMARY KEY ("DASH_DATE", "PODNAME", "KI_CODE") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING COMPUTE STATISTICS STORAGE(INITIAL 4194304 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "CRMODDEV_IDX" ENABLE,
CONSTRAINT "FHM_DASHBOARD_F_KI_CODE_FK" FOREIGN KEY ("KI_CODE") REFERENCES "CRMODDEV"."FHM_KEY_INDICATOR_D" ("KI_CODE") ENABLE
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE
INITIAL 3145728 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT
TABLESPACE "CRMODDEV_TBL" ENABLE ROW MOVEMENT ;the Primary key constraint is FHM_DASHBOARD_F_DATE_PK and is on 3 columns of the table DASH_DATE, PODNAME, KI_CODE
And this is the query used in the Procedure for inserting the data into the table
(SELECT PODNAME, DASH_DATE AS CU_DATE, KI.KI_CODE, NVL(PF.KI_VALUE,0),
CASE
WHEN PF.KI_VALUE = ki.warning_threshold then 2
when PF.KI_VALUE=0 then 0
ELSE 1
END AS ALERT_STATUS
From
(Select Podname,Db_Date As Dash_Date,Decode(A.Stats_Last_Status,'SUCCEEDED',1,'FAILED',2,'STOPPED',2,Null,0) Ki_Value From -- Added Distinct
FHM_DB_METRICS_F a,fhm_db_d b where a.dbname=b.dbname and podname in ('XYZ') and db_date = TRUNC(SYSDATE-2) and dbtype='OLTP')PF,
Fhm_Key_Indicator_D Ki Where Pf.Podname=Ki.Pod_Name And Ki.Tier_Code=3 And Ki.Ki_Name='DB_STATS'
And (Pf.Podname,Trunc(Pf.Dash_Date),Ki.Ki_Code) Not In (Select Podname,Dash_Date,Ki_Code From Fhm_Dashboard_F));It gives *2 record* as result
XYZ 20-JAN-12 2521 1 1
XYZ 20-JAN-12 2521 1 1
So it gives Unique constraint violation error while inserting. Then, I changed in the above inserting code by adding a distinct clause. After that the query gives only ONE record as result. However, that record also is not being inserted into the table and giving the same error.
Now the question is How shall I insert this record into the table successfully ?
Though the message is too long, However, I have given you the full structure of the object/procedure and error.
Thank You in Advance.when you have 5 columns in the result set adding DISTINCT is n ot the solution as you may get the same error again.
Check the target table whether the data exists before inserting ..if not check the table structure for unique constraint created on other columns.
select *from <table_name>
where
DASH_DATE=date '2012-01-20'
and PODNAME='XYZ'
and KI_CODE=2521; -
Hi,
I am a newbie to oracle..
I have a composite primary key consisting of sequence,reg_no,srvc_code and srvc_type..
when i tried inserting a record through the application it is showing that Unique constraint violated..But i did not find the record in the table for the same values
and if I insert the same values with an sql insert statement,the record is inserted successfully..Please suggest me the possibilities of getting such an error.952759 wrote:
Hi,
I am a newbie to oracle..
I have a composite primary key consisting of sequence,reg_no,srvc_code and srvc_type..
when i tried inserting a record through the application it is showing that Unique constraint violated..But i did not find the record in the table for the same values
and if I insert the same values with an sql insert statement,the record is inserted successfully..Please suggest me the possibilities of getting such an error.Either Oracle is mistaken or you are mistaken.
I'll give you 1000 to 1 odds that Oracle is correct & you are mistaken.
How can we reproduce what you report?
How do I ask a question on the forums?
SQL and PL/SQL FAQ -
Reattempt of insert after a ORA-0001 unique constraint violation
Hi,
I'm inserting into a table. The primary key on this table is made up of the user id and a one-up transaction number. Unfortunately, I cannot change the design of this table.
Because I have to query the table to get the next transaction number before I insert into the table, I sometimes get a ORA-0001 (unique constraint violation) error because some other session grabbed the next transaction number and committed before I did.
To deal with this I retry the insert, that is, read the table again for the next tran number and insert. I allow for this up to 3 times. If after the third attempt I fail again, I rollback.
I'm seeing 3 records in the table.
So here are my questions: Do I need to rollback when I get the ORA-0001 error? I thought I wouldn't have to. If I do, why? The insert failed, how could the commit statement commit 3 records?
Thanks!No, the userid and transaction numbers are not the same (combined) for each of the 3 rows.
Here is the logic to retry again when I get a ORA-0001:
PROCEDURE insert_record(
table1_rec_in IN table1%ROWTYPE,
tran_number OUT table1.trans_number%TYPE,
attempt_number IN PLS_INTEGER)
IS
next_tran_number table1.trans_number%TYPE;
BEGIN
SELECT NVL(MAX(trans_number), 0) + 1
INTO next_tran_number
FROM table1
WHERE userid = table1_rec_in.table1_userid;
INSERT INTO table1
(userid,
trans_number,
amount,
transdate)
VALUES
(table1_rec_in.userid,
next_tran_number,
table1_rec_in.amount,
SYSDATE);
tran_number := next_tran_number;
EXCEPTION
WHEN DUP_VAL_ON_INDEX THEN
IF attempt_number < 3
THEN
DECLARE
next_attempt_number PLS_INTEGER;
BEGIN
next_attempt_number := attempt_number + 1;
insert_record(
table1_rec_in,
tran_number,
next_attempt_number);
END;
ELSE
RAISE unable_to_insert_rec;
END IF;
WHEN OTHERS THEN
RAISE unable_to_insert_rec;
END;
I'm using recursion to try the insert again. Is this the source of my problems? I don't see it and can't reproduce it. -
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,
Venkat1) 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 -
Help needed for PK_REV_COL unique constraint violation
We’re receiving a SNPW.PK_REV_COL unique constraint violation when trying to reverse a pipe delimited source file. There are no duplicate column names within the source file but the same column names are used across several different input files. Does anyone have a solution to this problem?
Hi,
This is a problem with the Reversed tables from ODI.
Go to work repository and truncate any "snp_rev...." tables.
That should solves it.
Cezar Santos
[www.odiexperts.com]
Edited by: Cezar Santos - www.odiexperts.com on 20/10/2009 15:34 -
Post Process Event Handler ----Unique Constraint Violation--Create User
Hi Evryone..
I am creating the user using the create user request template and there is one level of approval for this.
I have one pre process event handler which populates one field A and one post process event handler which updates some 3 fields in the user form .
In request template itself we had placed value as "ABC" for field B and this field B will be overridden in the post process event handler with Value as "XYZ" .
Now when i raise the request the user is getting created in OIM but the value XYZ is not getting replaced in the field B.
Below are the errors which i got in the logs while executing post process event handler :
<Mar 28, 2012 10:25:58 AM CDT> <Warning> <oracle.iam.callbacks.common> <IAM-2030146> <[CALLBACKMSG] Are applicable policies present for this async eventhandler ? : false>
<Mar 28, 2012 10:25:59 AM CDT> <Warning> <org.eclipse.persistence.session.oim> <BEA-000000> <
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.1.3.v20110304-r9073): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_OIM.UK_UAR_ATTR_NAME_VALUE) violated
Error Code: 1
Call: INSERT INTO USR_ATTRIBUTE_RESERVATIONS (UAR_RESERVATION_KEY, UAR_ATTRIBUTE_NAME, CREATED_BY, CREATED_ON, DATA_LEVEL, UAR_REQUEST_ID, UAR_RESERVED_VALUE, UPDATED_BY, UPDATED_ON) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)
bind => [10, User Login, null, null, null, 10, DUMMY14, null, null]
Query: InsertObjectQuery([email protected]658269)
Exception at usrIntf.updateUser IAM-3050128 : Cannot reserve user attribute User Login with value DUMMY14 in OIMDB. Corresponding request ID is 10.:User Login:DUMMY14:10
I checked reservations table and there are no records in that table.
Has any one faced this issue..if so how it can be resolved..Are you trying to update the User ID? As far as I know during create user requests, OIM reserves the user login as it goes through approval and you cannot update that directly I think. I haven't tried it but can you tell me which fields you are prepopulating and which are you updating? Are there any OOTB fields in this or UDF?
-Bikash -
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 SidhuHi 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! -
Unique constraint violation while updating a non PK column
Hi,
I seem to have found this strange error.
What I try to do is bulk fetch a cursor in some table arrays. with limit of 1000
Then using a forall and a save exceptions at the end
I update a table with the values inside one of the table arrays.
The column I update is not part of a PK
I catch the error message: ORA-24381
by using PRAGMA exception_init(dml_errors, -24381);
and later on :
WHEN dml_errors THEN
errors := SQL%BULK_EXCEPTIONS.COUNT;
FOR i IN 1..sql%BULK_EXCEPTIONS.count LOOP
lr_logging.parameters:= 'index = ' || sql%BULK_EXCEPTIONS(i).error_index || 'error = ' ||Sqlerrm(-sql%BULK_EXCEPTIONS(i).error_code) ;
END LOOP;
I insert these errors in another table. and i get 956 errors
first one is :
index = 3error = ORA-00001: unique constraint (.) violated
last one is
index = 1000error = ORA-00001: unique constraint (.) violated
How can this be.Since i don't update in a PKcolumn.
FULL CODE IS:
PROCEDURE Update_corr_values( as_checkdate_from IN VARCHAR2,
as_checkdate_until IN VARCHAR2,
as_market IN VARCHAR2
IS
LS_MODULE_NAME CONSTANT VARCHAR2(30) := 'update_values';
lr_logging recon_logging.logrec;
CURSOR lc_update IS
SELECT /*+ORDERED*/c.rowid,c.ralve_record_id,d.value,c.timestamp,f.value
FROM rcx_allocated_values a,
rcx_allocated_values b,
meter_histories e,
rcx_allocated_lp_value c,
rcx_allocated_lp_value d,
counter_values f
WHERE a.slp_type NOT IN ('S89', 'S88', 'S10', 'S30') --AELP
AND b.slp_type IN ('S89', 'S88') --residu
AND a.valid_from >= to_date(as_checkdate_from,'DDMMYYYY HH24:MI')
AND a.valid_to <= to_date(as_checkdate_until,'DDMMYYYY HH24:MI')
AND a.market = as_market
AND a.market = b.market
AND a.ean_sup = b.ean_sup
AND a.ean_br = b.ean_br
AND a.ean_gos = b.ean_gos
AND a.ean_dgo = b.ean_dgo
AND a.direction = b.direction
AND a.valid_from = b.valid_from
AND a.valid_to = b.valid_to
AND c.ralve_record_id = a.record_id
AND d.ralve_record_id = b.record_id
AND c.TIMESTAMP = d.TIMESTAMP
AND e.ASSET_ID = 'KCF.SLP.' || a.SLP_TYPE
--AND f.timestamp between to_date(gs_checkdate_from,'ddmmyyyy') and to_Date(as_checkdate_until,'ddmmyyyy')
AND e.SEQ = f.MHY_SEQ
AND f.TIMESTAMP =c.timestamp - 1/24
ORDER BY c.rowid;
TYPE t_value IS TABLE OF RCX_ALLOCATED_LP_VALUE.VALUE%TYPE;
TYPE t_kcf IS TABLE OF COUNTER_VALUES.VALUE%TYPE;
TYPE t_timestamp IS TABLE OF RCX_ALLOCATED_LP_VALUE.TIMESTAMP%TYPE;
TYPE t_ralverecord_id IS TABLE OF RCX_ALLOCATED_LP_VALUE.RALVE_RECORD_ID%TYPE;
TYPE t_row IS TABLE OF UROWID;
ln_row t_row :=t_row();
lt_value t_value := t_Value();
lt_kcf t_kcf := t_kcf();
lt_timestamp t_timestamp := t_timestamp();
lt_ralve t_ralverecord_id := t_ralverecord_id();
v_bulk NUMBER := 1000;
val number;
kcf number;
ralve number;
times date;
dml_errors EXCEPTION;
errors NUMBER;
PRAGMA exception_init(dml_errors, -24381);
BEGIN
--setting arguments for the logging record
lr_logging.module := LS_MODULE_NAME;
lr_logging.context := 'INFLOW_ALL_VALUES_PARTS';
lr_logging.logged_by := USER;
lr_logging.parameters := 'Date time started: ' || TO_CHAR(sysdate,'DD/MM/YYYY HH24:MI');
-- log debugs
recon_logging.set_logging_env (TRUE, TRUE);
recon_logging.log_event(lr_logging,'D');
OPEN lc_update;
LOOP
FETCH lc_update BULK COLLECT INTO ln_row,lt_ralve,lt_value,lt_timestamp,lt_kcf LIMIT v_bulk;
FORALL i IN NVL(lt_value.first,1)..NVL(lt_value.last,0) SAVE EXCEPTIONS
UPDATE RCX_ALLOCATED_LP_VALUE
SET VALUE = VALUE * lt_value(i) * lt_kcf(i)
WHERE rowid =ln_row(i);
COMMIT;
lt_value.delete;
lt_timestamp.delete;
lt_ralve.delete;
lt_kcf.delete;
ln_row.delete;
EXIT WHEN lc_update%NOTFOUND;
END LOOP;
CLOSE lc_update;
recon_logging.log_event(lr_logging,'D');
lr_logging.parameters := 'Date time ended: ' || TO_CHAR(sysdate,'DD/MM/YYYY HH24:MI');
recon_logging.log_event(lr_logging,'D');
--to be sure
COMMIT;
EXCEPTION
WHEN dml_errors THEN
recon_logging.set_logging_env(TRUE,TRUE);
lr_logging.module := 'updatevalues';
lr_logging.context := 'exception';
lr_logging.logged_by := USER;
lr_logging.parameters := 'in dml_errors';
recon_logging.log_event(lr_logging);
errors := SQL%BULK_EXCEPTIONS.COUNT;
lr_logging.parameters:=errors;
recon_logging.log_event(lr_logging);
lr_logging.parameters :=('Number of errors is ' || errors);
--DBMS_OUTPUT.PUT_LINE('Number of errors is ' || errors);
FOR i IN 1..sql%BULK_EXCEPTIONS.count LOOP
lr_logging.parameters:= 'index = ' || sql%BULK_EXCEPTIONS(i).error_index || 'error = ' ||Sqlerrm(-sql%BULK_EXCEPTIONS(i).error_code) ;
recon_logging.log_event(lr_logging);
END LOOP;
--recon_logging.set_logging_env(TRUE,TRUE);
--recon_logging.log_event(lr_logging);
commit;
WHEN OTHERS THEN
lr_logging.module := 'updatevalues';
lr_logging.context := 'exception';
lr_logging.logged_by := USER;
recon_logging.set_logging_env(TRUE,TRUE);
lr_logging.parameters := 'in others error=' || SQLERRM;
recon_logging.log_event(lr_logging);
commit;--to look which is truly the last (else only commit after 1000)
--raise_application_error(-20001,'An error was encountered - '||SQLCODE||' -ERROR- '||SQLERRM);
END Update_corr_values;Hi,
No I didn't update a unique constraint.
But I found out that there is a trigger that causes the unique constraint while updating in the table.
Silly mistake.Didn't know there was a trigger there.
Thx anyway.
Greetz -
Uniques constraint violation error while executing statspack.snap
Hi,
I have configured a job to run the statspack snap at a interval of 20 min from 6:00 PM to 3:00 AM . Do perform this task , I have crontab 2 scripts : one to execute the job at 6 PM and another to break the job at 3 AM. My Oracle version is 9.2.0.7 and OS env is AIX 5.3
My execute scripts look like:
sqlplus perfstat/perfstat <<EOF
exec dbms_job.broken(341,FALSE);
exec dbms_job.run(341);
The problem is , that the job work fine for weekdays but on weekend get aborted with the error :
ORA-12012: error on auto execute of job 341
ORA-00001: unique constraint (PERFSTAT.STATS$SQL_SUMMARY_PK) violated
ORA-06512: at "PERFSTAT.STATSPACK", line 1361
ORA-06512: at "PERFSTAT.STATSPACK", line 2471
ORA-06512: at "PERFSTAT.STATSPACK", line 91
ORA-06512: at line 1
After looking on to metalink , I came to know that this is one listed bug 2784796 which was fixed in 10g.
My question is , why there is no issue on weekdays using the same script. There is no activity on the db on weekend and online backup start quite late at night.
Thanks
AnkyThe reasons for hitting this bug are explained in Metalink, "...cursors with same sql text (at least 31 first characters), same hash_value but a different parent cursor...", you can also find the workaround in Note:393300.1.
Enrique -
OWB 10.2.0.4.36: Unique Constraint Violation on WB_RT_SERVICE_QUEUE_TAB.
Hello.
I'm using OWB 10.2.0.4.36. I've recently started to get an error on a mapping that has been scheduled and running successfully for several years now. The details are below. This only occurs on one specific mapping. I've synchronized my metadata in OWB and also redeployed the mapping and the associated source/target objects. Still the issue occurs.
I'm looking for help in troubleshooting the error and preventing it from happening again. I've taken a look at the packages, but they are OWB packages and I'm not really going to touch those for fear of bringing down my entire system.
I haven't really found any suggestions via Google, the forum or Metalink.
Any thoughts?
Thanks.
Dan
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
Session altered.
Role set.
Stage 1: Decoding Parameters
| location_name=ATLAS_STAGING_PROD
| task_type=PLSQL
| task_name=M_BSO_COMPANY_STG_FULL
Stage 2: Opening Task
| l_audit_execution_id=2509772
Stage 3: Overriding Parameters
Stage 4: Executing Task
begin
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-00001: unique constraint (DW_REPOS.SYS_C005805) violated
ORA-06512: at "DW_REPOS.WB_RTI_QUEUES", line 202
ORA-06512: at "DW_REPOS.WB_RTI_SERVICE_EXECUTION", line 500
ORA-06512: at "DW_REPOS.WB_RTI_SERVICE_EXECUTION", line 558
ORA-06512: at "DW_REPOS.WB_RT_EXECUTION_CONTROL", line 13
ORA-06512: at "DW_REPOS.WB_RT_API_EXEC", line 365
ORA-06512: at "DW_REPOS.WB_RT_API_EXEC", line 726
ORA-06512: at line 10
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options.I am also having same problem and my environment is
Environment: Oracle 9.2.0.3, OWB 10g, workflow 2.6.2, sun solaris 2.8 - 64 bits. Does installing/upgrading OWF 2.6.2 to 2.6.3 solve the problem and does it have any ripple effect on the system if you upgrade the OWF from 2.6.2 to 2.6.3? Please help..... -
ORA-00001 unique constraint violation updating row
Hi Folks,
Using oracle application express version 3.1.2.00.02 to update one column in a table ORA-00001: unique constaint (BI_ADS.FCV_UK) violated error is returned. This is strange as the column being updated has no constraint on it.
We have had a trace done on the database action and it is a normal UPDATE statement.
You can run this UPDATE statement directly against the database with no errors.
When using APEX the error is returned.
Some rows update OK and a few rows will not.
There are no sequences involved.
Thanks
BrianIt turns out the form is stripping the time off the date column (constraint column) and this is causing the unique contraint violation. Any one had any dealings with times not being updated with a date column from a form??
Maybe you are looking for
-
Hi my IPad was stolen today from my RV in Mexico. I havent activated ICloud or Find My Ipad. I am trying to report it stolen on line, but have not been able to do much yet. I have emailed to my home in Canada, asking people to look for my serial numb
-
sorry, i cant login in my Macbook pro,, iMessage and FaceTime.., could u please help me to fix it? im international student, so i must use facetime to chat with my family and fds.. please help me.. please help me..
-
hi every body, Pl. Tell me ,how to change the database name so that when i query to the V$DATABASE view it should reflect the new database name .Changing the GLOBAL_NAME does not reflect changes in V$DATABASE view. thanx in advance..
-
Hi all, I have a question on the download settings when downloading an ALV table content (e.g. content of PPT). Sequence: 1. Choose the "Export" button 2. Choose Spreadsheet 3. Choose any format 4. Check on the checkbox "Always Use Selected Format" 5
-
Where are ringtones iPhone 4 ios5
Hello everyone. I'm looking for guidence here in the Apple community. Seems I have an issue with ringtones as part of the update party yesterday. Hardware: iPhone 4 w/ ios5 Macbook pro w/ 10.7.2 iTunes 10.5 Ringtones have bben purchased for apple. Ev