IBM Support

JR48271: REPLICATION FAILED WITH MANUAL LOG SHIPPING.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In manual log shipping mode, IIDR will not wait for logs to
    become available. Instead, it will end with an event similar to
    the following.
    IBM InfoSphere Change Data Capture daemon has encountered an
    error message.
    Redo log file information not found for subscription
    SHAREDSCRAPE. The Oracle database does not contain valid redo
    log file information corresponding to the log position
    '109510540.0.0.0.0.0.0' for the current database incarnation.
    Error detected in file OracleRedoNativeApi.java at line 1176.
    This may be caused by any of the following: a) The SCN portion
    of the log position 109510540.0.0.0.0.0.0 is invalid. b) The SCN
    associated with log position 109510540.0.0.0.0.0.0 does not
    correspond to a current on-line redo log file and ARCHIVELOG
    mode is not enabled. c) The redo log file(s) corresponding to
    log position 109510540.0.0.0.0.0.0 does not currently exist,
    exists but is inaccessible or exists and is corrupt. d) The
    control file contains invalid information. e) The database was
    shut down abort. Re-start replication will resolve this issue.
    f) There was error archiving redo logs because of insufficient
    disk space. Try to resolve this issue by doing the following and
    re-start replication: a) Change the log position to specify a
    correct SCN value. b) Examine the views V$LOG and V$ARCHIVED_LOG
    to determine a valid SCN for which a corresponding online or
    archived redo log file exists. Change the log position to
    specify a valid SCN for the current database incarnation. c)
    Restore a valid copy of the required redo log file(s) from
    backup. d) Ensure the disk space for archived redo logs is not
    full.
    

Local fix

  • Restart mirroring when a log becomes available.
    

Problem summary

  • In manual log shipping mode, IIDR for Oracle will not wait for
    logs to become available. Instead, it will end with an event
    similar to the following:
    
    
    
    IBM InfoSphere Change Data Capture daemon has encountered an
    error message.
    Redo log file information not found for subscription
    SHAREDSCRAPE. The Oracle database does not contain valid redo
    log file information corresponding to the log position
    '109510540.0.0.0.0.0.0' for the current database incarnation.
    Error detected in file OracleRedoNativeApi.java at line 1176.
    This may be caused by any of the following: a) The SCN portion
    of the log position 109510540.0.0.0.0.0.0 is invalid. b) The SCN
    associated with log position 109510540.0.0.0.0.0.0 does not
    correspond to a current on-line redo log file and ARCHIVELOG
    mode is not enabled. c) The redo log file(s) corresponding to
    log position 109510540.0.0.0.0.0.0 does not currently exist,
    exists but is inaccessible or exists and is corrupt. d) The
    control file contains invalid information. e) The database was
    shut down abort. Re-start replication will resolve this issue.
    f) There was error archiving redo logs because of insufficient
    disk space. Try to resolve this issue by doing the following and
    re-start replication: a) Change the log position to specify a
    correct SCN value. b) Examine the views V$LOG and V$ARCHIVED_LOG
    to determine a valid SCN for which a corresponding online or
    archived redo log file exists. Change the log position to
    specify a valid SCN for the current database incarnation. c)
    Restore a valid copy of the required redo log file(s) from
    backup. d) Ensure the disk space for archived redo logs is not
    full.
    
    This issue affects users running IIDR 10.2 Interim Fix 5,6 or 7
    for Oracle Redo configured for manual log shipping.
    

Problem conclusion

  • This issue is fixed by applying IIDR 10.2 Interim Fix 8 for
    Oracle Redo.
    

Temporary fix

  • Restart mirroring when the log becomes available.
    

Comments

APAR Information

  • APAR number

    JR48271

  • Reported component name

    IS CDC ORACLE

  • Reported component ID

    5725E30OR

  • Reported release

    A20

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-29

  • Closed date

    2013-10-29

  • Last modified date

    2013-10-29

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    IS CDC ORACLE

  • Fixed component ID

    5725E30OR

Applicable component levels

  • RA20 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.2.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 October 2021