Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2003

    Unanswered: "Path to log files" and logarchmeth1 are different why

    info from db cfg for "Path to log files" and logarchmeth1 are different. Why?

     Path to log files = /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/
     First log archive method (LOGARCHMETH1) = DISK:/home/db2inst1/mytemp/log/
    Why are this two paths different? What is the difference between this two parameters?


  2. #2
    Join Date
    Apr 2006
    Provided Answers: 11
    the first is the real path to log files
    logarchmeth1 and 2 are methods to archive the log files. in your case copy the files to new location
    tape-tsm.. can also be specified...see infocenter for details
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified

  3. #3
    Join Date
    Jan 2003
    thanks a lot...

    I would like to create backup (only one file) with logs included inside backup image (so no more one file for backup image and multiple files for logs).

    So I have created the following steps for "backup with logs included", but I need logarchmeth1 to be set to make it possible to use this one backup file principle. See the code:
    db2 create db mydb
    db2 update db cfg for mydb using logarchmeth1 disk:/home/db2inst1/mytemp/log
    db2 backup db mydb to /dev/null
    db2 connect to mydb
    db2 "create table mytable (a int)"
    db2 "insert into mytable values (1)"
    db2 backup db mydb online to /home/db2inst1/mytemp/backup include logs
    db2 terminate
    db2 "restore db mydb from /home/db2inst1/mytemp/backup into mynewdb logtarget /home/db2inst1/mytemp/log"
    db2 "rollforward db mynewdb to end of logs and stop overflow log path (/home/db2inst1/mytemp/log)"
    db2 connect to mynewdb
    db2 "select * from mytable"
    So logarchmeth1 parameter in my database environment is only for "backup include logs" purpose. Is there any other more simple way of having logs included in backup image and not using logarchmeth1 parameter?

    My system: DB2 Enterprise v9.5 on Linux xSeries
    Last edited by grofaty; 05-06-08 at 14:02.

Posting Permissions

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