When we introduced the Hybrid mining strategy, we adjusted the LogMiner query to include fetching rows where the TABLE_NAME column was prefixed with "OBJ# ". These rows represent tables that have recently had a DDL change, and the redo entry's object identifier, data object identifier, or object version no longer matches the data dictionary. By reducing the fetch load, there are some corner cases where this should lead to better overall performance for users as this reduces network bandwidth usage and less stress on the connector to filter out unnecessary changes.

As these rows are filtered out automatically when the Hybrid strategy is not used in the connector, there is no reason for these rows to even be fetched outside the Hybrid strategy. This change will only apply when setting log.mining.query.filter.mode. When this mode is left set as none or the user has not set any include/exclude table filters, this will not apply as the idea is that all filtering is done at the connector level.