Re: golden_date_erroir

Posted by ErmanArslansOracleBlog on
URL: http://erman-arslan-s-oracle-forum.114.s1.nabble.com/golden-date-erroir-tp8140p8159.html

Okay. So the row to be deleted is not present in the target.
I don't know your environment. Is there anything that may cause this result?

For example : you have app1 and db1, and you have app2 and db2
suppose you have a bidirectional GG configuration between db1 <-> db2
So now suppose app2 delete a record in db2 and App1 deletes the same record in db1
Just after that, GG extracts from db1 and replicates to db2 and tries to do the same delete in db2.. Ofcourse it can not do that.. Because that record in db2 was already deleted by the relevant application (app2)

In such environments, we use the REPERROR parameter to control how Replicat responds to errors..

Please speak with the person who designed this GG configuration.
Please check how this row was deleted from the target..

Once you have the necessary information, update me..

There are also some specific cases like the following ..

A very specific case -> Replicat Abends with "OGG-01154 SQL error 1403 mapping" (Doc ID 1329189.1)