Db2 Analytics Accelerator for z/OS

nested-group-icon.png

DB2

Expand all | Collapse all

Loading a replicated table on IDAA

  • 1.  Loading a replicated table on IDAA

    Posted Wed July 08, 2020 04:12 AM
    Dear all:
    After upgrading from V5 to V7.5.1,  there seems to be some difference for loading a replicated table with lock mode NONE.
    In V5, the reason-code AQT20006E give a clear messages about the requirement.
    However, in V7 the task was run without error code.
    The load_table was performed via stored procedure.  
    Anyone has the same symptom?

    Best Regards.

    ------------------------------
    VICTOR HSIAO
    I/T Specialist
    ------------------------------


  • 2.  RE: Loading a replicated table on IDAA

    Posted Thu July 09, 2020 03:54 AM
    Hi Victor,
    yes, you are right.  In V7 a so-called 'continuous incremental update' method is used which allows that a replicated table can be loaded to the Accelerator without locking it (LOCKMODE TABLE) on the Db2 z/OS side. This means that on Db2 for z/OS applications can continue to change the table by INSERTs, UPDATEs, DELETEs while the table is loaded to the Accelerator. This is an advantage since the applications are not impacted any more by a locked table.
    Any changes on the Db2 for z/OS table while the table is loaded are replicated to the Accelerator as well through a separate mechanism, so you can be sure that all changes are replicated to the Accelerator.
    BTW, even in V5 this 'continuous incremental update' method exists as an additional configurable option in the Configuration Console. In V7 it is the default and only option.
    I hope this helps and let us know if you have further questions.
    Best regards
    Ute Baumbach

    ------------------------------
    Ute Baumbach
    ------------------------------