TDP SAP DB2 log archiving is failing

[shaaha85]

Hi Guys,

I have installed TDP for SAP DB2 archiving is failing with below error.Where as Backup is running fine.
Please help me to resolve it .Thanks in advance


**************************************************************
First log archive method (LOGARCHMETH1) = DISK:/db2/MWP/log_archive/
Archive compression for logarchmeth1 (LOGARCHCOMPR1) = OFF
Options for logarchmeth1 (LOGARCHOPT1) =
Second log archive method (LOGARCHMETH2) = VENDOR:/opt/tivoli/tsm/tdp_r3/db264/libtdpdb264.so
Archive compression for logarchmeth2 (LOGARCHCOMPR2) = OFF
Options for logarchmeth2 (LOGARCHOPT2) = /db2/MWP/dbs/vendor.env
Failover log archive path (FAILARCHPATH) = /db2/MWP/log_retrieve/
Number of log archive retries on error (NUMARCHRETRY) = 5
Log archive retry Delay (secs) (ARCHRETRYDELAY) = 20
Vendor options (VENDOROPT) = /db2/MWP/dbs/vendor.env
****************************************************************

db2diag.log

2013-08-15-14.28.52.925507+060 E1306110041E888 LEVEL: Error
PID : 28778 TID : 140409900623616 PROC : db2sysc 0
INSTANCE: db2mwp NODE : 000
HOSTNAME: hlxp0bf005
EDUID : 28 EDUNAME: db2logmgr (MWP) 0
FUNCTION: DB2 UDB, data protection services, sqlpInitVendorDevice, probe:1030
MESSAGE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR
"A vendor device reported a media error."
DATA #1 : String, 29 bytes
Init failed! Vendor rc info:
DATA #2 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
Vendor RC=0x0000000B=11 -- see DB2 API Guide for meaning.
DATA #3 : Hexdump, 48 bytes
0x00007FB2F508CAD0 : 0B00 0000 5453 4D45 5250 3A20 5554 4C20 ....TSMERP: UTL
0x00007FB2F508CAE0 : 7061 7273 6520 6572 726F 7221 0000 0000 parse error!....
0x00007FB2F508CAF0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................


2013-08-15-14.28.52.925816+060 I1306110930E451 LEVEL: Error
PID : 28778 TID : 140409900623616 PROC : db2sysc 0
INSTANCE: db2mwp NODE : 000
HOSTNAME: hlxp0bf005
EDUID : 28 EDUNAME: db2logmgr (MWP) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogVendor, probe:1820
MESSAGE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR
"A vendor device reported a media error."


2013-08-15-14.28.52.926009+060 E1306111382E514 LEVEL: Warning
PID : 28778 TID : 140409900623616 PROC : db2sysc 0
INSTANCE: db2mwp NODE : 000
HOSTNAME: hlxp0bf005
EDUID : 28 EDUNAME: db2logmgr (MWP) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3150
MESSAGE : ADM1848W Failed to archive log file "S0001030.LOG" to "VENDOR chain
0" from
"/db2/MWP/log_retrieve/db2mwp/MWP/NODE0000/LOGSTREAM0000/C0000000/".


2013-08-15-14.28.52.926404+060 E1306111897E604 LEVEL: Error
PID : 28778 TID : 140409900623616 PROC : db2sysc 0
INSTANCE: db2mwp NODE : 000
HOSTNAME: hlxp0bf005
EDUID : 28 EDUNAME: db2logmgr (MWP) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3160
MESSAGE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR
"A vendor device reported a media error."
DATA #1 : <preformatted>
Failed to archive log file S0001030.LOG to VENDOR chain 0 from /db2/MWP/log_retrieve/db2mwp/MWP/NODE0000/LOGSTREAM0000/C0000000/.


2013-08-15-14.28.52.926586+060 E1306112502E520 LEVEL: Warning
PID : 28778 TID : 140409900623616 PROC : db2sysc 0
INSTANCE: db2mwp NODE : 000
HOSTNAME: hlxp0bf005
EDUID : 28 EDUNAME: db2logmgr (MWP) 0
FUNCTION: DB2 UDB, data protection services, sqlpgCleanFailArchPath, probe:4940
DATA #1 : <preformatted>
Unable to archive log file 1030 from failarchpath /db2/MWP/log_retrieve/db2mwp/MWP/NODE0000/LOGSTREAM0000/C0000000/ for LOGARCHMETH2 due to rc -2045771739.




Thanks in advance.

 

[TSMCON]

Hi

Have a look at this link

http://www-01.ibm.com/support/docview.wss?uid=swg21621572

What you have provided is the DB2 API return code (11) but the hex dump would normally provide a TSM error code. The common TSM codes are

rc=106 (permissions on a file)
rc=168 (DB2 cannot find the password file)
rc=406 (DB2 cannot find the dsm.opt file). Either 1) the file does not exist, 2) a symbolic link has not been defined between the api and the ba directories, 3) DB2 DSMI_CONFIG not correctly set

 

[shaaha85]

It resolved ....
It was due to environmental variable issue.Though i set it properly, it was not picked up by db user id.
So asked Db2 administration to set the required environmental variable while starting up the Db,and it worked..


http://www-01.ibm.com/support/docview.wss?uid=swg21636143

Thanks all...