When you invoke the pdb_xlog command with the remove keyword, Replication Agent creates a script (remove.sql) that, when executed successfully, removes all transaction log objects from the primary database.
In the event that the remove.sql script fails for some reason, some transaction log components may be removed from the primary database and some components may remain.
If errors cause a script execution failure, you should
refer to your primary database error log(s) and the Replication Agent system
log to evaluate the any errors and determine if any corrective action
is necessary.
Even after you correct the cause of the failure, if you simply re-execute the remove.sql script after a failure in which some (but not all) transaction log components were removed, the script will immediately fail again because of the missing (successfully removed) transaction log components.
To avoid this problem and finish removing transaction log components after a script execution failure, you can invoke the pdb_xlog command with the remove keyword followed by the force keyword:
pdb_xlog remove, force
When you use the force keyword, the execution of the remove.sql script continues, even when errors are encountered, until the script is finished.
