SQL2025N An I/O error "-72" occurred on media "TSM" on DB2 onoline backup

[AjM]

Hi,

DB2 backup fails with this error message during db2 onlibe backup, sometime works fine.

Also appears this errors on db2diag


2012-08-28-01.15.08.200119-300 E234044483A380 LEVEL: Error
PID : 15335614 TID : 21929 PROC : db2sysc 0
INSTANCE: db2p01 NODE : 000
EDUID : 21929 EDUNAME: db2med.17736.0 (P01) 0
FUNCTION: DB2 UDB, database utilities, sqluMCWriteToDevice, probe:930
MESSAGE : Media controller -- problem writing to vendor device. rc = -2025


2012-08-28-01.15.08.236825-300 E234047007A462 LEVEL: Error
PID : 15335614 TID : 17736 PROC : db2sysc 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-4723 APPID: *LOCAL.db2p01.120828051433
AUTHID : DB2P01
EDUID : 17736 EDUNAME: db2agent (P01) 0
FUNCTION: DB2 UDB, database utilities, sqlubMWResponse, probe:970
MESSAGE : SQL2025N An I/O error "-72" occurred on media "TSM".

2012-08-28-01.15.14.852336-300 E234047470A448 LEVEL: Error
PID : 21364818 TID : 1 PROC : db2vend
INSTANCE: db2p01 NODE : 000
EDUID : 1
FUNCTION: DB2 UDB, database utilities, sqluvDoQueryAndDelete, probe:2762
DATA #1 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
Vendor RC=0x00000006=6 -- see DB2 API Guide for meaning.
MESSAGE : Could not find any objects to delete.
DATA #2 : signed integer, 8 bytes
0



2012-08-28-01.15.16.111932-300 E234048853A592 LEVEL: Error
PID : 15335614 TID : 17736 PROC : db2sysc 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-4723 APPID: *LOCAL.db2p01.120828051433
AUTHID : DB2P01
EDUID : 17736 EDUNAME: db2agent (P01) 0
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.



Any ideas?

Thabks in advance.

[AjM]

Found this on tsm log

ANR0538I A resource waiter has been aborted.

On past days, set this values on dsmserv.out and dsmsta.opt

idletimeout 60
commtimeout 3600
resourcetimeout 60

this is a lanfree backup.

[opermty]

please check this and let us know if it working for you

http://www-01.ibm.com/support/docvie...id=swg21413003

Resolving the problem
Exceeding the COMMTIMEOUT setting on the Tivoli Storage Manager Server is a common problem during DB2 redirected restores. The problem occurs because DB2 spends time rebuilding the containers that the backup data will be restored into. For large databases, this process can take over an hour, and the Tivoli Storage Manager session will remain in a SendW state for this time period which is counted against the COMMTIMEOUT option.

For the restore to be successful, increase the COMMTIMEOUT on the Tivoli Storage Manager Server using the command SETOPT COMMTIMEOUT. This value should be increased to at least 3600, and may need to be set over 10000 seconds for very large (over 200GB) databases.

NOTE: If this is a LANFREE restore, the error might be reported as a -72. In this case, the COMMTIMEOUT and IDLETIMEOUT values would need to be increased on the Storage Agent, also.

regards