OGG-01154 : Error mapping

https://community.oracle.com/thread/2383700?start=0&tstart=0
https://docs.oracle.com/goldengate/1212/gg-winux/GWURF/gg_parameters088.htm#GWURF529

If this is the first time u run into 1403 in your configured GG environment that has been running for a while, you can try to manually fix it by looking at the data from discard file/trail file. You can also try INSERTMISSINGUPDATES but there are a couple of cavets you need to pay attention. 

If you just set this up and bumped into this error, then most likely you didnt have a clean target database to begin with. Might as well just re-instantiate the target and re-try the trail files.

Valid For

Replicat

Description

Use the INSERTMISSINGUPDATES and NOINSERTMISSINGUPDATES parameters to control whether or not Oracle GoldenGate inserts a record based on the source record when the target record does not exist.

INSERTMISSINGUPDATES inserts the missing update but should only be used when the source database logs all column values, whether or not they changed). It can work with a database that uses a compressed form of updates (where only the changed values are logged) if the target database allows NULL to be used for the missing column values.

When the default of NOINSERTMISSINGUPDATES is in effect, a missing record causes an error, and the transaction may abend depending on REPERRORsettings.

The INSERTMISSINGUPDATES and NOINSERTMISSINGUPDATES parameters are table-specific. One parameter remains in effect for all subsequent MAPstatements, until the other parameter is encountered.

REPLICAT rep3

INSERTMISSINGUPDATES

Default

NOINSERTMISSINGUPDATES

OR use , ADDTRANDATA SCOTT.*  for resolve this issue .