Oracle LogMiner to Binary Log Reader Migration FAQs

Binary Log Reader is Fivetran’s latest change data capture (CDC) method for Oracle databases. This method reads Oracle redo log files (online and archived) directly using Oracle BFILE. Binary Log Reader delivers significantly improved performance and reliability than LogMiner. For more information, see our Binary Log Reader documentation.

We have sunset the LogMiner method and replaced it with the Binary Log Reader method. We don't support the LogMiner method for new Oracle connections.

We are migrating existing LogMiner-based connections to Binary Log Reader to improve performance, scalability, reliability, and to remove redo-log availability constraints inherent to LogMiner. To continue syncing data without disruption, you must migrate to Binary Log Reader.

All Oracle connections currently using the LogMiner method must migrate to Binary Log Reader.

For step-by-step instructions, see our quickstart guide for LogMiner migration.

• April 15, 2026: End of support for Oracle connections using LogMiner. Connections may continue syncing after this date, but Fivetran no longer provides support or recovery for LogMiner connections. Also, you won't be able to resume any paused connections after this date.

• May 15, 2026: All connections still using LogMiner stop syncing at the end of this day.

The migration to Binary Log Reader involves the following steps:

1. Check migration readiness

   • Open the Status tab on the connection details page
   • Review any warnings or required setup steps

2. Complete prerequisites

   • Grant the required database permissions
   • Configure any required settings

3. Validate eligibility

   • Run a sync to re-check eligibility
   • Once all checks pass, eligibility test failure warnings will disappear. After the sync cycle completes, no new warnings appear.
   • Connection is ready for migration

4. Automatic migration

   • Within a few days, Fivetran automatically migrates the connection during a sync cycle. If you would like the migration to occur on a specific schedule, create a Fivetran Support ticket.
   • No manual action is required from you

5. Resume syncing with Binary Log Reader

   • The connection resumes syncing using Binary Log Reader
   • Existing configuration and sync behavior are preserved

For a detailed step-by-step instructions, see our quickstart guide for LogMiner migration.

No. The migration updates your existing connection to use Binary Log Reader.

Yes. After your connection meets the prerequisites, you can manually set the incremental sync method (Update method) of your connection to use Binary Log Reader. However, this bypasses the standard automatic migration flow, resulting in a full re-sync. It may also lead to additional tables or columns being captured.

Yes. After meeting the prerequisites, create a Fivetran Support ticket to schedule the migration at a specific time.

No. Migration does not require downtime; it happens during a sync cycle.

After your connection meets the prerequisites, migration typically occurs within a few days. It runs during a sync cycle and completes almost instantly without impacting sync duration.

Yes. You can create a new Binary Log Reader connection, validate it, and then proceed with migrating your existing connection. For more information on creating a new connection with Binary Log Reader, see our setup guide.

No. Existing sync configuration (such as history mode or soft deletes) remains unchanged after migration.

No. Migration only changes the incremental sync method and does not impact the Monthly Active Rows (MAR) usage.

Open the Status tab on the connection details page.

If the connection is not eligible, a warning message lists the pre-migration requirements and any failed eligibility tests, along with exact remediation steps. After your connection meets the prerequisites and you run a sync, the warning automatically disappears.

No. After your connection meets the prerequisites, Fivetran automatically migrates eligible LogMiner connections to Binary Log Reader without a full re-sync. However, if you manually change the incremental sync method to Binary Log Reader, it results in a full re-sync.

Yes. Migration requires a supported Oracle version (11g R2 to 21c).

The warning in your connection’s Status tab displays the grants required for your Oracle deployment.

For the required permissions and how to grant them, see our quickstart guide for LogMiner migration.

• Disk space: Ensure that the Oracle server has free space in the staging area equal to at least five times the size of the largest redo log file, as Binary Log Reader creates temporary local copies of log files.

• Database setup: Complete the required database setup based on your Oracle deployment, including permissions and redo log access.

• Connection configuration: Provide required details such as PDB service name, TDE settings, or ASM configuration, if your environment uses them.

Your connection’s Status tab lists all required prerequisites and remediation steps specific to your environment. For step-by-step instructions, see our quickstart guide for LogMiner migration.

If your database uses TDE, you must:

• Ensure that the wallet is accessible and correctly configured
• Grant the required TDE-related database permissions

In the connection setup form:

• Set the Using TDE Encryption toggle to ON
• Provide the required wallet details, such as the wallet password or auto-login credentials

The warning in your connection’s Status tab lists missing permissions or invalid TDE configuration and provides remediation steps. For step-by-step instructions, see our quickstart guide for LogMiner migration.

If your database stores redo or archive logs in ASM, you must configure a staging location and grant the required permissions.

In your database:

• Create a staging directory on the database host file system
• Create a DIRECTORY object that points to this staging directory
• Grant read and write access to the Fivetran user
• Grant EXECUTE permissions on DBMS_FILE_TRANSFER and UTL_FILE

In the connection setup form:

• Set the Using ASM toggle to ON
• Enter the staging directory path in the ASM Staging Directory Path field

The warning in your connection’s Status tab lists missing permissions or configuration issues and provides remediation steps. For step-by-step instructions, see our quickstart guide for LogMiner migration.

Yes. Binary Log Reader supports all data types supported by LogMiner and additionally supports more data types. Binary Log Reader includes support for types such as BINARY_FLOAT, BINARY_DOUBLE, LONG, LONG RAW, ROWID, and LOB types (BLOB, CLOB, NCLOB) that are not supported by LogMiner. For more information, see our Oracle connector Type Transformations documentation.

Binary Log Reader uses Oracle ROWID to populate _fivetran_id when a table has no primary key or supplemental logging is not enabled. If supplemental logging is enabled and a table has a primary key, Binary Log Reader uses the primary key as the replication key. For more information, see our Binary Log Reader replication key documentation.

Binary Log Reader handles only a defined set of DDL operations without requiring a re-sync. Operations that modify existing rows or cannot be reliably tracked trigger a re-sync. For more information, see our Binary Log Reader supported DDL operations documentation.

Ensure all tables are syncing as expected and monitor your connection for errors or warnings over the next 24 to 48 hours.

You may see new tables after migration because LogMiner excluded certain tables due to its limitations, while Binary Log Reader includes these tables automatically.

To exclude unwanted tables, use the Schema tab on the connection details page.

Re-syncs are rare and typically limited to specific table types.

If you see a data integrity issue after migration, re-sync the affected tables. If the issue persists after re-sync, contact Fivetran Support.

If your connection is not eligible for migration, review the warning in the Status tab to identify the issue. The warning lists missing prerequisites, permissions, or unsupported configuration, along with steps to resolve them. After resolving the issue, run a sync to re-check eligibility.

If migration does not start after you complete the prerequisites, run a sync to trigger eligibility checks and confirm that no warnings remain in your connection’s Status tab. Migration is scheduled automatically and typically occurs within a few days during a sync cycle.

Create a Fivetran Support ticket with a screenshot of the connection status and the eligibility failure messages. The eligibility warning contains the exact checks that failed and the SQL/steps to run; include any DBA output that shows wallet/ASM/log accessibility. Fivetran can validate or help with staging tests.

• TDE failures: Verify that the TDE wallet is accessible and correctly configured, and that all required permissions are granted.

• ASM failures: Ensure ASM is enabled in the connection setup, a valid staging directory is provided, and the required permissions are granted.

• Permission failures: Grant the required database permissions listed in the eligibility warning.

• Error Cannot open log file path C:/.../tde/cwallet.sso (in Windows): Grant the Oracle service account (for example, OracleService<SID>) Full Control permissions for the folder containing cwallet.sso. This resolves ORA-22288: file or LOB operation FILEOPEN failed errors encountered during Binary Log Reader setup tests.

These issues typically occur when required setup steps are incomplete or misconfigured. Review the error messages in the Status tab and follow the provided remediation steps. If needed, use the quickstart guide to verify that you have completed all required setup steps. If the issue persists, create a Fivetran Support ticket and include details about the error and the steps you have taken.

Yes, exceptions are possible, but they are evaluated on a case-by-case basis. Create a Fivetran Support ticket to submit an exception request with justification and environment details. Fivetran reviews exception requests and approves them only with valid justification.

Some Oracle Cloud Infrastructure (OCI) environments may not support the required permissions for Binary Log Reader. So, Oracle on OCI can block Binary Log Reader migration for some OCI-managed services. Environments on OCI may be out of scope for automatic migration; you must either request an exception or work with OCI/the platform provider to enable the required access. Confirm whether your OCI service edition is supported, or submit an exception request if OCI prevents you from meeting the migration prerequisites.

If your database is managed by a third party, coordinate with the vendor to enable the migration prerequisites (PDB service name, wallet access, required grants, ASM staging, etc.). If the vendor blocks migration, submit an exception request and include vendor’s contact or justification; Fivetran evaluates exceptions on a case-by-case basis.

Security concerns about directory creation and directory permissions are common. Fivetran provides guidance and secure configuration options for environments with strict security requirements. If security policies prevent a required privilege, create a Fivetran Support ticket including the specific security requirement so we can propose a locked-down permission pattern or evaluate an exception.