Results 1 to 7 of 7
  1. #1
    Join Date
    Sep 2002
    Posts
    456

    Arrow Unanswered: Numbe of log files

    When doing archival logging, is there any limit to the number of log files created by the database manager?? Assuming database backup being done every day.

    dollar

  2. #2
    Join Date
    Jan 2002
    Location
    Manila, Philippines
    Posts
    71

    for Active Logs

    in DB2 for Windows
    - look at the db config parameters LOGPRIMARY and LOGSECOND

    in DB2 for OS/390
    - the no of active logs is set during installation, after all active logs are filled, it will automatically offload it (write to archive logs)

    HTH,
    Oliver
    Last edited by oliver; 10-09-02 at 22:23.

  3. #3
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: for Active Logs

    ----in DB2 for Windows
    ---- - look at the db config parameters LOGPRIMARY and LOGSECOND


    In DB2 V8, this restriction is being removed ...

  4. #4
    Join Date
    Jan 2002
    Location
    Manila, Philippines
    Posts
    71

    Re: for Active Logs

    Hi Sathyaram_S,

    Are you referring to the -1 value on LOGSECOND ? If not, would you be so kind to post a link to document that details the removal of this restriction ?

    Thanks !
    Oliver



    Originally posted by sathyaram_s
    ----in DB2 for Windows
    ---- - look at the db config parameters LOGPRIMARY and LOGSECOND


    In DB2 V8, this restriction is being removed ...

  5. #5
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: for Active Logs

    Till V7, a transaction can span only logprimary+logsecondary number of log files ....

    On V8, logprimary+logsecondary does not limit the number of logfiles a transacation can span over... In other words, your uncommited transaction can be in the archive logs also ...

    Hope I have been clear ...

    Refer to What's New in V8 on IBM Website ....

    Cheers

    Sathyaram

    Originally posted by oliver
    Hi Sathyaram_S,

    Are you referring to the -1 value on LOGSECOND ? If not, would you be so kind to post a link to document that details the removal of this restriction ?

    Thanks !
    Oliver
    Last edited by sathyaram_s; 10-15-02 at 19:11.

  6. #6
    Join Date
    Jan 2002
    Location
    Manila, Philippines
    Posts
    71

    Re: for Active Logs

    Infinite Active Log feature is enabled by setting the LOGSECOND parameter to -1...

    You still would need to check LOGSECOND value in the db config to know if you have an infinite active log... right ?

    So, in a sense, the LOGPRIMARY+LOGSECOND limitation have not been removed in DB2V8... you'll still have it if you don't have LOGSECOND = -1 setting... right ?

    Thanks !
    Oliver


    Originally posted by sathyaram_s
    Till V7, a transaction can span only logprimary+logsecondary number of log files ....

    On V8, logprimary+logsecondary does not limit the number of logfiles a transacation can span over... In other words, your uncommited transaction can be in the archive logs also ...

    Hope I have been clear ...

    Refer to What's New in V8 on IBM Website ....

    Cheers

    Sathyaram

  7. #7
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: for Active Logs

    Thanks Oliver ...

    I had missed the point about logsecond=-1 in What's new ...


    Cheers

    Sathyaram

    Originally posted by oliver
    Infinite Active Log feature is enabled by setting the LOGSECOND parameter to -1...

    You still would need to check LOGSECOND value in the db config to know if you have an infinite active log... right ?

    So, in a sense, the LOGPRIMARY+LOGSECOND limitation have not been removed in DB2V8... you'll still have it if you don't have LOGSECOND = -1 setting... right ?

    Thanks !
    Oliver

Posting Permissions

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