IBM Support

JR62158: SCHEDULED END BY TIME DOESN'T WORK WHEN DB IS 100% IDLE, SHARED SCRAPE IS USED AND OPERATIONS IN THE CHANGE LOG EXIST

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

  • Subscription may not stop via scheduled end by time if database
is 100% idle and subscription is using shared scrape and has
found operations in the change log that are past its start
bookmark and the change log had added all operations from the
source database log before the source database became idle.

Local fix

  • Keeping a dummy subscription running all the time. The dummy
subscription would have one table and no operations are ever
performed on it, so there is never anything to replicate. This
will keep the shared scrape parser running constantly.

Problem summary

  • ****************************************************************
* USERS AFFECTED:                                              *
* This issue affects clients with subscriptions configured to  *
* mirror until a scheduled end time or position.               *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* A subscription may not stop via scheduled end by time if     *
* database is 100% idle and subscription is using shared       *
* scrape, has found operations in the change log that are past *
* its start bookmark, and the change log had added all         *
* operations from the source database log before the source    *
* database became idle.                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to IDR LUW 11.4.0.2-5544 or newer for all LUW        *
* engines.                                                     *
****************************************************************

Problem conclusion

  • Upgrading to IDR LUW 11.4.0.2-5544 or newer for all LUW engines
resolves the issue.

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    JR62158
    • 

  • Reported component name
    IS CDC DB2 LUW
    • 

  • Reported component ID
    5725E30DL
    • 

  • Reported release
    B40
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2020-03-22
    • 

  • Closed date
    2020-04-15
    • 

  • Last modified date
    2020-04-15
    • 





    

  • 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 DB2 LUW
    • 

  • Fixed component ID
    5725E30DL
    • 



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

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            16 April 2020
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback