Results 1 to 2 of 2
  1. #1
    Join Date
    Jan 2004
    Posts
    2

    Unanswered: TSM Restore across Linux Servers

    We are running db2 v8.1 fp 5 on Linux SLES 8.1 fp 3.

    I am having problems restoring a production database to our test server. We have the prod db backed up on TSM.
    I have created an empty database and changed the tsm configuration parameters on the new db. We also edited the tsm client sys.opt file to prompt for a password & changed the nodename to the production one.

    When I issue the db2adutl command I can see the list of backups for the database I am trying to restore. However when I issue the restore command it give me the following error.

    restore db sessadm use tsm taken at 20051225 redirect
    SQL2542N No match for a database image file was found based on the source database alias "SESSADM" and timestamp "20051225" provided.

    It also throws the following error into the diag log.

    2005-12-28-09.57.08.165420 Instance:ncudb6 Node:000
    PID:11452(db2med.11444.0) TID:1024 Appid:none
    database utilities sqluMapVend2MediaRCWithLog Probe:0

    Vendor error: rc = 6 returned from function sqluvint.
    Return_code structure from vendor library libtsm.a:


    0xBFFFCB10 : 7900 0000 3737 3020 3132 3100 0000 0000 y...770 121.....
    0xBFFFCB20 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0xBFFFCB30 : 0000 0000 0000 0000 ........

    2005-12-28-09.57.08.179495 Instance:ncudb6 Node:000
    PID:11452(db2med.11444.0) TID:1024 Appid:none
    database utilities sqluMapVend2MediaRCWithLog Probe:0


    2005-12-28-09.57.08.182992 Instance:ncudb6 Node:000
    PID:11452(db2med.11444.0) TID:1024 Appid:none
    database utilities sqluMCProcessRestoreStates Probe:30

    Media controller -- invalid device type. dev type = 65

    2005-12-28-09.57.08.183012 Instance:ncudb6 Node:000
    PID:11444(db2agent (SESSADM)) TID:1024 Appid:*LOCAL.ncudb6.032928155708
    database utilities sqludMRResponse Probe:10 DatabaseESSADM

    DiagData
    0x305A0870 : 12F6 FFFF 5345 5353 4144 4DFF 3230 3035 .÷  SESSADM 2005
    0x305A0880 : 3132 3235 3034 3539 3130 00 1225045910.

    2005-12-28-09.57.08.714378 Instance:ncudb6 Node:000
    PID:11444(db2agent (SESSADM)) TID:1024 Appid:*LOCAL.ncudb6.032928155708
    database utilities sqludMRResponse Probe:20 DatabaseESSADM

    DiagData
    0xBFFF3C80 : 0xFFFFF612 .÷  

    2005-12-28-09.57.08.727108 Instance:ncudb6 Node:000
    PID:11444(db2agent (SESSADM)) TID:1024 Appid:*LOCAL.ncudb6.032928155708
    database utilities sqludDeleteBRGFile Probe:10 DatabaseESSADM

    DiagData
    0x305A0870 : D909 0000 0A00 0F86 2E42 5247 00 ┘........BRG.

    2005-12-28-09.57.08.739112 Instance:ncudb6 Node:000
    PID:11444(db2agent (SESSADM)) TID:1024 Appid:*LOCAL.ncudb6.032928155708
    database utilities sqludDeleteBRGFile Probe:10 DatabaseESSADM

    0x305A0870 : D909 0000 0A00 0F86 2E42 5247 00 ┘........BRG.

    2005-12-28-09.57.08.750531 Instance:ncudb6 Node:000
    PID:11444(db2agent (SESSADM)) TID:1024 Appid:*LOCAL.ncudb6.032928155708
    database utilities sqludrsa Probe:110 DatabaseESSADM

    Restore Terminated.

    2005-12-28-09.57.08.789627 Instance:ncudb6 Node:000
    PID:11922(db2bp) TID:1024 Appid:none
    database utilities sqludValidateParameters Probe:820

    DiagData
    0x413770D4 : 0xFFFFF828 (°  


    I anyone could give me some pointers on what is going wrong I would appreciate it.

    Thanks

  2. #2
    Join Date
    Sep 2003
    Posts
    237
    In my tsm restore command there is a time after the date ; like 20051118033101 ; try with this time extension which you can see with db2adutl;
    mota

Posting Permissions

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