Pipeline failure due to Redo Log expiry

Last updated on Nov 10, 2022
On This Page
Applies to Oracle Source (all variants) with Redo Log Pipeline mode.
Error Message Text(s) - The Redo Log has expired. Ensure a log retention period of at least 72 hours in your Oracle instance.

Potential Causes

Hevo is unable to read the Redo Log files as they have expired. This can happen if you have a sudden spike in Events which causes the Redo Log to expire sooner than expected and Hevo is unable to replicate it.

Suggested Actions

  1. In the error displayed in the Pipelines Detailed View, click FIX NOW.

    RedoLog FIX NOW

  2. Do one of the following:

    • Recover the lost Events by ingesting them as historical data. To do this:

      1. Enable the Run Historical Load option.

      2. Select the objects you want to restart the historical load for.

        Enabled Historical Load

      3. Click OK, FIX IT.

    • Skip the expired Events and read the latest available Redo Log files. To do this:

      1. Disable the Run Historical Load option.

        Disabled Historical Load

      2. Click OK, FIX IT.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Sep-05-2022 NA Brought this page under its respective Source documentation folder.
Dec-06-2021 1.77 New document.
Was this page helpful?

Tell us what went wrong