IBM Support

JR63847: NECCESSITYEXCEPTION "CHANGE LOG BLOCK WE ARE TRYING TO READ IS EMPTY!" IF TIMING CIRCUMSTANCES ARE UNFORTUNATE

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

  • NeccessityException "Change log block we are trying to read is
    empty!" if timing circumstances are unfortunate.
    
    com.datamirror.ts.util.TsExceptionHandler
    processUnhandledException()
    An uncaught exception has occurred:
    com.datamirror.ts.assertion.NecessityException
    The error value is " Change log block we are trying to read is
    empty!".| at
    com.datamirror.ts.assertion.Necessity.necessity(Necessity.java:6
    1)| at
    com.datamirror.ts.scrapers.singlescrape.ChangeLogPointer.getOpsF
    romMemory(ChangeLogPointer.java:796)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This issue might affect you if you are using IDR             *
    * 11.4.0.3-5594 or earlier as a source engine, and shared      *
    * scrape is active.                                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When the source engine encountered an empty block, it would  *
    * stop.                                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IDR 11.4.0.4-5599 or newer for all LUW engines    *
    ****************************************************************
    

Problem conclusion

  • Upgrading to IDR 11.4.0.4-5599 or newer for all LUW engines
    resolves this issue. When a source engine encounters an empty
    block, it now continues on to the next non-empty block.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR63847

  • 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

    2021-06-20

  • Closed date

    2021-07-13

  • Last modified date

    2021-07-13

  • 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

  • RB40 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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"}]

Document Information

Modified date:
16 July 2021