Skip to main content Skip to complementary content

Redo log files - access method guidelines

The Replicate Oracle source endpoint can be configured to access online and archived Oracle redo log files using either Oracle LogMiner (Oracle’s built-in method) or Replicate Log Reader (Replicate’s high-speed redo log reader).

Generally, it is recommended to use Replicate Log Reader as it is more efficient, faster, and uses less resources.

Replicate Log Reader is especially recommended in the following situations:

  • The volume of changes in the redo log is more than 30GB/hour
  • The volume of changes is between 10GB/hour and 30GB/hour and the changes need to be processed (i.e. replicated to the target) as fast as possible.
  • There are multiple tasks replicating from the same source. Using Oracle LogMiner is less efficient in this case, as it accesses the redo logs via the database, thereby consuming additional database resources.

Both Replicate Log Reader and Oracle LogMiner are subject to certain limitations, support different compression methods, and require different access permissions. It is therefore strongly recommended to review the relevant sections before configuring the endpoint settings. In the end, your decision whether to use Replicate Log Reader or Oracle LogMiner may be based on a limitation that exists in one but not the other, the way your data is compressed, or the permissions that you are willing to grant the Replicate user.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!