Results 1 to 2 of 2
  1. #1
    Join Date
    May 2007

    Unanswered: Disable full refresh

    I'm running an old DB2 V7.1 with Data Propagator.
    One of those databases that I am replicating has around 400 tables and some of them very big (10 millions rows +) . After trying many times all choices and options I always get problems filling logs (or timing out). Tried ASNLOAD as apply option as I have heard could aliviate my logs to getting full but it locked some source tables and also got problems.
    So I decided to trick Replicator by disabling all subscription to perform a full refresh and also update prncntl with binary zeros etc.
    But I still confused.
    1) Should I start capture cold or warm?
    2) Before starting apply I will update pruncntl and then start it but what happen to the tables that get the message saying that a full refresh wasn't successful due my disable full refresh update? They will be keep capturing anyway (but not performing a full refresh)?

    How can I solve this?


  2. #2
    Join Date
    Jun 2006
    if you start capture with cold - you request/force a full refresh
    start apply and full refresh will be done or
    start apply and perform a resynch of source and target
    in v7 there was a djra tool that allowed/created statements to perform a resynch without full refresh.
    in v8-9 it is in replication center
    but if re-synch is performed manually - be sure tables are alligned
    if full refresh is needed and disabled - capture will not capture anymore and waiting for the refresh finished
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts