Question

The trigger below is delaying my insert response. How can I prevent this?

create or replace
TRIGGER GETHTTPONINSERT
BEFORE INSERT ON TABLENAME
FOR EACH ROW 
Declare
  --   
BEGIN
  -- The inserted data is transfered via HTTP to a remote location
END;

EDIT People are telling me to do batch jobs, but I would rather have the data earlier than having 100% consistency. The advantage of the trigger is that it happens as soon as the data arrives, but I can’t afford the insert response delay.

Answer 1

There is a perfect solution for this exact situation called Database Change Notification.

You can think of it almost exactly like an async trigger.

You use the DBMS_Change_Notification package to tell oracle which tables to watch and what to do when a change occurs. You can monitor for DML and DDL, you can have Oracle batch the changes (i.e. wait for 10 changes to occur before firing). It will call a sproc with an object containing all the rowids of the changed rows… you can decide how to handle, including calling HTTP. It will not have to finish for the insert to commit.
Documentation for 10gR2