DB Backup problems after upgrading to 6.2

[JSmith310]

After upgrading from TSM 6.12 to 6.2, I can no longer perform a DB backup. I've searched all similar errors, but none of the solutions work for mine setup. Below is the db2diag log. Any assistance would be greatly appreciated.

2010-04-19-15.36.11.149000-240 E630534F459 LEVEL: Info
PID : 3596 TID : 2440 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000 DB : TSMDB1
APPHDL : 0-901 APPID: *LOCAL.SERVER1.100419194526
AUTHID : SYSTEM
EDUID : 2440 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1533
MESSAGE : Starting an online db backup.

2010-04-19-15.36.12.241000-240 E630995F409 LEVEL: Error
PID : 3596 TID : 4392 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000
EDUID : 4392 EDUNAME: db2med.2440.0 (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqluvint, probe:405
DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
TSM RC=0x0000003D=61 -- see TSM API Reference for meaning.

2010-04-19-15.36.12.256000-240 I631406F765 LEVEL: Error
PID : 3596 TID : 4392 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000
EDUID : 4392 EDUNAME: db2med.2440.0 (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:655
DATA #1 : String, 141 bytes
Vendor error: rc = 11 returned from function sqluvint.
Return_code structure from vendor library C:\PROGRA~1\Tivoli\TSM\db2\bin\db2tsm.dll:

DATA #2 : Hexdump, 48 bytes
0x000007FDA7F25CF8 : 3D00 0000 3430 3520 3631 0000 0000 0000 =...405 61......
0x000007FDA7F25D08 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FDA7F25D18 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2010-04-19-15.36.12.272000-240 I632173F380 LEVEL: Error
PID : 3596 TID : 4392 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000
EDUID : 4392 EDUNAME: db2med.2440.0 (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:695
MESSAGE : Error in vendor support code at line: 405 rc: 61

2010-04-19-15.36.12.272000-240 E632555F357 LEVEL: Error
PID : 3596 TID : 4392 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000
EDUID : 4392 EDUNAME: db2med.2440.0 (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqluMCInitBackupMC, probe:683
MESSAGE : Media controller -- Generic error

2010-04-19-15.36.12.272000-240 E632914F450 LEVEL: Error
PID : 3596 TID : 4392 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000
EDUID : 4392 EDUNAME: db2med.2440.0 (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqluMCInitBackupMC, probe:683
MESSAGE : SQL2033N An error occurred while accessing TSM during the processing
of a database utility. TSM reason code: "".

2010-04-19-15.36.12.272000-240 E633366F343 LEVEL: Error
PID : 3596 TID : 4392 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000
EDUID : 4392 EDUNAME: db2med.2440.0 (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqluMCInitBackupMC, probe:683
DATA #1 : String, 2 bytes
61

2010-04-19-15.36.12.272000-240 E633711F572 LEVEL: Severe
PID : 3596 TID : 2440 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000 DB : TSMDB1
APPHDL : 0-901 APPID: *LOCAL.SERVER1.100419194526
AUTHID : SYSTEM
EDUID : 2440 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqlubHandleTSMError, probe:1178
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-2033
DATA #2 : Hexdump, 7 bytes
0x000007FD9F7F4F28 : 0FF8 FFFF 3631 00 ....61.

2010-04-19-15.36.12.272000-240 E634285F987 LEVEL: Severe
PID : 3596 TID : 2440 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000 DB : TSMDB1
APPHDL : 0-901 APPID: *LOCAL.SERVER1.100419194526
AUTHID : SYSTEM
EDUID : 2440 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqlubHandleTSMError, probe:1178
MESSAGE : SQL2033N An error occurred while accessing TSM during the processing
of a database utility. TSM reason code: "".
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2033 sqlerrml: 2
sqlerrmc: 61
sqlerrp : sqlubHan
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

2010-04-19-15.36.12.646000-240 E635274F514 LEVEL: Error
PID : 3596 TID : 2440 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000 DB : TSMDB1
APPHDL : 0-901 APPID: *LOCAL.SERVER1.100419194526
AUTHID : SYSTEM
EDUID : 2440 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqluvdel, probe:1809
DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
TSM RC=0x0000003D=61 -- see TSM API Reference for meaning.

2010-04-19-15.36.12.646000-240 I635790F959 LEVEL: Error
PID : 3596 TID : 2440 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000 DB : TSMDB1
APPHDL : 0-901 APPID: *LOCAL.SERVER1.100419194526
AUTHID : SYSTEM
EDUID : 2440 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqlubDeleteVendorImage, probe:558
MESSAGE : SQL2062N An error occurred while accessing media "". Reason code:
"".
DATA #1 : String, 27 bytes
Error returned by sqluvdel.
DATA #2 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
Vendor RC=0x0000001A=26 -- see DB2 API Guide for meaning.
DATA #3 : Hexdump, 48 bytes
0x000007FDA7F25CF8 : 3D00 0000 3138 3039 2036 3100 0000 0000 =...1809 61.....
0x000007FDA7F25D08 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x000007FDA7F25D18 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2010-04-19-15.36.12.646000-240 E636751F611 LEVEL: Error
PID : 3596 TID : 2440 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000 DB : TSMDB1
APPHDL : 0-901 APPID: *LOCAL.SERVER1.100419194526
AUTHID : SYSTEM
EDUID : 2440 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqlubCleanupPartialBackup, probe:708
MESSAGE : SQL2062N An error occurred while accessing media "". Reason code:
"".
DATA #1 : String, 63 bytes
Could not delete partial backup image created on vendor device.

2010-04-19-15.36.12.740000-240 E637364F437 LEVEL: Severe
PID : 3596 TID : 2440 PROC : db2syscs.exe
INSTANCE: SERVER1 NODE : 000 DB : TSMDB1
APPHDL : 0-901 APPID: *LOCAL.SERVER1.100419194526
AUTHID : SYSTEM
EDUID : 2440 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:843
MESSAGE : Backup terminated.

 

[JSmith310]

Solved

I fixed this isssue by doing a total uninstall of 6.2 and reinstalling it. I then followed the procedure for manually creating the instance and linking it to the existing database.