Results 1 to 6 of 6
  1. #1
    Join Date
    Oct 2004
    Posts
    268

    Unanswered: Archive loging issue

    Linux RH3, DB2 V8.1 FP14

    I will setup an Archive loging for 3 production database on a linux server. The management want me to do a dual logging having one set of logs on the server where databases resides and the other set to be created on a mounted drive from another linux server. My questions are:

    1- What happens when one of the drive is not available to write (Most probably the mounted drive) ?. Does the DB2 stops ? It creates on the available drive and errors out on the not-available one but continues to run ?

    2- Can I still do nightly on/off line full backups ?


    Thanks for any help.

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    1) DB2 will continue on, write a message in db2diag.log, and retry later.

    2) yes.

    Andy

  3. #3
    Join Date
    Oct 2004
    Posts
    268
    Thanks......................

  4. #4
    Join Date
    Oct 2004
    Posts
    268
    Quote Originally Posted by ARWinner
    1) DB2 will continue on, write a message in db2diag.log, and retry later.
    I forgot to ask, If the drive restored later on, will it continue from where it left off or the logs between the time the drive was unaccessible till it become accessible be lost ?

    Thanks again.

  5. #5
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    If you are archiving logs with both LOGARCHMETH1 and LOGARCHMETH2, you should not be losing anything if one of them fails. It should start archiving right where it left off when the resource becomes available.

    Andy

  6. #6
    Join Date
    Oct 2004
    Posts
    268
    Both LOGARCHMETH1 and LOGARCHMETH2.................Thanks............... ..

Posting Permissions

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