Results 1 to 6 of 6

Thread: SQL Replication

  1. #1
    Join Date
    Apr 2007
    Posts
    21

    Unanswered: SQL Replication

    DB2 SQL Replication:

    I face a paculiar situation. This looks weird.

    When I start Apply without starting Capture, it creates files xx.000, xx.001 and so on and does nothing. I am perplexed, why Apply should do something when Capture process is down/ not yet started.

    There is no information in the APPLYTRAIL table.

    There is no information in IBM manual about this.

    Our setup worked till couple weeks back. I am not sure what happened.

    Any thoughts?

  2. #2
    Join Date
    Jun 2006
    Posts
    471
    looks like apply is extracting cd tables and putting data in temp files
    you could start apply with trcflow parameter and see if any message
    these should be in applytrail table
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  3. #3
    Join Date
    Apr 2007
    Posts
    21
    Will Apply process even when Capture is not running?

    We have setup to capture "UPDATE" at the source as pairs of inserts & deletes.

    When we monitor the apply process, it shows Update statements, which I feel is not the way apply is supposed to work.

  4. #4
    Join Date
    Jun 2006
    Posts
    471
    apply and capture are not related - they can work without each other
    the update indication does not seem correct
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  5. #5
    Join Date
    Apr 2007
    Posts
    21
    I am providing the detail setup of our replication.

    We have defined 35 subscription set for processing 455 tables, grouped based on the business functionality.

    Few tables have more than 1 Million records.

    Our biggest table in size is 26 Million.

    Problem appears with one table having 3.3 million, replication of this table seems to be in a loop.

    This is were the Apply is initially performing insert and then swithing over to update. The update is strange. Maybe IBM SQL replication is internally designed to perform update when insert activity fails, this is my guess.

    When we stop the subscription set containing this table, for all other subscription sets the data gets propagated. Now we have to troubleshoot with this information.

    One thing I am surprised is that there are 10 to 20 tables which are bigger in size ( > 4 million) and they don't have this issue.

    Why does replication fail for this table alone?

  6. #6
    Join Date
    Jun 2006
    Posts
    471
    as indicated before - activate the trace
    deactivate all other sets and only have this problem set active
    start apply with trcflow
    the update can be when insert occures and record does already exists, the insert is translated to update.
    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
  •