Results 1 to 3 of 3
  1. #1
    Join Date
    Jul 2011

    Unanswered: Archival Logging (DB2 UDB V9 AIX 5.3)

    I tried to message to Stolze but I'm not sure if he received.

    Regardless, my understanding as of now and reinforced by other uses on this forum is that as soon as an Active log is filled, (regardless as to whether or not it has committed/uncommitted/rolledback transactions) that log file is archived.

    However, Stolze stated the following in this thread:

    A log file is only archived if it doesn't contain stuff from a transaction that is not yet committed/rolled back. Such a log file is active. Log files that don't contain stuff from running transactions anymore are not active and can be archived. Now, if I have a long running transaction that did some INSERTs that were logged in the first log file, that file cannot be archived. Let's assume that some more transactions (or even the same one) cause log files 2..10 to be used. Even more operations requiring to be logged give us the "when needed" situation: another log file is needed and then a secondary log file is created.

    Which is correct?


  2. #2
    Join Date
    Aug 2008
    Toronto, Canada
    Which is correct?


    The information in the manual is correct.

    "When archiving, a log file is passed to the log manager when it is full, even if the log file is still active and is needed for normal processing."

    See the link provided by n_i in your previous thread.

  3. #3
    Join Date
    Jun 2003
    Toronto, Canada
    Provided Answers: 1
    The terminology can be a bit confusing. Even if a log file becomes archived (that is, moved to archive storage) it may still remain active (i.e. cannot be reused).

Posting Permissions

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