Active-Active replication

Question

Hi , I'm implementing Active -active replication between two oracle databases, please find below my replicat setup,
REPLICAT REP_A
USERID ggadmin, PASSWORD ggadmin
DISCARDFILE E:\ggs\dirrpt\conf_dsc.rpt, append
ASSUMETARGETDEFS
DDL INCLUDE ALL
DDLERROR DEFAULT IGNORE RETRYOP
--HANDLECOLLISIONS
APPLYNOOPUPDATES
GETAPPLOPS
IGNOREREPLICATES
ALLOWDUPTARGETMAP
MAP MY_USER.EMPLOYEE, TARGET MY_USER.EMPLOYEE, &
REPERROR (22000, DISCARD), &
SQLEXEC ( ID checkemployee, ON UPDATE, &
QUERY "select count(*) empduplicate from MY_USER.EMPLOYEE where employee_id = :p1 and &
employee_timestamp > :p2 ", &
PARAMS (p1 = employee_id, p2 = employee_timestamp), BEFOREFILTER, ERROR REPORT, &
TRACE ALL),&
FILTER (checkemployee.empduplicate = 0 , ON UPDATE, RAISEERROR 22000 );
This same replicat prm configured on both source and target environments , the processes are running fine, but while try to update the same row at a time in source and target , i'm getting the below error message in both side and replicat process goes ABEND status, please help me to resolve this issue and guide me how to avoid conflict with help of timestamp?>
2011-06-27 18:11:40 GGS ERROR 218 Oracle GoldenGate Delivery for Oracle, REP_C.prm: Error mapping from MY_USER.EMPLOYEE to MY_USER.EMPLOYEE.
2011-06-27 18:11:40 GGS ERROR 190 Oracle GoldenGate Delivery for Oracle,
REP_A.prm: PROCESS ABENDING.

Answer 1

You'll have to look at the full report file.
You've pasted the replicat file for "REP_A", but the error message says REP_C.prm.
From a support perspective, the great thing about report files is that they contain the exact param (*.prm) file used when the process was started. So even if someone changes the prm file after the fact, the report file always contains the "real" params used to start the process.
Also, just to take this one step at a time, try to not run in active/active mode. First, try to replicate in one direction, and just manually create the row in the target that you want to cause the conflict. (It's possible that you don't have the active-active configuration correct... Do you have a trace table to exclude cycles? You should explicitly use the "traceTable" param so this is clear. Or do you want to use "excludeUser" to avoid cycles?)
Thanks,
-Michael