How to handle Database's trigger

Question

Greetings,
i have an application on JDeveloper 11.1.2.4.0. At some point the user add new customer and its been saved to the database.
Because the application may be used in more than 1 shop, i have created a 2nd database, only for biography uses and history,
so it can be view by all shops. What i did is, when a new record is inserted into application's biography table, i also have a trigger
that after the row is inserted, i also insert the new row into my 2nd database. In both databases a primary key exists to avoid duplicated id's.
I was hoping instead of handling duplicated records on trigger, the database will handle it (if duplicated records exists, just dont save it at all),
but my problem now is, its throw me a proper exception
ORA-00001: unique constraint (PERSONAL_RECORD.BIOGR_PK) violated ORA-06512: at "ELAB.SAVE_BIOGR", line 11 ORA-04088: error during execution of trigger 'ELAB.SAVE_BIOGR' ORA-06512: at line 1
AND it does not save the biogr on the 1st database either. I do not understand what the trigger have to do with the first database since its after insert row method and not before.
It should insert the record into the database, then fire the trigger, throw an exception and dont save the record in 2nd database. But instead the record its been saved nowhere..
The case is: user fields some text boxes for a new customer, i check if the id is already exists in the 2nd database, and i notify the user that this new customer already exists in
the personal record database (2nd database, 1 common database for all shops), and i ask the user if he/she wants to synchronize or use the current fields. If synchronize, i take the record
from the 2nd database and insert them into the 1st. If not, i insert them into the 1st database, and thats when the trigger should handle the duplicate row exception, not my application.
Is there a way i can temporally turn off database trigger from my adf application or i can handle the exception BUT the record be save on the 1st database? because if the exception its been
thrown, the new record its gone.
thanks in advance for any help.

Answer 1

True, since i can't handle the trigger procedure, i add an exception inside of it. So it will do something when the exception occurs BUT it will save the customer
in 1st database. Here is my trigger code:
create or replace TRIGGER SAVE_BIOGR
AFTER INSERT
   ON ELAB.BIOGR
   FOR EACH ROW
DECLARE
   v_username varchar2(10);
BEGIN
   SELECT user INTO v_username
   FROM dual;
   INSERT INTO PERSONAL_RECORD.BIOGR
   ( ID,
     NAME,
     SNAME,
     USERNAME )
   VALUES
   ( :NEW.ID_PATIENTS,
     :NEW.NAME,
     :NEW.SNAME,
     v_username);
    EXCEPTION
    WHEN DUP_VAL_ON_INDEX THEN
    UPDATE PERSONAL_RECORD.BIOGR SET ERROR = 'ALREADY EXIST';
END;
I add update on exception because leaving it blank or with comment in THEN section it gave me an error i dont know why. So i just
include a dump update procedure.