An Oracle database can configure multiple archive log destination paths for various purposes, some for recovery by storing files locally on the server, others for shipping logs to a physical standby, etc.

It's critical that when such a set-up is enabled, the user explicitly configures the log.mining.archive.destination.name configuration. The connector expressly looks for rows that have STATUS=VALID and TYPE=LOCAL. So, if multiple rows match this criteria, this configuration is required.

To solve this problem, we should first clarify this in the documentation, perhaps adding a subsection as a part of the set-up steps to confirm the database configuration and to know what settings are mandatory when configuring the connector.

Secondly, we should probably add a validity check at the outset of the connector that examines the V$ARCHIVE_DEST_STATUS table and fetches the number of VALID destinations. We should emit a WARN message if we obtain more than one and the log.mining.archive.destination.name is not configured.