In all LogMiner implementations, we know the current list of logs and what of those will be mined on the next iteration. We should look into whether we can inspect the current log list that include or come after the low watermark SCN and if those logs have the dictionary begin/end markers set to Yes. If both markers exist, that means the entire data dictionary is present, and we could theoretically skip the next build step.

This has several advantages, which include:

• Less log switches generated by the redo_log_catalog strategy
• Better stability with the redo_log_catalog strategy with multi-connector deployments
• Faster mining session start-ups reading fewer dictionary extracts