I opened a Jira earlier this year regarding support for multiple Oracle log destinations. Our situation is that we have an Oracle database with Dataguard enabled. There are always three log archive destinations VALID and ACTIVE on all servers (DEST_1, DEST_2, and DEST_3). The primary server writes to two of those (DEST_1 and DEST_3) and the standby writes to just one destination (DEST_2).

Support was added for multiple destinations in version 3.3.  I've tested that fix, and, unfortunately, it will not work with our use. I've talked to our DBAs, and since all three locations are VALID and ACTIVE for us, it is still picking the first one. This setup is due to Dataguard.

We would love the ability for Debezium to be able to select the destination by another means. The problem for us is that in a switchover or failover event (switchovers happen monthly during maintenance), Debezium will die, and we have to recover it manually. Unfortunately, this won't scale.

Thanks for the continued support!

Which use case/requirement will be addressed by the proposed feature?

• Implementations where the source DB is Oracle with Oracle Dataguard enabled with multiple log archive destinations. During a switchover or failover event, Debezium can recover itself without manual intervention

Implementation idea

• Possibly search for the SCN and select the log archive destination from the provided list based on whichever one contains the SCN? I don't know if this is possible, and it could be quite expensive. Not sure what all the options are.