From version 2.8 onwards Dbreplicate parameters APPLY_LOOP_PREVENTION and MINE_LOOP_PREVENTION will become public ones.
This page is trying to shed some light onto the meaning of the APPLY_LOOP_PREVENTION and MINE_LOOP_PREVENTION parameters.
APPLY_LOOP_PREVENTION ( YES on default)
Purpose: Changes that are mined on the source server and then applied on the target server are not mined again on the target server. This is prevented by the APPLY_LOOP_PREVENTION setting.
Check if the DDL was done by an apply process on this db; modify the DDL by adding comment to the end so next mine/apply can check that it was done by apply.
Valid Settings: YES or NO
MINE_LOOP_PREVENTION ( NO on default)
Purpose: Changes that are mined on the source server and then applied on the target server. This is controlled by the MINE_LOOP_PREVENTION setting.
If set to YES it checks if we skip this DDL due to
- it is created by an APPLY process and apply adds comment to end of the DDL - This is disabled - we need to pass at least CREATE TABLE to apply; we just let apply loop prevention to do it's job for DDL
- an established isolation level triggered by a SET TRANSACTION statement
Valid Settings: YES or NO
If both APPLY_LOOP_PREVENTION and MINE_LOOP_PREVENTION are disabled APPLY will not set/use transaction name 'DBREPL_%'.