MX Sql automatically aborts a batch of transactions after an IUD (Insert, Update, Delete).
IUD - I wonder who came up with that abbreviation...lol.
So, when loading a database, you might lose 50,000 inserts for 1 referential integrety error. This is unacceptable for a data base with terabytes of data. To get around this, set :
UPD_ABORT_ON_ERROR to off.
To check that setting:
display_explain options 'f' my_query;
The OPT column displays token upd_action_on_error: on_rollback. A value of "x" means that the transaction will be rolled back.
If this solution doesn't work for some reason, all I can see are two options:
1 - Turn Audit off on the target database. That would slow down the load though.
2 - Table up all the batched transactions, and write them to a restart file whenever an error occurs.