Find DML SQL statement literal values caused Replicate to Abend.

Generally in Goldengate replicat apply SQL using bind variable so when error occurs report file or error log will have SQL statement with bind
variable. This is hard to catch which literal values caused a problem at Target side. Below is example to see Which literal values caused a
problem.

Error log / Reporfile (Normal Mode)

2013-05-15 11:08:31  WARNING OGG-01004  Oracle GoldenGate Delivery for Oracle, rbmdr.prm:  
Aborted grouped transaction on 'DUMMY_ADMIN_6.DUMMYEVENT', Database error 1403 (OCI Error ORA-01403: no data found, SQL ).

2013-05-15 11:08:31  WARNING OGG-01154  Oracle GoldenGate Delivery for Oracle, rbmdr.prm:  
SQL error 1403 mapping DUMMY_ADMIN.DUMMYEVENT to DUMMY_ADMIN_6.DUMMYEVENT OCI Error ORA-01403: no data found, SQL .

2013-05-15 11:08:31  ERROR   OGG-01296  Oracle GoldenGate Delivery for Oracle, rbmdr.prm:  
Error mapping from DUMMY_ADMIN.DUMMYEVENT to DUMMY_ADMIN_6.DUMMYEVENT.

Edit below parameters in replicat and start again.

NOBINARYCHARS
NODYNSQL
SHOWSYNTAX

Error log / Reporfile (Actual value)

2013-05-15 11:17:35  WARNING OGG-01004  Oracle GoldenGate Delivery for Oracle, rbmdr.prm:  
Aborted grouped transaction on 'DUMMY_ADMIN_6.DUMMYEVENT', Database error 1403 (OCI Error ORA-01403: no data found, SQL ).
2013-05-15 11:17:35  WARNING OGG-01154  Oracle GoldenGate Delivery for Oracle, rbmdr.prm:  

SQL error 1403 mapping DUMMY_ADMIN.DUMMYEVENT to DUMMY_ADMIN_6.DUMMYEVENT OCI Error ORA-01403: no data found, SQL .
2013-05-15 11:17:35  ERROR   OGG-01296  Oracle GoldenGate Delivery for Oracle, rbmdr.prm:  
Error mapping from DUMMY_ADMIN.DUMMYEVENT to DUMMY_ADMIN_6.DUMMYEVENT.