Results 1 to 10 of 10

Thread: db2 archive log

  1. #1
    Join Date
    Feb 2012
    Posts
    7

    Unanswered: db2 archive log

    I hope db2 archive log command, truncates and archive the log and switches to the next log file. I see this working as expected on Linux but not on Solaris.

    On Linux

    db2inst1> db2 get db cfg for TIMLDAPP | grep "First active"
    First active log file = S0005080.LOG
    db2inst1> db2 archive log for database TIMLDAPP
    DB20000I The ARCHIVE LOG command completed successfully.
    db2inst1> db2 get db cfg for TIMLDAPP | grep "First active"
    First active log file = S0005081.LOG

    On Solaris

    db2inst1> db2 get db cfg for ITIMLDPP | grep "First active"
    First active log file = S0000024.LOG
    reg-itimldap:db2inst1> db2 archive log for database ITIMLDPP
    DB20000I The ARCHIVE LOG command completed successfully.
    db2inst1> db2 get db cfg for ITIMLDPP | grep "First active"
    First active log file = S0000024.LOG

    Due to the issue with archival, hot backup of the database fails, once in a while

    FUNCTION: DB2 UDB, database utilities, sqlubProcessLogExtent, probe:1859 MESSAGE : ADM8010E Backup was unable to copy requested log file "S0000203.LOG"
    for inclusion in the backup image. The backup has been aborted.


    Please advise

  2. #2
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Which DB2-version, fixpack?
    Which version of Solaris?

  3. #3
    Join Date
    Feb 2012
    Posts
    7
    reg-itimldap:db2inst1:ITIMLDPP> uname -a
    SunOS reg-itimldap 5.10 Generic_147440-19 sun4u sparc SUNW,Sun-Fire-V490
    reg-itimldap:db2inst1:ITIMLDPP> db2level
    DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09074"
    with level identifier "08050107".
    Informational tokens are "DB2 v9.7.0.4", "s110330", "IP23240", and Fix Pack
    "4".
    Product is installed at "/opt/IBM/db2/V9.7".

  4. #4
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    The "ADM8010E Backup was unable to copy requested log file "
    symptom looks like:

    IBM IC66414: TIMEOUT VALUE FOR LOG RETRIEVE IS HARD CODED. - United States

    and also

    http://www-01.ibm.com/support/docvie...id=swg21444358
    Last edited by db2mor; 07-31-12 at 12:10. Reason: extra url

  5. #5
    Join Date
    Feb 2012
    Posts
    7
    Recommendation mentioned in the link is DB2 9.7 Fix pack 2. The db2 version used here is DB29.7 Fix Pack 4. So may be, there is a different reason behind this.

  6. #6
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    See also the second link

  7. #7
    Join Date
    Feb 2012
    Posts
    7
    The second link is related to TSM. We are not using TSM, This database is for TIM

  8. #8
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Are there any errors logged for log S0000024.LOG in the db2diag.log?

  9. #9
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Since 'archive log' is async, with respect to the invoker, for how long do you wait after the command, before you query the first active log file ?

    Also, how does the concurrency (tps) compare between your Linux database(s) and this Solaris database?

  10. #10
    Join Date
    Feb 2012
    Posts
    7
    db2girl: There are no error messages for log S0000024.LOG

    db2mor: I issued immediately after the command on both linux and solaris. I also issued the command again now. Which is 4 hours from the time i issued the archive log command. and it still shows S0000024.LOG

Posting Permissions

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