Results 1 to 7 of 7

Thread: db2pd output

  1. #1
    Join Date
    Apr 2013
    Posts
    27

    Unanswered: db2pd output

    I am quite confused with the 'db2pd' output.
    When I fired the command as "db2pd -d <DB_NAME> -logs" the output on screens..,

    Logs:
    Current Log Number 22724
    Pages Written 583
    Method 1 Archive Status n/a
    Method 1 Next Log to Archive n/a
    Method 1 First Failure n/a
    Method 2 Archive Status n/a
    Method 2 Next Log to Archive n/a
    Method 2 First Failure n/a

    Can anyone tell me, Why status of some field is shows as not collected??
    Is there any harm in that??
    Or do we need to enable some parameters in order to collect the status??

    Regards,
    Nitin

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Method 1 & 2 refer to LOGARCHMETH1 and LOGARCHMETH2 in the db cfg. So I assume you have not set those up yet (or have not recycled database after changing them so that they take effect).
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  3. #3
    Join Date
    Apr 2013
    Posts
    27
    Hi Marcus,

    The LOGARCHMETH1 is set to LOGRETAIN while LOGARCHMETH2 is kept OFF., will u please tell me how do I recycle the database in order to take effect the changes I have done..

    Nitin

  4. #4
    Join Date
    Apr 2013
    Posts
    27
    And one more thing What steps need to carried out to recycle the database in HADR environment.,

  5. #5
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Quote Originally Posted by db2_nitin View Post
    Hi Marcus,

    The LOGARCHMETH1 is set to LOGRETAIN while LOGARCHMETH2 is kept OFF., will u please tell me how do I recycle the database in order to take effect the changes I have done..

    Nitin
    In the other thread, I told you to do the following:

    db2 update db cfg for <db-name> using LOGARCHMETH1 DISK:<path-name-for-archive-logging>
    db2 force application all
    db2 backup db <db-name>


    Do not set LOGARCHMETH1 to LOGRETAIN.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  6. #6
    Join Date
    Apr 2013
    Posts
    27
    Thanks for useful information.,
    After setting this can I use "db2 update db cfg for <db_name> using LOGRETAIN on"?

  7. #7
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Quote Originally Posted by db2_nitin View Post
    Thanks for useful information.,
    After setting this can I use "db2 update db cfg for <db_name> using LOGRETAIN on"?
    No, leave LOGRETAIN OFF. It is not used by DB2 anymore and that setting is deprecated (obsolete). You only need to set LOGARCHMETH1 to DISK:<path-name-for-archive-logging> and then take one offline backup, and your database will start archiving logs, and you can then do online backups.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

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