This content has been marked as final. Show 3 replies
Can you provide anymore details on what is happening here?
What object is the trigger on?
What does it do?
What are you doing on the local database that causes the remote operation?
The trigger is on the table
the trigger is inserting data into the table
we aare inserting /updating into a table via dblink which internally calls the trigger which is creating problem.
the trigger on the other db is trying to put the data into AQ.
We had succesfull run of the job in between the failure instances also.
we had rolled back the script being executed to a previous version which runs on daily basis it ran successfully.it internally reduced the number of records being proccessed on the single run.
bbut today another batch job which does the similar thing caused the same error.
can u provide some advice to resolve this thing.
This sounds like a bit of a minefield and it is quite difficult to say what might be causing this - has this process been around for a while or have you implemented it and started seeing these issues straight away?
Can I see exactly what the trigger is doing?