2012-04-12-15.05.51.833299+060 I3746905A427 LEVEL: Error
PID : 4915432 TID : 33155 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 33155 EDUNAME: db2logmgr (FDBKDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogVendor, probe:2870
MESSAGE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR
"A vendor device reported a media error."
TSM error 41 says:
0041 E DSM_RC_ABORT_EXCEED_MAX_MP
Explanation: All the tape mount points for this node are in use.
System Action: The system returns to the calling procedure.
User Response: Increase the number of allowed tape mounts for this node on the server
am able to connect to the DB on 02p. But application were not able to connect to the db .. and above errors were reported in the diag.log.
Basic checks :
checked whether node is locked at tsm end and whether sufficient space is available.
No errors reported apart from the above mentioned ones.
checked the connectivity of the db.
backup and log archiving works on 01p. only when it moves to 02p - it gives the error and also sometime log archivings gets completed without errors.
@meehange : Yup all other Bakcups work fine except this log archiving.
@Sathya: TSM team says as below:
The issue with archiving log is failing some time as it is looking for the tape. This should not be normal case as the archive log should archive with the management class LOG The management class parameter need to change from default to LOG.
you need to change the management class parameter . You should use the management class as below .
For database backup use management class: DB
For Archive log use the managemenet class: LOG
But I have configured so many db backup but not set TSM management class from db2 end rather it has been set from TSM end.
So I doubt where this TSM management class needs to be set up ?