Feigl (AUDI)
Member
Hello there,
I
I
BUG: Procedure - Problem with Trigger
- Thread starter Feigl (AUDI)
- Start date
DoDo
Member³
ORA-02067: transaction or savepoint rollback required
Cause: A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed.
Action: rollback to a previous savepoint or rollback the transaction and resubmit.
--------------
In my experience you should avoid using triggers for updating remote database tables.
Cause: A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed.
Action: rollback to a previous savepoint or rollback the transaction and resubmit.
--------------
In my experience you should avoid using triggers for updating remote database tables.
Feigl (AUDI)
Member
Hi DoDo,
It
It
DoDo
Member³
If you have 10g try with queues, if not (like me) on triggers I fill "interface" table and then I refresh data with JOBS on remote database marking those I refreshed after inserting in remote table in the same transaction. So, if remote database can't connect or something happens, I know what is not applied on remote database.
sukhadukkham
Member³
you may use queues on 9i, too
Similar threads
- Discussion
- Discussion
- Discussion