Constraint violation on update through trigger

I have a table on which there are 2 before update triggers (one for update or delete and another for insert and update).
One of these tiggers is updating another table. (A history table)
Sometimes when I try to update a row in this table, this trigger tries to update the history table and fails with a constraint violation ORA error. However second time when I try to fire the same update sql, it goes fine.
What can be the possible causes? How do I rectify the same?
Thanks in advance

Hi,
I get the PK violation error. As mentioned earlier we try to update history table which has PK as (DEAL_NUM, VERSION). Please note that we are changing the version in the trigger. However exactly same update statement goes fine in second run. (The update is fired from code of the product I work on)
The trigger code is something like this:
CREATE OR REPLACE TRIGGER TEST1_HIST before update or delete on
TEST1 FOR EACH ROW
BEGIN
IF updating AND :new.version = 0 THEN
:new.version := :old.version;
ELSE
:new.version := :old.version + 1;
insert into TEST1_HIST(
DEAL_NUM
,VERSION)
VALUES
( :old.DEAL_NUM
,:old.VERSION
END IF;
END;
Thank you

Similar Messages

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

When the update statement will check the constraint violation ?

Hello all,
i am working on data masking of production data using oracle Translate function.i have created a function otis_mask using translate function to mask sensitive values .For this i am tesitng on a small table. i have created a table with single primary key column SSN.
sql>desc SSN_MASK
Name Null? Type
SSN NOT NULL NUMBER(10)
1) i have inserted the value 9949577766. if resulted mask value exist in table it should throw the constraint violation error.But it is not throwing any error.rows are properly updating .
Eg:-
Table contains below values.
PA_DATA_SUB @qdsrih30 >select *from SSN_MASK;
SSN
7727399911
9949577766
9989477700
UPDATE SSN_MASK SET SSN=otis_mask(SSN);
if above update statement process 7727399911 first then resulted mask value is 9989477700.This value is already in the table.
if the update statement process 9949577766 first then resulted mask value is 7727399911.This value is already in the table.
in any of the above scenario update statement should have to throw constraint violation error. But its not happening. rows are properly updating . when the update statement checking the constraint violation ? after processing all the rows or processing of each row ?
Please help me in understandding the update statement processing ?
Thanks,
Venkat Vadlamudi.

1)created a function as below.
CREATE OR REPLACE Function otis_mask(incol varchar2) return varchar2 is
random_str varchar2(20);
begin
select (translate(incol,'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890','qwertyuiopasdfghjklzxcvbnmQWERTYUIOPASDFGHJKLZXCVBNM0842319576')) INTO random_str FROM DUAL;
return random_str;
end;
2. create a table ssn_mask.
create table ssn_mask(ssn number(10) primary key);
3) inserted 3 rows as below.
insert into ssn_mask values(9949577766);
insert into ssn_mask values(7727399911);
insert into ssn_mask values(9989477700);
4)UPDATE SSN_MASK SET SSN=otis_mask(SSN);
5) Table contains below rows.
Sql >select *from SSN_MASK;
SSN
9949577766
7727399911
9989477700.
6)UPDATE SSN_MASK SET SSN=otis_mask(SSN);
If the above statement process first row 9949577766,then otis_mask function will return 7727399911 and update statement will update the value of 9949577766 to 7727399911 .At this case 7727399911 is already in the table.So update statement should have to throw primary key constraint violation error.
If the above statement process second row 7727399911 first ,then otis_mask function will return 9989477700.and update statement will update the value of 7727399911 to 9989477700.At this case 9989477700 is already in the table.So update statement should have to throw primary key constraint violation error.
But its not throwing any integrity constraint violation error.
i just want to know when update statement will check the constraint ?
is update statement will first process all records and kepp in handy the new values then update the table with new values (or) process the first row and update the new value with old value then process second row and update with new value so on ?
Thanks,
Venkat Vadlamudi.

PL/SQL Trying to update a table through trigger on the same table

Hi everyone my name is Edwin and I'm new to this forum. I hope I can learn a lot from this community and over time contribute to it.
The problem I'm facing at the moment is a tough one. I need to update a table (table a) with a value called block_id. This block_id is generated by a procedure I have written myself, the end result is stored in another table (table b). This block_id needs to be generated after certain rows of table a get updated with a trans_id. The trans_id is all the same for these rows in table a, but the generated block_id isn't. In my code I use an after update on collumn a of table a trigger. So if the the collumn gets updated the trigger fires. The trigger calls the procedure that generates the block_id and the procedure generates table b with all the block_id's. But then I want to update the rows in table a with the generated block_id in table b. The problem is that this self-deadlocks.
You might think that this would call a recursive trigger, but I have written code in the trigger that checks if the block_id isn't allready filled in on table a.
Also I really need all the values wich get updated (table a), so I believe a before update is also out of the question.
And the first update of table a is done through an erp-packet and I can't get at that code, otherwise I would just have run my code from there.
Message was edited by:
user625855

CREATE OR REPLACE TRIGGER block_id_trigger AFTER UPDATE ON unload_details_tab
DECLARE
current_transport_id NUMBER;
check_value NUMBER;
check_block_id NUMBER;
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
current_transport_id := get_curent_trans_id; --function that gets the current transport_id
check_value := check_site_and_directive(current_transport_id); --function checks if this transport_id should have a block_id
check_block_id := check_for_block_id(current_transport_id); --function checks if there isn't allready a block_id set.
IF check_value = 1 AND check_block_id = 0 THEN
create_blok_id_table(current_transport_id); --this procedure creates the blok_id in temptable
UPDATE unload_details_tab a SET a.block_id = (SELECT DISTINCT b.blok_id FROM temptable b WHERE b.mark = a.mark_1) WHERE a.transport_id = current_transport_id; --this statement should update the table back, if I leave it out everything works fine, but when I leave it I get the self-deadlock error.
ELSE
null;
END IF;
END block_id_trigger;
Ok, I cleaned the code somewhat.
user625855

Update pwdChangedTime via ldapmodify causes "Constraint violation"

Hi,
we're migrating an application from IBM products (WebSphere+Tivoli DS) to Sun produdcts (SJSAS 9.0+SJSDS 6.0). I need to be able to change an entry's pwdChangedTime using the ldapmodify command.
Running the following command
ldapmodify -D "cn=Directory Manager" -v -f /tmp/change_pwdChangedTime.txt
with the folloing /tmp/change_pwdChangedTime.txt file
dn: cn=abc,ou=people,o=aaa,c=bbb
changetype: modify
replace: pwdChangedTime
pwdChangedTime: 20070806082500Z
gives me the following output
ldap_init( localhost, 389 )
replace pwdChangedTime:
20070806082500Z
modifying entry cn=abc,ou=people,o=aaa,c=bbb
ldap_modify: Constraint violation
ldap_modify: additional info: Constraint violation in modifications
In Tivoli Directory Server I was able to use the command above using the "-k" option to be able to change the value of operational attributes like pwdChangedTime. Is there anywthing similar in SJSDS 6?
Is there any other way to update this attribute manually when required but still have the server updating it when the password is changed by the user?
Message was edited by:
mcari

We are trying to constrain applications from meddling with operational attributes due to the possibility of surprising behavior of the DSA as a result of an unanticipated value.
In a lab environment, I would think it would be acceptable to remove the "read-only" restriction. Edit <instance_root>/config/schema/00ds6pwp.ldif and remove the constraint.
We can consider adding a programmatic mechanism (e.g., an LDAP extended operation) in a future release to manage these operational attributes for testing and other administrative purposes. Could you let us know what other attributes you modify and to what ends?

True about updates through a view

hi frds
i just need the right answer for the choices mentioned below with explanation
plz help me
What is true about updates through a view?
A. You cannot update a view with group functions.
B. When you update a view group functions are automatically computed.
C. When you update a view only the constraints on the underlying table will be in effect.
D. When you update a view the constraints on the views always override the constraints on the underlying tables.

And a very tricky only it is.
Peter, you are correct that view constraints are not enforced in the sense of PKs and FKS, but there are two other view constraints that are enforced.
SQL> CREATE TABLE t AS
2 SELECT rownum id, object_name
3 FROM all_objects
4 WHERE rownum < 11;
Table created.
SQL> CREATE VIEW t_read AS
2 SELECT * FROM t
3 WITH READ ONLY;
View created.
SQL> CREATE VIEW t_check AS
2 SELECT * FROM t
3 WHERE mod(id,2) = 0
4 WITH CHECK OPTION;
View created.
SQL> CREATE VIEW t_nocheck AS
2 SELECT * FROM t
3 WHERE MOD(id, 2) = 0;
View created.
SQL> INSERT INTO t_read VALUES (100, 'READ ONLY');
INSERT INTO t_read VALUES (100, 'READ ONLY')
ERROR at line 1:
ORA-01733: virtual column not allowed here
SQL> INSERT INTO t_check VALUES (100, 'EVEN ID');
1 row created.
SQL> INSERT INTO t_check VALUES (101, 'ODD ID');
INSERT INTO t_check VALUES (101, 'ODD ID')
ERROR at line 1:
ORA-01402: view WITH CHECK OPTION where-clause violation
SQL> INSERT INTO t_nocheck VALUES(100, 'EVEN ID');
1 row created.
SQL> INSERT INTO t_nocheck VALUES(101, 'ODD ID');
1 row created.
SQL> UPDATE t_check SET id = 201
2 WHERE id = 2;
UPDATE t_check SET id = 201
ERROR at line 1:
ORA-01402: view WITH CHECK OPTION where-clause violation
SQL> UPDATE t_nocheck SET id = 201
2 WHERE id = 2;
1 row updated.The WITH READ ONLY constraint bars all changes to the view. The WITH CHECK OPTION stops any changes that would make the record invisible to the view. It is essentially a CHECK constraint on the view.
John

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 AM

When 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:
aschilling

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:
aschilling

How to debug and find the exact constraint violation error

{122712 14:22:36:ErrorCode -1 with ErrorMessage as ORA-00001: unique constraint (OPS$CMS.PK_TB_ML_EXER_UPLOAD) violated has occured for [SSO16063259009], [CMSCOST_USER] pk_xop_subsales.pr_process_exer }
{PROCEDURE pr_process_exer(
p_voucher_num           tb_xop_order_manager_t.voucher_num%TYPE,
p_status_type           tb_xop_order_manager_t.status_type%type,
p_dest                    tb_xop_order_manager_t.dest%type,
p_reference_key            tb_xop_order_manager_t.reference_key%type,
p_seq_num                tb_xop_order_manager_t.seq_num%type,
p_return_code            tb_xop_order_manager_t.return_code%type,
p_reason_desc           tb_xop_order_manager_t.reason_desc%type,
p_activity_qty            tb_xop_order_manager_t.activity_qty%type,
p_leaves_qty            tb_xop_order_manager_t.leaves_qty%type,
p_exec_price            tb_xop_order_manager_t.exec_price%type,
p_current_status        tb_xop_order_manager_t.current_status%type,
p_err_cur          OUT ref_cursor)
IS
CURSOR get_order_dtls(v_voucher_num tb_xop_order_manager_t.voucher_num%type)
IS
SELECT *
FROM   tb_xop_order_manager_t
WHERE voucher_num = v_voucher_num;
CURSOR get_mail_cd(v_opt_num OPTIONEE.opt_num%TYPE) IS
      SELECT mail_cd, sp_mail_cd
      FROM XOP_OPTIONEE
      WHERE opt_num = v_opt_num;
cursor get_opt_dtls(v_opt_num OPTIONEE.opt_num%TYPE) IS
select
SUBSTR(trim(O.name_first) || ' ' || trim(O.name_mi) || ' ' ||
          trim(O.name_last), 1, 35) p_name,
        SUBSTR(O.address1, 1, 35) opt_addr1,
          SUBSTR(O.address2, 1, 35) opt_addr2,
          SUBSTR(O.address3, 1, 35) opt_addr3,
          SUBSTR(O.address4, 1, 35) opt_addr4,
          SUBSTR(O.address5, 1, 35) opt_addr5,
          SUBSTR(O.address6, 1, 35) opt_addr6,
        SUBSTR(trim(O.city) || ' ' || trim(O.state) || ' ' ||
        trim(O.zip) || ' ' || trim(O.country), 1, 35) city_state_zip_country,
        trim(O.city) city,
        trim(O.state) state,
        trim(O.zip) zip,
        trim(O.country) country
from optionee o
where o.opt_num = v_opt_num;
--CQ:PCTUP00210726- Added wire instructions audit for deleted wire info.
CURSOR c_wire_instruction (
      in_wire_seq_no           TB_XOP_WIRE_INSTRUCTIONS.wire_seq_no%TYPE ) IS
      SELECT ml_brok_acct_num,
             ssn,
             plan_num,
             instr_type,
             aba_routing_num,
             swift_routing_code,
             bank_name,
             bank_acct_num,
             name_on_account,
             bank_addr_1,
             bank_addr_2,
             bank_addr_3,
             city,
             state,
             country,
             zip,
             bank_ident_num,
             addtl_info
        FROM TB_XOP_WIRE_INSTRUCTIONS
       WHERE wire_seq_no = in_wire_seq_no
       UNION
       SELECT ml_brok_acct_num,
             ssn,
             plan_num,
             instr_type,
             aba_routing_num,
             swift_routing_code,
             bank_name,
             bank_acct_num,
             name_on_account,
             bank_addr_1,
             bank_addr_2,
             bank_addr_3,
             city,
             state,
             country,
             zip,
             bank_ident_num,
             addtl_info
        FROM TB_XOP_WIRE_INSTRUCTIONS_AUDIT
       WHERE wire_seq_no = in_wire_seq_no;
CURSOR c_order_qty IS
SELECT order_qty
FROM tb_xop_order_manager
WHERE voucher_num = p_voucher_num;
v_order_qty     tb_xop_order_manager.order_qty%TYPE;
v_wire_instruction             c_wire_instruction%ROWTYPE;
v_order_dtls      get_order_dtls%rowtype;
v_opt_dtls        get_opt_dtls%rowtype;
v_settle_dt       tb_ml_exer_upload.settle_dt%type;
v_cusip_num       corp.cusip_num%type;
v_err_cd          number(12):=0;
v_err_msg         varchar2(4000);
v_compy_nme       tb_fc_Compy.compy_nme%type;
v_ml_sec_num      tb_fc_compy.ml_sec_num%type;
v_mail_cd         xop_optionee.mail_cd%type;
v_count1            PLS_INTEGER := 0;
v_sum_activity_qty tb_xop_order_manager_t.activity_qty%TYPE;
v_transact_no       PLS_INTEGER;
v_ivr_plan_num      tb_fc_compy.ivr_plan_num%TYPE;
wait_for_more       EXCEPTION;
exceeds_order_qty   EXCEPTION;
--Added for CQ# PCTUP00481233
v_sub_totfee number;
v_sub_fixedfee1 number;
v_sub_fixedfee2 number;
v_sub_fixedfee3 number;
v_sub_secfee number;
v_sub_feenum number;
--Added for CQ# PCTUP00481233
v_fixedfee1 tb_xop_order_manager_t.fixed_fee1%TYPE; --SPIF# 43161- variable to hold fixed fee1
BEGIN
    OPEN c_order_qty;
    FETCH c_order_qty INTO v_order_qty;
    CLOSE c_order_qty;
    dbms.output.put_line('completed1');
    IF v_order_qty <> p_activity_qty THEN
      dbms.output.put_line('completed2');
        IF p_status_type = 'EO' AND v_order_qty < p_activity_qty THEN
            RAISE exceeds_order_qty;
              dbms.output.put_line('completed3');
        ELSIF p_status_type = 'EO' AND v_order_qty > p_activity_qty THEN
            -- Partial Execution
            INSERT INTO tb_xop_hold_multi_orders
                ( voucher_num
                , reference_key
                , seq_num
                , return_code
                , reason_desc
                , status_type
                , activity_qty
                , leaves_qty
                , exec_price
                , current_status
                , waiting
                ,activ_dt )
            VALUES
                ( p_voucher_num
                , p_reference_key
                , p_seq_num
                , p_return_code
                , p_reason_desc
                , p_status_type
                , p_activity_qty
                , p_leaves_qty
                , p_exec_price
                , p_current_status
                , 'Y'
                ,SYSTIMESTAMP );
                  dbms.output.put_line('completed4');
        ELSE
            IF p_status_type = 'BE' THEN
                SELECT COUNT(1) INTO v_count1
                FROM tb_xop_hold_multi_orders
                WHERE voucher_num = p_voucher_num;
                  dbms.output.put_line('completed5');
                IF v_count1 > 0 THEN
                    INSERT INTO tb_xop_hold_multi_orders
                        ( voucher_num
                        , reference_key
                        , seq_num
                        , return_code
                        , reason_desc
                        , status_type
                        , activity_qty
                        , leaves_qty
                        , exec_price
                        , current_status
                        , waiting
                        ,activ_dt)
                    VALUES
                        ( p_voucher_num
                        , p_reference_key
                        , p_seq_num
                        , p_return_code
                        , p_reason_desc
                        , p_status_type
                        , (-1) * p_activity_qty
                        , p_leaves_qty
                        , p_exec_price
                        , p_current_status
                        , 'Y'
                        ,SYSTIMESTAMP );
                    UPDATE tb_xop_hold_multi_orders
                    SET waiting = 'Y'
                    WHERE voucher_num = p_voucher_num;
                      dbms.output.put_line('completed6');
                END IF;
            END IF;
        END IF;
          dbms.output.put_line('completed7');
        SELECT SUM(NVL(activity_qty,0)) INTO v_sum_activity_qty
        FROM tb_xop_hold_multi_orders
        WHERE waiting = 'Y'
        AND voucher_num = p_voucher_num;
        IF v_sum_activity_qty > 0 THEN
            IF v_sum_activity_qty <> v_order_qty THEN
                RAISE wait_for_more;
            ELSE
                -- final order in the partial execution; complete the process
                UPDATE tb_xop_hold_multi_orders
                SET waiting = 'N'
                    , process_dt = SYSDATE
                WHERE voucher_num = p_voucher_num;
            END IF;
        END IF;
    END IF;
    UPDATE tb_xop_order_manager_t
    SET activ_dt = TO_CHAR( SYSDATE, 'YYYY-MM-DD HH24:MI:SS' ) || '.000'
        , dest = p_dest
        , reference_key = p_reference_key
        , seq_num = p_seq_num
        , return_code = p_return_code
        , reason_desc = p_reason_desc
        , status_type = p_status_type
        , activity_qty = v_order_qty --p_activity_qty
        , leaves_qty = 0 --p_leaves_qty
        , exec_price = p_exec_price
    WHERE voucher_num = p_voucher_num;
    dbms.output.put_line('completed8');
     * SPIF# 43161- Update of current status to PO moved at the end, same as how PROD works.
IF (p_status_type = 'EO') THEN
BEGIN
    select cusip_num
      into   v_cusip_num
      from   corp;
EXCEPTION
      WHEN NO_DATA_FOUND THEN
          SELECT cusip_num
            INTO v_cusip_num
            FROM tb_xop_espp_compy
           WHERE compy_acronym = replace(replace(user,'CMS'),'_USER');
      WHEN OTHERS THEN
          NULL;
END;
   select compy_nme,ml_sec_num, ivr_plan_num
   into   v_compy_nme,v_ml_sec_num, v_ivr_plan_num
   from   tb_fc_compy
   where compy_acronym = replace(replace(user,'CMS'),'_USER')
   UNION ALL
   select compy_nme, je_ml_security_number, ivr_plan_num
   from tb_xop_espp_compy
   where compy_acronym = replace(replace(user,'CMS'),'_USER');
--   where ivr_plan_num = replace(substr(p_voucher_num,1,7),'SSO','XOP');
open get_order_dtls(p_voucher_num);
FETCH get_order_dtls INTO v_order_dtls;
   v_settle_dt := fn_xop_bankopen_bizday(TRUNC(v_order_dtls.exer_date + 1));
   v_settle_dt := fn_xop_bankopen_bizday(TRUNC(v_settle_dt + 1));
   v_settle_dt := fn_xop_bankopen_bizday(TRUNC(v_settle_dt + 1));
   FOR c_mail_cd IN get_mail_cd(v_order_dtls.opt_num)
   LOOP
     v_mail_cd := c_mail_cd.mail_cd;
     -- Do we need to get sp_mail_cd and overlay with the sp_mail_cd in order_manager_t???
   END LOOP;
   OPEN get_opt_dtls(v_order_dtls.opt_num);
   FETCH get_opt_dtls INTO v_opt_dtls;
   CLOSE get_opt_dtls;
v_fixedfee1 := nvl(v_order_dtls.fixed_fee1, 0);
   * SPIF# 43161- atleast one handling fee per day of transaction
v_fixedfee1 := pk_xop_enh_exerupdate.chrg_tranxfixed_fee(v_fixedfee1,
                                                           v_order_dtls.symbol,
                                                           v_order_dtls.corp_acronym,
                                                           v_order_dtls.opt_num);
--Insert into tb_ml_exer_upload
--Added for CQ# PCTUP00481233
   Pk_Xop_Transactmodel.GET_FEE(v_order_dtls.GROUP_ID,v_order_dtls.SVC_ID,'SQ',v_order_dtls.opts_exer,
                                round(v_order_dtls.exec_price, 4),v_sub_totfee,v_sub_fixedfee2,v_sub_fixedfee1,
                                v_sub_fixedfee3,v_sub_secfee,v_sub_feenum,lpad(v_order_dtls.ssn,9,0));
   v_order_dtls.sec_fee:=v_sub_secfee;
   UPDATE tb_xop_order_manager_t
    SET sec_fee=v_sub_secfee
    WHERE voucher_num = p_voucher_num;
    dbms.output.put_line('completed8');
--- End CQ # PCTUP00481233
INSERT INTO tb_ml_exer_upload
                        (exer_num,exer_seq,
                         exer_dt, written_flag, backout_flag, output_line,
                         je_flag, opts_exer,
                         tot_tax,shrs_sold,comm_value,tot_fee,
                         mkt_prc,exer_type, soc_sec,
                         name_first, name_mi,
                         name_last,check_addr_1,check_addr_2,check_addr_3,
                         check_addr_4,check_addr_5,city,state,zip,country,
                         city_state_zip_country,
                         p_name,opt_addr1,opt_addr2,opt_addr3,opt_addr4,
                         opt_addr5,opt_addr6,
                         settle_dt,send_to_citibank_flag,
                         dom_chek_distr,foreign_currency_code,
                         distribution_method,wire_seq_no,
                         cusip_num, ml_retail_account,multi_curr_handling_fee,
                         ml_sec_num, corp_name,upd_optionee_addr,
                         outbound_flag, -- make it N
                         corp_symbol,taxwire_approve, -- make it not applicaplabe
                         exersource,
                         mail_cd, sp_mail_cd,
                         backup_withholding,
                         user_id,
                         acct_num_othr)
   VALUES(v_order_dtls.exer_num,0,v_order_dtls.exer_date,'N','N',NULL,
-- PG 12/12/05 Changed to populate the je_flag based on dom_chek_distr         'D',
-- PG 12/16/05 JE should not be generated for international checks.. So 'Y' always
          'Y', --je_flag
          v_order_dtls.opts_exer,0,--total tax will be 0.
          v_order_dtls.opts_exer, --shrs_sold,
          v_order_dtls.comm_value,
          --SPIF# 43161- replaced nvl(v_order_dtls.fixed_fee1, 0) with v_fixedfee1
          v_fixedfee1 + nvl(v_order_dtls.fixed_fee3,0) + nvl(v_order_dtls.sec_fee,0), --v_order_dtls.fees_amt,
          round(v_order_dtls.exec_price, 4),v_order_dtls.exer_type,
          LPAD(v_order_dtls.ssn,9,'0'), --v_order_dtls.ssn, Modified by Suresh on 02/08/07 for SPIF # 37210
          v_order_dtls.name_first,v_order_dtls.name_mi,v_order_dtls.name_last,
          v_order_dtls.check_addr_1,v_order_dtls.check_addr_2,v_order_dtls.check_addr_3,
          v_order_dtls.check_addr_4,v_order_dtls.check_addr_5,nvl(v_order_dtls.city,v_opt_dtls.city),
          nvl(v_order_dtls.state,v_opt_dtls.state),nvl(v_order_dtls.zip,v_opt_dtls.zip),
          nvl(v_order_dtls.country,v_opt_dtls.country),
          SUBSTR(nvl(v_order_dtls.city||v_order_dtls.state||v_order_dtls.zip||v_order_dtls.country,
              v_opt_dtls.city_state_zip_country),1,34), -- COLUMN LENGTH MAX IS 35
          v_opt_dtls.p_name,v_opt_dtls.opt_addr1,v_opt_dtls.opt_addr2,v_opt_dtls.opt_addr3,
          v_opt_dtls.opt_addr4,v_opt_dtls.opt_addr5,v_opt_dtls.opt_addr6,
          v_settle_dt,decode(v_order_dtls.distribution_method,'W','Y','D','Y','C','Y','D'),
          v_order_dtls.dom_chek_distr,v_order_dtls.foreign_currency_code,
          v_order_dtls.distribution_method,v_order_dtls.wire_seq_no,
          v_cusip_num,v_order_dtls.acct_num,v_order_dtls.multi_curr_handling_fee,
--          nvl(fn_get_sec_num(replace(substr(p_voucher_num,1,7),'SSO','XOP'),v_order_dtls.symbol),v_ml_sec_num),
          nvl(fn_get_sec_num(v_ivr_plan_num, v_order_dtls.symbol),v_ml_sec_num),
          v_compy_nme,v_order_dtls.upd_optionee_addr,
          'N', --'N' is for outbound flag.
          v_order_dtls.symbol,'D', --'D' for taxwires disabled
          'S', -- 'S' for source being subsequent sale.
          v_mail_cd, --need to get mail_Cd??
          v_order_dtls.sp_mail_cd,v_order_dtls.backup_withholding,
          user,v_order_dtls.acct_num_othr);
IF (NVL(v_order_dtls.wire_seq_no,0) > 0) THEN
   OPEN c_wire_instruction(v_order_dtls.wire_seq_no);
   FETCH c_wire_instruction INTO v_wire_instruction;
   CLOSE c_wire_instruction;
INSERT INTO TB_XOP_TRANSACT_WIRE_INSTR
                       (user_id, exer_num, wire_seq_no, ml_brok_acct_num, ssn,
                        plan_num, instr_type, aba_routing_num,
                        swift_routing_code, bank_name, bank_acct_num,
                        name_on_account, bank_addr_1, bank_addr_2, bank_addr_3,
                        city, state, country, zip, bank_ident_num, addtl_info )
                    VALUES
                       (USER,v_order_dtls.exer_num, v_order_dtls.wire_seq_no,
                        v_wire_instruction.ml_brok_acct_num, v_wire_instruction.ssn,
                        v_wire_instruction.plan_num, v_wire_instruction.instr_type, v_wire_instruction.aba_routing_num,
                        v_wire_instruction.swift_routing_code, v_wire_instruction.bank_name, v_wire_instruction.bank_acct_num,
                        v_wire_instruction.name_on_account, v_wire_instruction.bank_addr_1, v_wire_instruction.bank_addr_2,
                        v_wire_instruction.bank_addr_3, v_wire_instruction.city, v_wire_instruction.state, v_wire_instruction.country, v_wire_instruction.zip,
                         v_wire_instruction.bank_ident_num, v_wire_instruction.addtl_info);
        dbms.output.put_line('completed10');
END IF;
/* PG 01/05/06 Call the check conversion only for international checks and wires */
IF v_order_dtls.dom_chek_distr = 'N' AND v_order_dtls.distribution_method IN ('W', 'D', 'C') THEN
    /* PG 12/20/05 To process subsequent sales with wire or foreign currency distribution */
     v_transact_no := 88;
     pk_xop_citibank_forex.pr_cashconversion_ins_request( v_order_dtls.acct_num
                                                          , LPAD(v_order_dtls.ssn,9,'0') --v_order_dtls.ssn, Modified by Suresh on 02/15/07 for SPIF # 37210
                                                          , v_order_dtls.distribution_method
                                                          , v_order_dtls.foreign_currency_code
                                                          , v_order_dtls.wire_seq_no
                                                          , ROUND((v_order_dtls.opts_exer * round(v_order_dtls.exec_price, 4)),2)
                                                            - ROUND(v_order_dtls.comm_value,2)
                                                            - ROUND(nvl(v_order_dtls.fixed_fee1,0) + nvl(v_order_dtls.fixed_fee3,0) + nvl(v_order_dtls.sec_fee,0),2)
                                                            - nvl(v_order_dtls.multi_curr_handling_fee,0)
                                                            - nvl(v_order_dtls.backup_withholding,0) -- net proceeds
                                                          , v_order_dtls.multi_curr_handling_fee --handling fee
                --Modified by Bhaskar/Suresh on 03/02/2006    --, v_order_dtls.login_name
                                                          , CASE v_order_dtls.login_name WHEN 'CLIENT/' THEN v_order_dtls.login_name||'SSO' ELSE v_order_dtls.login_name||'/SSO' END
                                                          , v_transact_no -- transact_no as place holder for exer_type 88
                                                          , v_order_dtls.check_addr_1
                                                          , v_order_dtls.check_addr_2
                                                          , v_order_dtls.check_addr_3
                                                          , v_order_dtls.check_addr_4
                                                          , v_order_dtls.upd_optionee_addr
                                                          , v_order_dtls.city
                                                          , v_order_dtls.state
                                                          , v_order_dtls.zip
                                                          , v_order_dtls.country
                                                          , v_order_dtls.login_ipaddress
                                                          , v_order_dtls.fcnum
                                                          , v_order_dtls.opt_num
                                                          , v_settle_dt,
                                                          p_exer_num => v_order_dtls.exer_num
END IF;
COMMIT;
close get_order_dtls;
END IF;
* SPIF# 43161- Update to current status into PO is moved to this part, same as PROD.
UPDATE tb_xop_order_manager_t
SET exec_dttime = decode(p_status_type,'EO',to_char(sysdate,'DD-MON-YYYY HH24:mi:ss'),null)
     , exer_date = TRUNC(SYSDATE)
     , cancel_dttime = decode(p_status_type,'CX',to_char(sysdate,'DD-MON-YYYY HH24:mi:ss'),'UR',to_char(sysdate,'DD-MON-YYYY HH24:mi:ss'),null)
     , current_status = 'PO'
     , sum_status = decode(p_status_type,'EO','X','C')
     , sum_stat_dttime = SYSDATE
WHERE voucher_num = p_voucher_num;
      v_err_cd := sqlcode;
      v_err_msg := sqlerrm;
      open p_err_cur for select v_err_cd err_code,v_err_msg err_msg from dual;
EXCEPTION
        dbms.output.put_line('completed200');
/* PG 02/10 handled 'partial fill order' exception */
when wait_for_more then
      v_err_cd := 0;
      v_err_msg := 'ORA-0000: normal, successful completion';
      pr_xop_log_errors('Partially filled; Waiting for more - Activity qty:' || to_char(v_sum_activity_qty)|| ' pk_xop_subsales.pr_process_exer');
      open p_err_cur for select v_err_cd err_code,v_err_msg err_msg from dual;
when exceeds_order_qty then
      v_err_cd := sqlcode;
      v_err_msg := sqlerrm;
      open p_err_cur for select v_err_cd err_code,v_err_msg err_msg from dual;
      pr_xop_log_errors('Activity quantity exceeded the Order_qty - Activity qty: ' || to_char(p_activity_qty) || ' pk_xop_subsales.pr_process_exer');
when others then
      v_err_cd := sqlcode;
      v_err_msg := sqlerrm;
      open p_err_cur for select v_err_cd err_code,v_err_msg err_msg from dual;
      pr_xop_log_errors('ErrorCode '||SQLCODE||' with ErrorMessage as '||SQLERRM||' has occured for '||user||'pk_xop_subsales.pr_process_exer');
            dbms.output.put_line('completed125');
END pr_process_exer;
Hi friends, any1 help me out how to define the ref-cursor in declaration section, and how to find at what situation the constraint error occurred..

956684 wrote:
Hi,.
Friends plz help me out ..how to debug and find the exact position of the constraint violation..thank you for the help..There isn't a way to trace it unless you have caught the exception raised.
As a way to start the debug, you will have to monitor
1. All DML's against the Table on which you have constraint. More specifically, the DML's that act on the column you have constraint on.
2. Use Exception Handling, to log the Error and the data that causes the constraint to fail.
3. Do not forget to monitor the Triggers, if they are used, that would write some data into the column you have constraint on.
Or
Another way to trace is:
select *
from user_source
where lower(text) like '%your_table_name%';
order by type, name, line;Look at the lines, exclude that are in Declaration or in SELECT statements and target the DML's.
Looking at the un-formatted code you posted, this statement looks like a culprit.
INSERT INTO tb_ml_exer_upload
(exer_num,exer_seq,
exer_dt, written_flag, backout_flag, output_line,
je_flag, opts_exer,
tot_tax,shrs_sold,comm_value,tot_fee,
mkt_prc,exer_type, soc_sec,
name_first, name_mi,
name_last,check_addr_1,check_addr_2,check_addr_3,
check_addr_4,check_addr_5,city,state,zip,country,
city_state_zip_country,
p_name,opt_addr1,opt_addr2,opt_addr3,opt_addr4,
opt_addr5,opt_addr6,
settle_dt,send_to_citibank_flag,
dom_chek_distr,foreign_currency_code,
distribution_method,wire_seq_no,
cusip_num, ml_retail_account,multi_curr_handling_fee,
ml_sec_num, corp_name,upd_optionee_addr,
outbound_flag, -- make it N
corp_symbol,taxwire_approve, -- make it not applicaplabe
exersource,
mail_cd, sp_mail_cd,
backup_withholding,
user_id,
acct_num_othr)
VALUES(v_order_dtls.exer_num,0,v_order_dtls.exer_date,'N','N',NULL,
-- PG 12/12/05 Changed to populate the je_flag based on dom_chek_distr 'D',
-- PG 12/16/05 JE should not be generated for international checks.. So 'Y' always
'Y', --je_flag
v_order_dtls.opts_exer,0,--total tax will be 0.
v_order_dtls.opts_exer, --shrs_sold,
v_order_dtls.comm_value,
--SPIF# 43161- replaced nvl(v_order_dtls.fixed_fee1, 0) with v_fixedfee1
v_fixedfee1 + nvl(v_order_dtls.fixed_fee3,0) + nvl(v_order_dtls.sec_fee,0), --v_order_dtls.fees_amt,
round(v_order_dtls.exec_price, 4),v_order_dtls.exer_type,
LPAD(v_order_dtls.ssn,9,'0'), --v_order_dtls.ssn, Modified by Suresh on 02/08/07 for SPIF # 37210
v_order_dtls.name_first,v_order_dtls.name_mi,v_order_dtls.name_last,
v_order_dtls.check_addr_1,v_order_dtls.check_addr_2,v_order_dtls.check_addr_3,
v_order_dtls.check_addr_4,v_order_dtls.check_addr_5,nvl(v_order_dtls.city,v_opt_dtls.city),
nvl(v_order_dtls.state,v_opt_dtls.state),nvl(v_order_dtls.zip,v_opt_dtls.zip),
nvl(v_order_dtls.country,v_opt_dtls.country),
SUBSTR(nvl(v_order_dtls.city||v_order_dtls.state||v_order_dtls.zip||v_order_dtls.country,
v_opt_dtls.city_state_zip_country),1,34), -- COLUMN LENGTH MAX IS 35
v_opt_dtls.p_name,v_opt_dtls.opt_addr1,v_opt_dtls.opt_addr2,v_opt_dtls.opt_addr3,
v_opt_dtls.opt_addr4,v_opt_dtls.opt_addr5,v_opt_dtls.opt_addr6,
v_settle_dt,decode(v_order_dtls.distribution_method,'W','Y','D','Y','C','Y','D'),
v_order_dtls.dom_chek_distr,v_order_dtls.foreign_currency_code,
v_order_dtls.distribution_method,v_order_dtls.wire_seq_no,
v_cusip_num,v_order_dtls.acct_num,v_order_dtls.multi_curr_handling_fee,
-- nvl(fn_get_sec_num(replace(substr(p_voucher_num,1,7),'SSO','XOP'),v_order_dtls.symbol),v_ml_sec_num),
nvl(fn_get_sec_num(v_ivr_plan_num, v_order_dtls.symbol),v_ml_sec_num),
v_compy_nme,v_order_dtls.upd_optionee_addr,
'N', --'N' is for outbound flag.
v_order_dtls.symbol,'D', --'D' for taxwires disabled
'S', -- 'S' for source being subsequent sale.
v_mail_cd, --need to get mail_Cd??
v_order_dtls.sp_mail_cd,v_order_dtls.backup_withholding,
user,v_order_dtls.acct_num_othr);What is the Table structure of tb_ml_exer_upload and what columns do you have constraints on?
Which column of the table tb_ml_exer_upload is your Primary Key (because constraint name mentions pk_tb_ml_exer_upload)?
Edited by: Purvesh K on Jan 4, 2013 12:57 PM

DML ERROR LOGGING - how to log 1 constraint violation on record

Hi there
We are using DML error logging to log records which violate constraints into an error table.
The problem is when a record violates > 1 constraint it logs the record but details only 1 constraint violation - is there a way to get it to record all constraint violations on an individual record.
Many Thanks

In the Netherlands several years ago a framework called CDM RuleFrame was introduced that did just this. Their main thought was that it is desirable to collect all error messages from one transaction and display them all at the end of the transaction.
[url http://www.dulcian.com/papers/ODTUG/2001/BR%20Symposium%202001/Boyd_BR.htm]Here is an article that explains the concept.
In short: it involves coding every single business rule as a database trigger using transaction management of CDM RuleFrame.
I would not recommend it however, because I think [url http://rwijk.blogspot.com/2007/09/database-triggers-are-evil.html]database triggers are evil. However, it may appeal to first time users of an application.
Hope this helps.
Regards,
Rob.
Message was edited by:
Rob van Wijk
But if cannot be "turned on" by some switch: you have to design your system this way. So the short answer to your question is: no, it is not possible.

JBO-28030 possible constraints violation for PS_TXN

Hi guys, any updates on this old thread from 2004?
Constraints violation for PS_TXN
Sometimes, i also receive this error Running WLS Cluster with 2 nodes:
oracle.jbo.PCollException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-28030
     at oracle.jbo.PCollException.throwException(PCollException.java:36)
     at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1901)
     at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:564)
     at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:688)
     at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:647)
     at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:465)
     at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
     at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:267)
     at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5975)
     at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5835)
     at oracle.adf.model.bc4j.DCJboDataControl.createSnapshot(DCJboDataControl.java:3143)
     at oracle.adf.model.dcframe.DataControlFrameImpl.createSnapshot(DataControlFrameImpl.java:879)
     at oracle.adf.model.BindingContext.createSnapshot(BindingContext.java:699)
     at oracle.adf.model.BindingContext.writeObject(BindingContext.java:666)
     at sun.reflect.GeneratedMethodAccessor726.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at weblogic.servlet.internal.session.ReplicatedSessionChange.writeExternal(ReplicatedSessionChange.java:153)
     at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1429)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1398)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:618)
     at weblogic.rjvm.MsgAbbrevOutputStream.writeObjectWL(MsgAbbrevOutputStream.java:609)
     at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:38)
     at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:88)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:221)
     at weblogic.cluster.replication.ReplicationManager_1035_WLStub.update(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor675.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.cluster.replication.SecureReplicationInvocationHandler$ReplicationServicesInvocationAction.run(SecureReplicationInvocationHandler.java:194)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.cluster.replication.SecureReplicationInvocationHandler.invoke(SecureReplicationInvocationHandler.java:164)
     at $Proxy135.update(Unknown Source)
     at weblogic.cluster.replication.ReplicationManager.sendUpdateRequestToSecondary(ReplicationManager.java:740)
     at weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:662)
     at weblogic.servlet.internal.session.ReplicatedSessionData.syncSession(ReplicatedSessionData.java:639)
     at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:85)
     at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2860)
     at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2835)
     at weblogic.servlet.internal.ServletResponseImpl$1.run(ServletResponseImpl.java:1485)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1479)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1462)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (ADF_FMWK.PS_TXPLG_PK) violated
I'm using several passivation tables for different Application modules . PS_TXPLG acually have a PS_TXN table structure and PS_TXPLG_PK is equivalent to PS_TXN_PK .
Regards,
Krasimir

Hi guys, any updates on this old thread from 2004?
Constraints violation for PS_TXN
Sometimes, i also receive this error Running WLS Cluster with 2 nodes:
oracle.jbo.PCollException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-28030
     at oracle.jbo.PCollException.throwException(PCollException.java:36)
     at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1901)
     at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:564)
     at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:688)
     at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:647)
     at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:465)
     at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
     at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:267)
     at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5975)
     at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5835)
     at oracle.adf.model.bc4j.DCJboDataControl.createSnapshot(DCJboDataControl.java:3143)
     at oracle.adf.model.dcframe.DataControlFrameImpl.createSnapshot(DataControlFrameImpl.java:879)
     at oracle.adf.model.BindingContext.createSnapshot(BindingContext.java:699)
     at oracle.adf.model.BindingContext.writeObject(BindingContext.java:666)
     at sun.reflect.GeneratedMethodAccessor726.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at weblogic.servlet.internal.session.ReplicatedSessionChange.writeExternal(ReplicatedSessionChange.java:153)
     at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1429)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1398)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:618)
     at weblogic.rjvm.MsgAbbrevOutputStream.writeObjectWL(MsgAbbrevOutputStream.java:609)
     at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:38)
     at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:88)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:221)
     at weblogic.cluster.replication.ReplicationManager_1035_WLStub.update(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor675.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.cluster.replication.SecureReplicationInvocationHandler$ReplicationServicesInvocationAction.run(SecureReplicationInvocationHandler.java:194)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.cluster.replication.SecureReplicationInvocationHandler.invoke(SecureReplicationInvocationHandler.java:164)
     at $Proxy135.update(Unknown Source)
     at weblogic.cluster.replication.ReplicationManager.sendUpdateRequestToSecondary(ReplicationManager.java:740)
     at weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:662)
     at weblogic.servlet.internal.session.ReplicatedSessionData.syncSession(ReplicatedSessionData.java:639)
     at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:85)
     at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2860)
     at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2835)
     at weblogic.servlet.internal.ServletResponseImpl$1.run(ServletResponseImpl.java:1485)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1479)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1462)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (ADF_FMWK.PS_TXPLG_PK) violated
I'm using several passivation tables for different Application modules . PS_TXPLG acually have a PS_TXN table structure and PS_TXPLG_PK is equivalent to PS_TXN_PK .
Regards,
Krasimir

Unique constraint violation

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

Constraint violation: complex PK

hi,
I'm working with a schema where the composite PK of one table A contains one-column FKs to two other tables B and C. I have a TopLink mapping set up with an object for each of these tables, and the add..() methods as recommended in the guides. I have had no problems with other schemata (PK containing just one FK), but in this case, the attempt to insert a row in table A is preceded by a mysterious attempt to insert a row into table B leading to a constraint violation because the row already exists in B.
I apologise for being skimpy on the details, but I'd like to know if there's something I need to be doing, and if someone else has seen this problem.
regards and TIA
george

Three possibilities that I can think of, with these limited details, are:
1) you have a multiple table mapping between table A and B for the new object that you are inserting. Solution do not do this if partial data is pre-existing.
or
2) While creating the object within the UnitOfWork the B object is being registered without a primary key and TopLink is detecting the B object as new and attempts to insert it as well. To solve make sure B is read through the UnitOfWork before assigning A to it.
or
3) You are not using a UnitOfWork and simply executing an Insert query on A which may be cascading and attempting to insert B. Solution set cascade level on the query to shallow.
In order to provide more help I suggest contacting support with the descriptors for these 2 objects and a TopLink log of the insert.
--Gordon

How to show the message text for constraint violations

Hi all,
In a batch procedure a primary key is violated (ORA-00001). For the primary key, a message is recorded in the TAPI and the message table.
How to show the enduser a proper message text instead of the ORA-00001.
We are using Designer 6 with Headstart 2.1.2.
Thanks in advance,
Joep

Joep,
If you try to insert the record by calling the ins procedure of the Table API, you will see that it will result in an ORA-20998 message, which means that the error message details reside in the CG$ERRORS plsql message table. These messages can be extracted e.g. with the messages.sql script, shipped with headstart.
If you do not want to rewrite your direct DML (insert into [table name] ...) in the complexer calls to the TAPI services, you might want to user VAPI's for it. In fact, this is one of the major advantages of using VAPI's.
The CDM guidelines volume, chapter 6 states that:
<I>The front end no longer needs to trap declarative constraint
errors (Primary Key, Unique Key, Not Null and Check
Constraint violations) and replace them with a user-friendly
error. The View API issues DML statements through the TAPI
and the TAPI traps all declarative constraint errors, and puts
user-friendly message on the stack, in the preferred language of
the user! Fore more information, see the section, Completeness
of Rule Violations Reported in Front End, in this chapter.</I>
So the only thing you need to do is generate VAPI's, and trap the ORA-20998 message (qms$errors.qms$exception) in an exception handler, where you retrieve the user friendly messages from the message stack!!
Regards, Marc

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

Constraint violation on update through trigger

Similar Messages

Maybe you are looking for