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
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
No comments:
Post a Comment