Alternatively, the command DMACTOOS can be submitted from the command line or within a CLP program following a Sync Check. This makes a very simple way to automate checking fidelity of replication and issuing auto corrections of any exceptions.
Are there any possible gotchas? I would share there is slight risk that one of the objects in the OOS list are very large and the resulting REFRESH request could take a considerable amount of time and bandwidth that is unexpected. For that reason, I would not jump into submitting an Activate for ALL OOS too early in your deployment. Set up your replication. Correct any exceptions. Monitor it over time and become familiar with what event on your system and SC timings produce exceptions. After a short while of observation and tuning to make your deployment reliable and predictable, the automated invocation of DMACTOOS can substantially reduce your need to correct any OOS exceptions manually.