To fire a trigger

How can I fire a trigger after inserting data with
sqlloader , seems after insert does not work?

RTFM [url
http://oraclesvca2.oracle.com/docs/cd/B10501_01/server
.920/a96652/ch09.htm#1008146]Direct Loads,
Integrity Constraints, and Triggers
Elic,
Telling people to RTFM is not polite. You could, in theory, answer all posts just saying RTFM, but that achieves nothing. Instead it is better to say "Details are here in the manual".
;)

Similar Messages

How to Fire a trigger after an update of a table

Hi
I have a form that has one block and I am having the users
entering some information in it then at end I am comiting the
records. I would like after the records being comitted I want to
fire a trigger to do some other things like populating another
table. Could you please help me on this?
What kind of trigger will I need? where I would I put the
trigger?
Thanks
alpha

Thank you much. Can I ask you another question please.
I have a database trigger that need to be fired only when some
columns on a tabke is being updated so I have the trigger like
this
create or replace trigger FRK_HZ_LOCATIONS_AUR
after update of address1,address2,city,state
,postal_code,county,province,country,attribute20
on hz_locations
for each row
DECLARE
v_cust_account_id hz_cust_acct_sites_all.cust_account_id%type;
v_cust_acct_site_id hz_cust_acct_sites_all.cust_acct_site_id%
type;
v_org_id hz_cust_acct_sites_all.org_id%type;
-- cursor; all sites for this customer address
cursor sc is
select
s.site_use_id site_use_id
,s.attribute15 frk_addr_number
from
ra_site_uses_all s
where s.address_id = v_cust_acct_site_id
and s.site_use_code in ('BILL_TO','SHIP_TO');
rowcnt number;
But the trigger is firing even thought they insert instead of
update. Could you help please
Thanks

How to fire a trigger from java in oracle

Is it possible to fire/ call a trigger from java ? Is there any way ?

Sure.
Simply INSERT/DELETE/UPDATE your rows according to the trigger definition.

Timer fires during trigger processing on web

I was looking for a way to augment the default behaviour
of a hierarchical tree. The trouble is clicking in a tree can fire various combinations of WHEN-MOUSE-CLICK, WHEN-TREE-NODE-SELECTED, WHEN-TREE-NODE-EXPANDED,
WHEN-TREE-NODE-ACTIVATED, WHEN-MOUSE-DOUBLE-CLICKED. I wanted to trigger some action after they had finished firing but as I didn't know which would fire last, where to put the code ?
The solution I found was to start a 1 ms timer in WHEN-MOUSE-CLICK (which always fires first), gather information from the other triggers into a variable, and do my processing in WHEN-TIMER-EXPIRED. This worked fine on client/server but when I deployed it on the web I found the timer expired between WHEN-MOUSE-CLICK and WHEN-TREE-NODE-SELECTED (triggered by a single click).
My understanding of timers is that, however short their duration, they should not expire during trigger processing. Have I got this wrong or is this a bug ?
It seems to work OK with 5 ms but I would like to know what is going on.
(f6i patch 7)

All,
as promised, here's an answer from development. Duncan said it already, but here's the long version
1). Regarding timers in general. 1ms timers fire on the server (effectively,
at the time the timer is created in a trigger, we put a timer macro on the
stack so that that next time we go for input (after we've processed all
of the events we've already gotten at that point), it will act as if the timer
has expired. This, as you know, prevents us from doing round-trips to the
client when people are simply creating a timer to get around some of the
restricted built-in/trigger issues. Any timer of longer than 1ms will get
created on the client and thus cause round-trips. We have no plans to
bump that threshhold up, so people could use 2ms timers if they wanted...
2). Regarding timers expiring during trigger processing. It is true in both
client/server and web that we will not expire a timer while a trigger is
firing. However, the order in which the user will see events (and thus
which triggers will fire in) can vary. In the example that was given,
the user (double)clicks on a node in the tree on the client. The first
mouse click causes a message/event to be sent immediately to the
server, which ends up causing the when-mouse-clicked trigger to fire.
As soon as that message is sent, the server starts processing that
trigger. In the meantime, the client may decide that it needs to send
other messages (such as when-node-selected, etc.). However, until
the server sends a return-message to the client asking for more input,
this won't get sent. Now, the server fires the when-mouse-click trigger,
and as part of it a timer gets created. There are two possible scenarios
here.
In the first scenario, the timer is 1ms, and thus is handled on the
server. Thus, when the trigger ends, the server sees if there is any more
input to be processed, and sees that the timer has expired (because, as
I explained above, this gets put directly onto the macro stack). Thus, the
timer expired trigger fires. After that trigger fires, the server sees that it
has no more input waiting, and sends a message to the client telling it to
send more input. At that point, the client can send whatever other events
it has queued up (such as the when-node-selected) and we carry on.
In the second scenario, the timer is more than 1ms long. In this case, when
the trigger says to create a timer, the server queues up a message to send
to the client telling it to create a timer. When the rest of the trigger is complete
and the server sees that it has no more events to process, it sends this timer
creation message to the client at the same time it asks the client to give it
more events. The client sends the when-node-selected event, the server
processes it, and eventually asks the client for more input. By then, the
timer has expired and then the timer message gets sent to the server.
In neither of these cases does the timer trigger fire in the middle of
another trigger that is already firing, it is simply that the separate triggers
might fire in a different order because of the order that the underlying
events are processed. In client/server, the process is effectively the same
as the 2nd scenario above, because the timer is handled by the toolkit, just
like the other events, and thus the message for the timer expiring will get
sent to Forms after any of the events related to the mouse click. But again,
the rule about timers firing during trigger processing is not violated, it is just
that there is a break between triggers that can allow a 1ms timer to fire
'sooner' on the web than in client/server.
Fran

Fire trigger once when inserting 50 rows

Is there a way to fire a trigger once after inserting several rows in a table within a single transaction.
I dont want the overhead of firing the trigger for each row.

Here is something dirty, but works!
Works with regular inserts.
SQL> select * from emp1;
no rows selected
SQL> create or replace package emp1_pkg as
2 v_emp_inserts number := 0;
3 end emp1_pkg;
4 /
Package created.
SQL> create or replace trigger emp1_tgr
2 before insert
3 on emp1
4 begin
5       emp1_pkg.v_emp_inserts := emp1_pkg.v_emp_inserts + 1;
6       if emp1_pkg.v_emp_inserts > 5 then
7          dbms_output.put_line ('Trigger fired');
8          emp1_pkg.v_emp_inserts := 0;
9       end if;
10 end;
11 /
Trigger created.
SQL> set serveroutput on
SQL> insert into emp1 values ('a', 1);
1 row created.
SQL> insert into emp1 values ('b', 2);
1 row created.
SQL> insert into emp1 values ('c', 3);
1 row created.
SQL> insert into emp1 values ('d', 4);
1 row created.
SQL> insert into emp1 values ('e', 5);
1 row created.
SQL> insert into emp1 values ('f', 6);
Trigger fired
1 row created.
SQL> insert into emp1 values ('g', 7);
1 row created.
SQL> select * from emp1;
ENAME            ENUM
a                   1
b                   2
c                   3
d                   4
e                   5
f                   6
g                   7
7 rows selected.

Return Key doesn4t make my defined KEY-ENTER trigger to fire.

I4ve found that the trigger that fires when I press Return is KEY-NEXT-ITEM,but this doesn4t resolve my problem,because the tab key also fires this trigger.
I want to navigate within textitems with the tab key and that when I press return key make an action on the values entered in the items.
mila, PJR

You have to perform key mapping to get the Key-Enter trigger to work.
Open your forms90\fmrweb.res file in a text editor. Find the line:
10 : 0 : "Return" : 27 : "Return"
Change it to:
10 : 0 : "Return" : 75 : "Return"
Save the file and run the form again. The key-enter trigger should then fire when you press the Return key, but not when you press the Tab key.

Do not fire trigger for specific updates

I have a table that has a timestamp filed and varchar2 field that keeps track of the last update.
I have written a trigger that executes after update for each row and inserts the current user and sysdate into this fields. However most of the updates to this table are done to a single column and when this is the case I do not want the trigger to fire. If the update is done to any other column yes, but to this specific column then no.
Is there a way to implement this?
Thank you for your help.

One obvious way is to use the 'FOR UPDATE OF' clause, which allows you to list the columns that are supposed to fire the trigger.
There is, as far as I know, no 'FOR UPDATE OF ALL EXCEPT ...' capability.
More details in the SQL Reference manual.

How to handle Database's trigger

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.

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.

Help with trigger

Dear All,
I have a trigger that works fine when the value is updated by a user but when the value is updated by another trigger it does not seem to work.
When i log in and update the value in sqlplus it works fine but when I update a value in another table which then calls a trigger which then updates that value in the main table the trigger does not fire.
This is the scenario. We have a table called payments. When we run a process it sets some values in this payment table.
When this value is set in the payments table it fires a trigger which then updates the invoice table (paid_date) based on some value in the payments table.
Now when this value in the invoices table is set by the trigger it is meant to call another trigger which should recognise this new value but this does not hapen.
however if i go in manually and update the invoice table, the trigger fires.
Any help will be appreciated.
Below is the trigger that does not seem to fire.
I have also included the trigger which sets this value
create or replace
TRIGGER INVOICE_PAID before
UPDATE OF "PAID_DATE" ON "INVOICES" FOR EACH ROW
DECLARE
-- check if the invoice.mco_transfer_status has been updated to R
-- if it has then insert records into the relevant tables
-- Start the Insert based on the update of invoices.mco_transfer_status
fa_cnt PLS_INTEGER;
ecode VARCHAR2(100);
thisproc CONSTANT VARCHAR2(80) := 'trap_errmesg for mco_transfer_status';
v_value VARCHAR2(150);
BEGIN
-- do updates based on update of invoices.transfer_status column
IF :NEW.PAID_DATE IS NOT NULL AND :OLD.PAID_DATE IS NULL
THEN
:NEW.MCO_TRANSFER_STATUS := 'R';
:NEW.TRANSFER_STATUS:='R';
:NEW.RECONCILED_STATUS:='R';
INSERT INTO EMCO_INVOICE_STAGE (emco_document_number,invoice_id,raised_date,paid_date,pnr_reference,booking_date,
gross,currency,forename,surname)
SELECT :NEW.EMCO_DOCUMENT_NUMBER,:NEW.INVOICE_ID,:NEW.RAISED_DATE,:NEW.PAID_DATE,BK.PNR_REFERENCE,BK.BOOKING_DATE,:NEW.GROSS,
:NEW.CURRENCY,PX.FORENAME,PX.SURNAME
FROM BOOKINGS BK, PAX PX
WHERE BK.BOOKING_ID=:NEW.BOOKING_ID
AND PX.BOOKING_ID=:NEW.BOOKING_ID AND
PX.PAX_SEQ=(SELECT MIN(px2.pax_seq) FROM PAX px2 WHERE booking_id=:NEW.BOOKING_ID AND px2.status <>'X' AND px2.pax_type='A' );
-- Insert into PAYMENTS_STAGE table
INSERT INTO PAYMENTS_STAGE (EMCO_DOCUMENT_NUMBER, PAYMENT_ID, INVOICE_ID, PAYMENT_DATE,PAYMENT_TYPE,AMOUNT,
CURRENCY,CARD_NUMBER,TRANSACTIONID)
SELECT :NEW.EMCO_DOCUMENT_NUMBER,PAYMENT_ID,INVOICE_ID,PAYMENT_DATE,PAYMENT_TYPE,AMOUNT,CURRENCY,CC.CARD_NUMBER,TRANSACTIONID
FROM PAYMENTS PA, CREDIT_CARDS CC
WHERE PA.INVOICE_ID=:NEW.INVOICE_ID
AND CC.CARD_ID = PA.CARD_ID;
:NEW.MCO_TRANSFER_STATUS:='C';
SELECT COUNT(*) INTO fa_cnt FROM INVOICE_DETAILS WHERE
invoice_id=:NEW.INVOICE_ID AND CHARGE_TYPE='FA';
IF fa_cnt > 0
THEN :NEW.TICKETING_STATUS:='R';
ELSE
:NEW.TICKETING_STATUS:='N';
:NEW.EXCHANGED_DATE := :NEW.PAID_DATE;
END IF;
END IF;
EXCEPTION
WHEN OTHERS THEN
ecode := SQLCODE|| ' '||SQLERRM ;
dbms_output.put_line(thisproc || ' - ' || ecode);
v_value := thisproc || ' - ' || ecode;
INSERT INTO DOCUMENT_STATUS_STAGE (EMCO_DOCUMENT_NUMBER, STATUS,STATUS_DATE)
VALUES (:NEW.EMCO_DOCUMENT_NUMBER,v_value,SYSDATE);
:NEW.MCO_TRANSFER_STATUS := 'F';
END INVOICE_PAID;
TRIGGER "CAM_OWNER"."CHECK_INVOICE_PAID_IN_FULL" AFTER
UPDATE OF "PAYMENT_STATUS" ON "CAM_OWNER"."PAYMENTS"
DECLARE
-- check if all the payments for that invoice have been received (completed)
-- if they are complete then sum all the payments for that invoice and compare to gross value on invoices
v_invoice_amount NUMBER;
v_gross_amount NUMBER;
thisproc CONSTANT VARCHAR2(80) := 'trap_errmesg for mco_transfer_status';
v_value VARCHAR2(150);
BEGIN
-- Changed as requested by nicola on 12/09/05 IF :NEW.PAYMENT_COMPLETE is not null
--IF :NEW.PAYMENT_STATUS='C' AND :NEW.PAYMENT_STATUS <> :OLD.PAYMENT_STATUS
--THEN
CHECK_INVOICE_PAID_IN_FULL_PRO;
--END IF;
END CHECK_INVOICE_PAID_IN_FULL;
and this is the procedure that is called
PROCEDURE "CHECK_INVOICE_PAID_IN_FULL_PRO" IS
-- check if all the payments for that invoice have been received (completed)
-- if they are complete then sum all the payments for that invoice and compare to gross value on invoices
v_invoice_amount NUMBER(20);
v_gross_amount NUMBER(20);
thisproc CONSTANT VARCHAR2(80) := 'trap_errmesg for mco_transfer_status';
v_value VARCHAR2(150);
BEGIN
-- We will sum all the payments for that invoice that have a value in payment_complete
--select sum(amount) into v_invoice_amount from payments where payment_complete is not null and invoice_id=:NEW.INVOICE_ID;
FOR x IN (SELECT invoice_id FROM PAYMENTS_TEMP) LOOP
SELECT NVL(SUM(amount),0) INTO v_invoice_amount FROM PAYMENTS
WHERE payment_status ='C' AND invoice_id=X.INVOICE_ID;
SELECT NVL(gross,0) INTO v_gross_amount FROM INVOICES WHERE
invoice_id =X.INVOICE_ID;
-- We will also get the gross amount for the invoice to compare to the sum of the payments
IF v_invoice_amount = v_gross_amount
THEN
UPDATE INVOICES SET paid_date=SYSDATE
WHERE invoice_id=X.INVOICE_ID;
END IF;
END LOOP;
END CHECK_INVOICE_PAID_IN_FULL_PRO;

The following demonstration is a direct response to your original question, in case you want to stick with that method of scheduling your index rebuilds through a trigger. In order to do ddl like alter index you will need to use dynamic sql like execute immediate. Since you can't rebuild the index before the insert or update has been committed, you will need to use dbms_job.submit to schedule the rebuild. In the following example, the index rebuild will be done as soon as the insert or update has been committed.
scott@ORA92> CREATE TABLE cc_contenidos (cvalor CLOB)
2 /
Table created.
scott@ORA92> CREATE INDEX cont ON cc_contenidos (cvalor) INDEXTYPE IS ctxsys.context
2 /
Index created.
scott@ORA92> SELECT last_ddl_time FROM user_objects WHERE object_name = 'CONT'
2 /
LAST_DDL_TIME
24-JAN-2005 21:10:13
scott@ORA92> CREATE OR REPLACE PROCEDURE alter_index_cont
2 AS
3 BEGIN
4    EXECUTE IMMEDIATE 'ALTER INDEX cont REBUILD ONLINE PARAMETERS (''sync memory 45M'')';
5 END;
6 /
Procedure created.
scott@ORA92> SHOW ERRORS
No errors.
scott@ORA92> CREATE OR REPLACE TRIGGER actualiza
2    AFTER DELETE OR INSERT OR UPDATE on cc_contenidos
3 DECLARE
4    v_job NUMBER;
5 BEGIN
6    DBMS_JOB.SUBMIT (v_job, 'alter_index_cont;', SYSDATE);
7 END actualiza;
8 /
Trigger created.
scott@ORA92> SHOW ERRORS
No errors.
scott@ORA92> INSERT INTO cc_contenidos (cvalor) VALUES ('test 1')
2 /
1 row created.
scott@ORA92> INSERT INTO cc_contenidos (cvalor) VALUES ('test 2')
2 /
1 row created.
scott@ORA92> COMMIT
2 /
Commit complete.
scott@ORA92> EXECUTE DBMS_LOCK.SLEEP (15)
PL/SQL procedure successfully completed.
scott@ORA92> SELECT last_ddl_time FROM user_objects WHERE object_name = 'CONT'
2 /
LAST_DDL_TIME
24-JAN-2005 21:10:17
scott@ORA92> SELECT * FROM cc_contenidos WHERE CONTAINS (cvalor, 'test') > 0
2 /
CVALOR
test 2
test 1
scott@ORA92>

Get Current SQL in Before delete trigger

Hi,
I have created a before delete trigger to track which records are deleted from a table I need to know what statements fires the trigger. can someone please describe how I can retrieve the current SQL.
using sys_context('userenv','CURRENT_SQL') returns null for CURRENT SQL
Note:
For me the easier is to enable auditing and audit delete on the table however at the moment I cant get a downtime from the business to bounce the database to enable auditing.
CREATE OR REPLACE TRIGGER before_delete BEFORE DELETE
ON AUDIT_TEST_TAB
FOR EACH ROW
DECLARE
v_username varchar2(50);
v_stmt varchar2(255);
v_client_info varchar2(200);
v_os_user varchar2(50);
v_machine varchar2(50);
v_program varchar2(50);
v_module varchar2(50);
v_auth_type varchar2(200);
v_ip_addr varchar2(200);
v_sql_statement VARCHAR2(4000);
BEGIN
SELECT sys_context ('USERENV', 'CURRENT_SQL')
INTO v_sql_statement
FROM dual;
-----------insert into logging table statment ----
end;

A few comments.
Lets assume you run a delete statement that deletes 550 rows from your table. If your trigger is working then the very same statement would be stored 550 times. I think an BEFORE or better an AFTER delete STATEMENT level trigger would be the better choice. Why AFTER? Because if the delete operation fails, for example because of existing child records, then everything is rolled back anyway to the implicit savepoint just before the delete.
So to store the SQL statement the correct trigger would be an AFTER STATEMENT DELETE trigger.
Now what to store: You want the sql statement. You could try to find the cursor/currently running SQL. It might be tricky to separate that from the SQLs that you run to find this out.
It could even be possible to simply save all commands that are in your PGA/Cached cursor area. First find out yur session, then store the SQL_text (first 60 chars) for all the cursors in this session by using v$open_cursor or the first 1000 chars by using v$sql.
Here are a few views that might be helpful. v$session , v$open_cursor, v$sql, v$sqltext, v$sql_bind_data, v$sql_bind_capture, dba_hist_sqltext

Instead Of Trigger And multiple Updable fields

Hi all,
I have an application based on a view (Customers,Products,..) above which an INSTEAD OF TRIGGER handles the updates done by end users.
A field,Updated_Date stores the date when the tuple was last modified.To better capture information and enhance the updates processes,
I want to store the exact date when a given field is modified.Only that field not the whole tuple.
Solution
Instead of 1 field,updated_date, i'd rather create 1 update_date_x for each column that might likely be modified.
I.e: updated_date_phone,updated_date_fax,...
Question
Is it possible to combine all those fields within a single Trigger firing with respect to the field being altered ?
Rather than creating a trigger for each updatable column.
Thks for any advise/point to a useful doc.
Lamine

Check if the following helps.
http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96590/adg13trg.htm#376
From above link
Detecting the DML Operation That Fired a Trigger (INSERTING, UPDATING, and DELETING Predicates)
If more than one type of DML operation can fire a trigger (for example, ON INSERT OR DELETE OR UPDATE OF Emp_tab), the trigger body can use the conditional predicates INSERTING, DELETING, and UPDATING to check which type of statement fire the trigger.
Within the code of the trigger body, you can execute blocks of code depending on the kind of DML operation fired the trigger:
IF INSERTING THEN ... END IF;
IF UPDATING THEN ... END IF;
The first condition evaluates to TRUE only if the statement that fired the trigger is an INSERT statement; the second condition evaluates to TRUE only if the statement that fired the trigger is an UPDATE statement.
In an UPDATE trigger, a column name can be specified with an UPDATING conditional predicate to determine if the named column is being updated. For example, assume a trigger is defined as the following:
CREATE OR REPLACE TRIGGER ...
... UPDATE OF Sal, Comm ON Emp_tab ...
BEGIN
... IF UPDATING ('SAL') THEN ... END IF;
END;
The code in the THEN clause runs only if the triggering UPDATE statement updates the SAL column. This way, the trigger can minimize its overhead when the column of interest is not being changed.

Import of .bacpac fails on view with instead of delete trigger

I'm using Azure Premium SQL.
When I export the database using the portal and blob storage and then immediately try to import it as a test to a new database (also using the portal) I get the error below.
Looking at the restored database, many of the views are not there (including the one listed) although that may be because it failed on this view during the restore.
The trigger seems to be working just fine in the original database. It just won't restore from the bacpac.
BTW, I notice in the original database before backup, the trigger says "DELETE
FROM alndata.AptChangeLog", not "DELETE alndata.AptChangeLog"
Thanks.
Bryan
Error encountered during the service operation.
Could not import package.
Error SQL72014: .Net SqlClient Data Provider: Msg 8197, Level 16, State 4, Procedure AdminChangeLogAptNameDelete, Line 7 The object 'AlnData.AdminChangeLogAptName' does not exist or is invalid for this operation.
Error SQL72045: Script execution error. The executed script:
CREATE TRIGGER [AlnData].[AdminChangeLogAptNameDelete]
ON [AlnData].[AdminChangeLogAptName]
INSTEAD OF DELETE
AS BEGIN
SET NOCOUNT ON;
DELETE alndata.AptChangeLog
WHERE aptchangelog_id IN (SELECT aptchangelog_id FROM deleted);
END

Hello,
Sorry for delay.
I had found a feedback about trigger issue when restore SQL Database from a BACPAC file. Microsoft said the fixed will be available in the next major release of DacFx.
Feedback:
SQL Azure fires a trigger when restoring from bacpac
You can refer to the workarounds in the feedback. For example, if there is small amount of triggers on the database, you can try to remove the triggers and then recreate when restore from bacpac file.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

ApEx 4.1.1: update record in a view with 'instead of update' trigger

I created a form against a view. The view is complex enough which prevents direct updates. To incorporate the update logic I created an 'instead of update' trigger on the view. When I open up the form, do changes, and click 'Apply Changes' button I am getting the following exception
ORA-02014: cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.
I understand that the standard 'Automatic Row Processing' process is trying to lock the record before updating using a cursor like
select *
from my_view
for update
and fails. Is it possible to bypass this locking while using the standard APEX processes?
I think I can create a custom PL/SQL process which would execute the UPDATE statement (at least, it works in SQL*Plus), but I would like to know if I can use a standard ApEx functionality for this.

Hello,
Sorry for delay.
I had found a feedback about trigger issue when restore SQL Database from a BACPAC file. Microsoft said the fixed will be available in the next major release of DacFx.
Feedback:
SQL Azure fires a trigger when restoring from bacpac
You can refer to the workarounds in the feedback. For example, if there is small amount of triggers on the database, you can try to remove the triggers and then recreate when restore from bacpac file.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

How to call or not call a Trigger in same table based on condition?

Hi
How to call or not call a Trigger in below situations..
If a table contains a record of same value i.e,
[i[u]]ID
1
1
3
In above ID 1 is repeated for two times.
In this situations i don't want to call a trigger..
But, the value ID is for 3, now i want to fire a trigger.
Based on this i want to delete in another table.
How can I check it?
Thanks

Thanks for ur reply..
The below is my scnario..
I am having two table
employee
Id empcol
101 111
101 222
102 444
Department
id deptcol
101 457
101 678
102 543
The above is my table structure no one column is PK, so i m not able create FK.
When I am deleting from employee where id =101 and empcol=111,
the above record is deleted.
At present I am using After Update Trigger..
So trigger is called and delete the id 101 in Department table.
In my scenario i can't delete a record in Department table
bcoz i am having id morethan 101 in employee table.
If employee table contains one ID like 102 the Trigger should works.
How can I check the condition After delete on employee table it contains morethan same employee id?
The below is my Trigger..
CREATE OR REPLACE TRIGGER CALL_TRIGGER
AFTER DELETE ON Employee
FOR EACH ROW
DECLARE
count_id pls_integer;
BEGIN
SELECT COUNT(*) INTO count_id from Employee WHERE ID <>:new.ID;
IF( count_id >1) THEN
DELETE FROM Depratment where ID=:old.ID;
END IF;
END;
I am geting an error ORA-04091 table is mutuating, trigger cannot seen it.
I had tried with package and package body also.. But no luck.
Thanks

INSERTstatement is not working if there is a before insert trigger

INSERTstatement is not working if there is a before insert trigger on that table. That trigger contains an insert to another table which having the main table reference.
Let us say, for example there a table named 'EMP_DEPT' and there is a before insert trigger on this table.
In this trigger inserting a record in to another table named 'AUDIT_EMP' and in this table using EMP_Dept primary key as foreign key.
Table EMP_DEPT is having the below columns:
EMP_DEPT_SYS_ID
EMP_DEPT_NO
DEP_NAME etc..
Table AUDIT_EMP is having the below columns:
AUDIT_EMP_SYS_ID
EMP_DEPT_SYS_ID
AUDIT_NO etc..
the code in the trigger is
INSERT INTO audit_emp
(audit_emp_sys_id, emp_dept_sys_id, audit_no
VALUES (audit_emp.NEXTVAL, :new EMP_DEPT_SYS_ID, '1101'
Now when you execute the insert query like:
INSERT INTO emp_dept
(emp_dept_sys_id, emp_dept_no, dep_name
VALUES (EMP_DEPT.nextval, 1001, 'Dep-1'
It is giving the error saying 'Integrity constraint error, parent key not found' from the trigger.
But, when you modify the above insert query like the below then it is working.
INSERT INTO emp_dept
(emp_dept_sys_id, emp_dept_no, dep_name
SELECT EMP_DEPT.nextval, 1001, 'Dep-1'
FROM DUAL;
I am using Oracle 10g.
Why the insert into values is not working. Is there any commit transaction sequence change? Any idea please?
Edited by: user6475632 on Sep 16, 2009 7:08 AM

Obviously the code you posted can not work.
You are inserting the detail record (the audit record) before the master record, where it should have been after. IMO, you should fire the trigger AFTER INSERT for each row.
If that still doesn't work, you need to change the foreign key constraint into a deferred constraint, which is evaluated at commit, instead of immediately. The SQL reference manual has further info on this.
'Oracle 10g' is considered a marketing label here, not a -4 digit- version.
Sybrand Bakker
Senior Oracle DBA

To fire a trigger

Similar Messages

Maybe you are looking for