Data Replication

  • 1.  redo log file could not process

    Posted Thu June 24, 2021 12:56 PM

    Situation:

    Mirroring failed. It is a bookmarking method. The error messages are as following:

    redo log file

    I referred to the IBM support website. (InfoSphere Change Data Capture for Oracle Replication - A fatal error has been encountered while processing a redo log...Redo log file information not found. (ibm.com))

    1. Verify if this redo log exists or not

    select name, thread#, sequence#, status, first_time, next_time,

    first_change#, next_change#

    from gv$archived_log

    where 51575650509 between first_change# and next_change#;

    Yes. It exists.

     

    1. Verify that you have no aged/orphaned transactions in the database for

    this SCN 51575650509. If there are any consider ending these transactions.

    SELECT START_DATE,START_TIME,TO_CHAR(START_SCN),START_SCNB,XID

    FROM V$TRANSACTION ORDER BY START_DATE, START_TIME;

    There is no transaction.

     

    1. If you have Test subscriptions or tables which are not currently

    being mirrored and are in a Mirror/Park status these should be set to

    Refresh/Park

    All subscriptions are in method mirror and status active.


    Refresh is not an option for my case. The database user have "alter any table" privileges. Anyone know about this issues? Please help me if anyone have any idea. Thank you.



    ------------------------------
    dataicons
    ------------------------------


    #DataIntegration
    #DataReplication


  • 2.  RE: redo log file could not process

    Posted Fri June 25, 2021 12:52 AM
    Hello

    You have tested that the Oracle database metadata knows about the log.

    The log file itself may not necessarily be present in the system - it may have been removed and the Oracle metadata not updated.

    Or the CDC user in the OS may not have read permission to the log files.

    Typically the CDC OS user would be a member of the dba and/or oinstall groups to ensure that it has read-only access at least to Oracle objects include log files

    Regards

    ------------------------------
    Robert Philo
    ------------------------------