Mapping problem with compressed update record (target format)...

One of the group abanded and ggserror.log says:
ERROR   OGG-01296  Oracle GoldenGate Delivery for Oracle, RRHP03.prm:  Error mapping from schema_name.table_name to schema_name.table_name

Discard file says:

Key column column_name (8) is missing from update on table table_name.column_name
and the list continues for all the columns in the table and:
Missing 46 key columns in update for table schema_name.table_name.
Current time: 2014-05-11 12:32:11
Discarded record from action ABEND on error 0


Aborting transaction on dirdat/rc beginning at seqno 63 rba 194046251
                         error at seqno 63 rba 194046975
Problem replicating schema_name.table_name to schema_name.table_name
Mapping problem with compressed update record (target format)...

Well, this table has UNIQUE INDEX defined at the source but somehow that index is missing at the target.
So, created that index at the target and also added this to parameter file to make sure that index column is being used instead of looking for the complete set of columns for the uniqueness.

map schema_name.table_name, target schema_name.table_name, keycols (unique_index_columns) ;

More details for different scenarios:

Replicat Abending With Mapping Error and discard file shows Missing Key Columns (Doc ID 1276538.1)

ORA-39014: One or more workers have prematurely exited.

This time issues with IMPDP.
Export was taken with parallelism of 4 and does Import too but still receiving this error.

ORA-39014: One or more workers have prematurely exited.

ORA-39029: worker 4 with process name "DW01" prematurely terminated

ORA-31671: Worker process DW01 had an unhandled exception.

ORA-00600: internal error code, arguments: [qerxtGetRefOffset_911], [], [], [], [], [], [], [], [], [], [], []

ORA-06512: at "SYS.KUPW$WORKER", line 1838

ORA-06512: at line 2

Reducing the parallelism to 2 and trying now again. Let's see I can get pass with this error.

Update:
Playing with Parallelism did not help in this case.
Digging alert log and the traces, found that the issue is with NESTED TABLES. 

OGG-01172 Discard file (dirrpt/RRHP02a2.dsc) exceeded max bytes (1000000)

One after another...

There is one table that I split into 3 different replicats due to its size and number of transactions that are happening on this table.
These groups abended due to 1403 issue which is due to data missing (well, there was no need to backload data at target and at source there were few dml's on those records).
So, took care of that by adding REPERROR (1403, TRANSDISCARD) to the param file.

Once that's taken care, it started abending again with Discard File exceeded max bytes.

Well, didn't define the max size for discard file and by default it's limiting to 1MB and there were ton's of dml's so within no time it will fill it up (well, need to record all transactions those got discarded).

So, changed the param file to set the limit as 1GB instead:

DiscardFile dirrpt/RRHP02a2.dsc, Append, megabytes 1000