Results 1 to 9 of 9
  1. #1
    Join Date
    Jul 2006
    Location
    Pune , India
    Posts
    433

    Unanswered: Online BKP\restore : Replication

    db2 8.2.0
    windows

    how can i acheive restoring and bringing the target DB to be in sync with Sorce DB after having restored the TGT DB with a image of SRC db.
    i Dont want my Production DB to Go down
    also complete refresh of Tables takes long time as they are quite big tables

    Presently we are doing offline backups > restore > manual refresh,
    But now we are thinking of changing it to Online to prevent downtime for Production Server
    Last edited by rahul_s80; 07-01-07 at 15:08.
    Rahul Singh
    Certified DB2 9 DBA / Application Developer

  2. #2
    Join Date
    Jun 2006
    Posts
    471
    as you say :
    take online backup - move backup image and log files to target system
    restore db - rollforward db - start capture - manual refresh (without export import) and start apply again
    this should do
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  3. #3
    Join Date
    Jul 2006
    Location
    Pune , India
    Posts
    433
    i m a bit doubtful regarding manual refresh .
    even if i have transfered logs to taget db and roll fwd it to end of logs.
    but in the mean time wont the live production DB will get ahead to Target DB.
    How to bring in sync among them?

    manual refresh will just take the current timestamp and go forward from there..(would it solve the diff in rows between source and target)

    i solution i can think of is that while starting 1st time , i have a cold start
    but while testing it took very long time
    Rahul Singh
    Certified DB2 9 DBA / Application Developer

  4. #4
    Join Date
    Jun 2006
    Posts
    471
    to be 100% in synch you do :
    - cold start and refresh all
    - manual refresh and do export/load yourself
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  5. #5
    Join Date
    Jul 2006
    Location
    Pune , India
    Posts
    433
    thanks Guy Przytula

    it would be very helpfull for me if u can elaborate further on
    - manual refresh and do export/load yourself
    Rahul Singh
    Certified DB2 9 DBA / Application Developer

  6. #6
    Join Date
    Jun 2006
    Posts
    471
    automatic refresh = refresh done by apply process
    you don't have any control and need much log space
    with manual refresh : initiated from replication center - right click on subscription - refresh - manual
    this will tell you the names of the tables to be exported from source db
    load these files to target db with load and nonrecoverable
    continue the refresh process, that will reset the pruncntl/subset table
    capture will start to capture from this timestamp
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  7. #7
    Join Date
    Jul 2006
    Location
    Pune , India
    Posts
    433
    i have used asnload for exporting/loading.
    quite fast than earlier tests, But still took approx. 3 hrs to cover up.
    Do you have any idea how to improve its performance.
    Also many of tables went into integrity pending because of Load.
    ne idea to prevent it.

    regards,
    Rahul Singh
    Certified DB2 9 DBA / Application Developer

  8. #8
    Join Date
    Jun 2006
    Posts
    471
    if foreign keys are available - tables are in check pending : this can not be avoided with load
    to fasten the load : utilheap - sortheap - SHEAPTHRES - MAX_QUERYDEGREE are important parameters
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  9. #9
    Join Date
    Jul 2006
    Location
    Pune , India
    Posts
    433
    actually , i have dropped all the references on target DB before starting replication...
    what else could be reason for tables to get into check pending
    there was no interruption while asnload was running..

    thanks ,
    Rahul Singh
    Certified DB2 9 DBA / Application Developer

Posting Permissions

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