Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2010
    Posts
    9

    Unanswered: TSM management class modified on TSM side but the changes are ignored by the db

    Hi,

    I have modified the management class parameter (TSM_MGMTCLASS), which was already used by the db, on the TSM server in order to change the primary storage pool where the logs are sent. When I query this management class on the TSM server it is showing me the updated destination but in fact the logs are still sent to the previous storage pool. Do you know why this is happening? Is it needed to do an offline backup or restart of the db before the changes done on TSM side will be taken also on db side?
    I am absolute beginner for db2 so excuse me if the question isn't clear and feel free to ask for details.

    Thanks!

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    TSM_MGMTCLASS affects backups, not log archiving. You will need to specify correct TSM options in the LOGARCHOPT1 (LOGARCHOPT1 ) database configuration parameter.

  3. #3
    Join Date
    Aug 2010
    Posts
    9
    Thanks a lot n_i!
    I learned my lesson now so I will triple check before doing modifications like that

Posting Permissions

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