Results 1 to 8 of 8
  1. #1
    Join Date
    May 2015
    Location
    Korea
    Posts
    50

    Unanswered: Transaction Logs > Primary + Secondary

    Under what conditions?
    Last edited by StellaZhang; 09-21-16 at 06:26.

  2. #2
    Join Date
    Jul 2016
    Location
    Germany
    Posts
    20
    Provided Answers: 1

    We need more details

    Hi StellaZhang,

    please have a look at 'Must Read before posting'

    1) Every question posted must include your DB2 Version, fixpack and Edition + your Operating System(including version info) + info on any third party software you use.
    You can get his info using the following commands
    db2level -> to get db2 version and fixpack level
    db2licm -l -> to get the db2 type (WSE, ESE, etc)

    Even the right questions depend on your Operating System

    To get an qualified answer you should give us more informations:

    Configured values for primary and secondary logs

    Configured values for log archiving

    First active log

    'we see the Transaction Logs on Standby are much more than configured value of Primary + Secondary logs'

    What do you mean by see ?

    How about a hardcopy ?

    Good luck
    db2dp

  3. #3
    Join Date
    May 2015
    Location
    Korea
    Posts
    50
    Quote Originally Posted by db2dp View Post
    Hi StellaZhang,

    please have a look at 'Must Read before posting'

    1) Every question posted must include your DB2 Version, fixpack and Edition + your Operating System(including version info) + info on any third party software you use.
    You can get his info using the following commands
    db2level -> to get db2 version and fixpack level
    db2licm -l -> to get the db2 type (WSE, ESE, etc)

    Even the right questions depend on your Operating System

    To get an qualified answer you should give us more informations:

    Configured values for primary and secondary logs

    Configured values for log archiving

    First active log

    'we see the Transaction Logs on Standby are much more than configured value of Primary + Secondary logs'

    What do you mean by see ?

    How about a hardcopy ?

    Good luck
    db2dp
    DB2 V9.7 Fix Pack 3 on AIX 7.1
    DB2 Advanced Enterprise Server Edition

    LOGFILSIZ = 10000
    LOGPRIMARY = 35
    LOGSECOND = 120
    Path to log files = /loghome/SAMPLE/NODE0000/LOGSTREAM0000/
    LOGARCHMETH1 = DISK:/home/db2arch/SAMPLE/
    LOGARCHCOMPR1 = OFF
    Last edited by StellaZhang; 09-21-16 at 06:26.

  4. #4
    Join Date
    Jul 2016
    Location
    Germany
    Posts
    20
    Provided Answers: 1

    quick and dirty

    Hi StellaZhang,

    if you check the First active log number
    against your ls output (next time) you might find
    that those logs are not secondary but expired and not archived.

    Good luck
    db2dp

  5. #5
    Join Date
    May 2015
    Location
    Korea
    Posts
    50
    Thanks, even though I don't know what was the first active log on standby at that time, it cannot be expired or so. I don't know what u mean by expired
    But i do know all those 200 logs had timestamp just within 5 mins, so definitely none was too old.

    So trying to understand how its possible

  6. #6
    Join Date
    Apr 2012
    Posts
    1,006
    Provided Answers: 16
    There was a bug in early fixpacks of DB2 V10.5 fixed by FP7 and higher that kept secondary-log files opened even after archival and present in the archive-log-directory. You might want to check if you have that situation. If the symptom repeats, check with lsof on your active-log directory to see which files are opened. If you do suffer that symptom, suggest you migrate to a current fixpack (e.g FP8) or request a special build.

  7. #7
    Join Date
    May 2015
    Location
    Korea
    Posts
    50
    ok thanks.......
    Last edited by StellaZhang; 09-21-16 at 06:27.

  8. #8
    Join Date
    Jul 2016
    Location
    Germany
    Posts
    20
    Provided Answers: 1
    Hi StellaZhang,

    by expired i mean log files, that are not in use any more and should have been archived.
    With you LOGARCHMETH1 = DISK:/home/db2arch/SAMPLE/ you should be able to check if and when
    your logfiles are archived.
    Just use ls against /home/db2arch/SAMPLE/ and the subdirectories till you find the log files.
    Then check the timestamps against your db2diag.log entries for the 'Completed archive for log file'
    messages.
    If there is a problem with the archiving of log files, they remain in the log directory until they can be archived.

    Good luck
    db2dp

Posting Permissions

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