Db2 Analytics Accelerator for z/OS

nested-group-icon.png

DB2

Expand all | Collapse all

Question about how to stop incremental updates

  • 1.  Question about how to stop incremental updates

    Posted Wed December 23, 2020 01:14 PM

    Hello,

    I have a question about how to stop incremental updates, in case of using Integrated Synchronization .

      (*) Assuming defining location alias and SECPORT for Integrated Synchronization.

    According to the description in manual, when stopping ( or starting ) incremental updates,  the user is guided to operate from IBM Db2 Analytics Accelerator Studio. But, our customer prefers to fire the command from SDSF ( or z/OS console ).

    So, is it possible to fire "MODIFY DDF ALIAS(xx) STOP" command for stopping incremental updates, instead of using IDAA Studio ?

    If not, If not, please let me know the reason why. 



  • 2.  RE: Question about how to stop incremental updates

    Posted Thu December 24, 2020 12:52 AM

    Hi,

    You can write a REXX program to execute the the ACCEL_CONTROL_ACCELERATOR stored procedure with the "<stopReplication/>" parameter. 



    ------------------------------
    Ron Hameiri  
    z/OS Db2 System Programmer and DBA
    Email: Ron.Hameiri@gmail.com
    Linkedin: https://il.linkedin.com/in/ron-hameiri
    ------------------------------



  • 3.  RE: Question about how to stop incremental updates

    Posted Sat December 26, 2020 06:35 PM
    I taken a look at the new publication, 'IBM Integrated Synchronization - Incremental Updates Unleashed', and found it to be a valuable resource in terms of stopping incremental updates, modifying DDF Alias (xx).

    First, I must emphasize the need to follow all installation, activation, and set-up guides.  If you didn't follow such guidelines, you must refer to the product documentation, and certain Redbook, Redpaper, primary network, and the Distributed Data Facility documentation.

    There are a few other concerns involved such as meeting the Integrated Synchronization pre-requisites, requirements, correct configuration settings; inclusive of activation Instructions.  Other instructional guides, e.g. the SMPE/E report MISSINGFIX command to specify in FIX Category, also need to be run.  There are additional resources and installations that will pull in almost all maintenance issues.

    "When incremental updates are enabled later in the configuration console, the application name <app|Name> as well as the signon key <key> will be needed, so that information can be passed onto the accelerator administrator."

    If this is a configuration issue , we need to disable incremental updates, and we need to provision a command to perform such:

    MODIFY DDF ALIAS(<alias-name>) STOP


    And new connections to the secure port can be enabled again with this command:


    -MODIFY DDF ALIAS(<alias-name>) START


    where

    �� <alias-name> is the name for the location alias for Integrated Synchronization.


    "An advantage of location aliases is that they can be started and stopped individually per Db2 member. This can be used to control resources and availability of the secure port for Integrated Synchronization on each Db2 member in a data sharing group, e.g. for planned maintenance. Other distributed workloads that access the general Db2 secure port would not be affected by stopping a location alias."


    To stop receiving incoming connections on the secure port defined by the location alias the above stated Db2 command is needed would be needed.


    I encourage you to visit the documentation at:

    http://www.redbooks.ibm.com/redpieces/pdfs/redp5616.pdf


    There is plenty of information on activating/deactivating incremental updates utilizing IBM's Integrated Synchronization - Incremental Updates Unleashed strategies and techniques.  The documentation specifies the information needed for permissions on transferring a certificate for verification of encrypted connection to DB2; enabling incremental updates in the configuration console, and more . . .



    I sincerely hope this helps.



    Yvonne


    Sent from my iPhone





  • 4.  RE: Question about how to stop incremental updates

    Posted Thu December 24, 2020 03:24 AM

    Hello Katsuko,

    I agree with Ron, you may have to use stored procedure to handle it.

    By the way there is a newly published redbook:

    IBM Integrated Synchronization - Incremental Updates Unleashed REDP-5616

    It doesn't really answer to your quest but it has lot's of interesting info on Insynch.

    Regards Chiara



    ------------------------------
    Chiara Baldan
    ------------------------------



  • 5.  RE: Question about how to stop incremental updates

    Posted Mon December 28, 2020 04:35 AM

    Hello,

    As suggested by other contributes, please use SYSPROC.ACCEL_CONTROL_ACCELERATOR Stored Procedure with <stopReplication/> command.

    https://www.ibm.com/support/knowledgecenter/SS4LQ8_7.5.0/com.ibm.datatools.aqt.doc/sp_msg/SPs/sp_idaa_control_accelerator.html

    If you have further questions, please reach out dwhz@de.ibm.com anytime.

    Best Regards, Cuneyt, IDAA Development



    ------------------------------
    MEHMET CUNEYT GOKSU
    ------------------------------



  • 6.  RE: Question about how to stop incremental updates

    Posted Mon December 28, 2020 05:23 AM

    Thank you very much, Ron, Chiara, Yvonne, Mehmet. 

    All of your suggestions/comments are helpful for me.



    ------------------------------
    KATSUKO HAYASHI
    ------------------------------



  • 7.  RE: Question about how to stop incremental updates

    Posted Mon January 11, 2021 10:28 AM

    Incremental updates should not be stopped by stopping the location alias for an extended period of time. While it is possible for a short period (a few seconds or up to a minute), an unreachable Db2 connection will trigger connection retries from the Incremental Update engine. These connection retries will only be attempted for a short period of time and then the incremental update process will be placed into error.

    To get incremental updates back up and running from that state it is necessary to either invoke the stored procedure to start incremental updates or do it through the GUI. For that reason it makes more sense to also use the stored procedure or GUI to stop incremental updates in the beginning (and it does a clean stop while an unavailable location alias would be an abrupt termination that needs to go through recovery).

    Regards,

    Christian



    ------------------------------
    Christian Michel
    ------------------------------