IBM Support

JR65343: IIDR ORACLE XSTREAM MAY SELECT INCOMPLETE BUILD POSITION TO BEGIN CAPTURE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Following an internal Oracle error ORA-01327  due to contention
    between multiple Build Dictionary requests, some Build calls may
    fail and result in incomplete metadata written to the Oracle
    Logs.  The Metadata Dictionary details of those incomplete
    attempts cannot be relied on to begin XStream Capture.
    
    
    IIDR will now filter and exclude such points from being
    selected when a Capture process is created, or re-created to
    advance the original firstScn position where Capture begins
    reading from the log files.
    

Local fix

  • Complete a new full  Dictionary Build  by calling
    ./dmbuilddatadict -I <InstanceName>  and confirm this command
    has returned and resulted in a record or pair of records in
    gv$archived_log  having  DICTIONARY_BEGIN=YES and DICTIONARY_END
    = YES that is more recent than the last failure.
    
    
    The ORA-01327 error can cause an attempt to begin Refresh of a
    subscription to fail.  It may also result in other unexpected
    behaviors for mirroring subscriptions in SharedScrape if such an
    incomplete Dictionary point was used to try and re-position and
    restart SharedScrape when the tables in-scope are changed.
    
    
    If a Refresh failed,   re-start the Refresh after this
    confirmed good Dictionary Build.
    
    If Mirroring resulted in error or failure,  a later full
    dictionary build may allow Mirroring to resume,  but some sanity
    checks on the data replicated between the  Incomplete and
    Completed dictionary points may be warranted.   If data loss did
    occur, a full refresh of all tables would be recommended or
    required.
    
    
    Applying this Fix Update is recommended to prevent unexpected
    behavior.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This issue might affect you if you are using IDR             *
    * 11.4.0.4-5694 or older for Oracle XStream.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Not available                                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IDR 11.4.0.5-5696 or newer for Oracle - XStream   *
    ****************************************************************
    

Problem conclusion

  • Upgrading to IDR 11.4.0.5-5696 or newer for Oracle - XStream
    resolves the issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR65343

  • Reported component name

    IS CDC ORACLE

  • Reported component ID

    5725E30OR

  • Reported release

    B40

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-09-19

  • Closed date

    2023-09-29

  • Last modified date

    2023-09-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

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

Document Information

Modified date:
30 September 2023