Results 1 to 10 of 10
  1. #1
    Join Date
    Jun 2016
    Posts
    5

    Answered: "A vendor device reported a media error." TSM issue

    The following diaglog file error was displayed :

    2016-06-13-23.12.13.561104+000 I387943352E485 LEVEL: Error
    PID : 11389 TID : 139622709454592 PROC : db2sysc 0
    INSTANCE: dbinst11 NODE : 000 DB : SAMPLE
    HOSTNAME: dev_inst11
    EDUID : 1759 EDUNAME: db2logmgr (SAMPLE) 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."

    2016-06-13-23.12.13.561197+000 E387943838E519 LEVEL: Warning
    PID : 11389 TID : 139622709454592 PROC : db2sysc 0
    INSTANCE: dbinst11 NODE : 000 DB : SAMPLE
    HOSTNAME: dev_inst11
    EDUID : 1759 EDUNAME: db2logmgr (SAMPLE) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3150
    MESSAGE : ADM1848W Failed to archive log file "S0054126.LOG" to "TSM chain 5"
    from "/samlog1/db2/logs/dbinst11/NODE0000/LOGSTREAM0000/".

    2016-06-13-23.12.13.561452+000 E387944358E620 LEVEL: Error
    PID : 11389 TID : 139622709454592 PROC : db2sysc 0
    INSTANCE: dbinst11 NODE : 000 DB : SAMPLE
    HOSTNAME: dev_inst11
    EDUID : 1759 EDUNAME: db2logmgr (SAMPLE) 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 S0054126.LOG to TSM chain 5 from /samlog1/db2/logs/dbinst11/NODE0000/LOGSTREAM0000/.

    2016-06-13-23.12.13.561540+000 I387944979E439 LEVEL: Error
    PID : 11389 TID : 139622709454592 PROC : db2sysc 0
    INSTANCE: dbinst11 NODE : 000 DB : SAMPLE
    HOSTNAME: dev_inst11
    EDUID : 1759 EDUNAME: db2logmgr (SAMPLE) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchivePendingLogs, probe:1500
    MESSAGE : Log archive failed with rc -2045771739 for LOGARCHMETH1.


    db2 get db cfg for SAMPLE |grep -i tsm

    First log archive method (LOGARCHMETH1) = TSM
    TSM management class (TSM_MGMTCLASS) =
    TSM node name (TSM_NODENAME) =
    TSM owner (TSM_OWNER) =
    TSM password (TSM_PASSWORD) =

    help me to solve this issue ! Is it the tsm issue or database side issue ?

    Thanks in advance.

  2. Best Answer
    Posted by db2mor

    "Talk with your TSM-server admin. Error 51 means all TSM-server sessions/resources are in use. This can be a temporary situation. DB2 will continue to retry, and provided you have sufficient local disk-storage capacity in the active-transaction log directory the DB2 will tolerate the TSM outage for a period of time. But you do need to get the issue resolved at the TSM-server end."


  3. #2
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    There must be some message with a "TSM RC" substring in the db2diag.log near the messages you provided.
    Do you have it?
    Regards,
    Mark.

  4. #3
    Join Date
    Jun 2016
    Posts
    5
    Quote Originally Posted by mark.b View Post
    There must be some message with a "TSM RC" substring in the db2diag.log near the messages you provided.
    Do you have it?

    2016-06-13-23.12.14.596850+000 E387945855E389 LEVEL: Error
    PID : 11765 TID : 139622813320992 PROC : db2vend (db2logmgr.meth1 - 1759
    INSTANCE: dbinst11 NODE : 000
    HOSTNAME: dev_inst11
    FUNCTION: DB2 UDB, database utilities, sqluvint, probe:321
    DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
    TSM RC=0x00000033=51 -- see TSM API Reference for meaning.

    I got this in the diaglog file..

  5. #4
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Talk with your TSM-server admin. Error 51 means all TSM-server sessions/resources are in use. This can be a temporary situation. DB2 will continue to retry, and provided you have sufficient local disk-storage capacity in the active-transaction log directory the DB2 will tolerate the TSM outage for a period of time. But you do need to get the issue resolved at the TSM-server end.

  6. #5
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Look at the description of the error.
    -051 E
    Regards,
    Mark.

  7. #6
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    TSM api return codes are signed. db2diag shows +51 (not -51)

  8. #7
    Join Date
    Jun 2016
    Posts
    5
    Quote Originally Posted by db2mor View Post
    TSM api return codes are signed. db2diag shows +51 (not -51)

    i hope this error is with the TSM only not in db2 right ?

  9. #8
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Quote Originally Posted by kiran21 View Post
    i hope this error is with the TSM only not in db2 right ?
    Yes.
    This is a TSM return code.
    Regards,
    Mark.

  10. #9
    Join Date
    May 2016
    Location
    Wellington
    Posts
    22
    Provided Answers: 1
    Clearly only TSM issue. You can ignore if its just a temporary issue and gets resolved in few mins. Could be due to network or no sessions available within TSM. If you see its repeating frequently you need to work with TSM to resolve it.
    There is no impact on the database until the logs fill your disk space as its not archived.

    Cheers!

  11. #10
    Join Date
    Jun 2016
    Posts
    5
    Thank you all for the answers..!

Posting Permissions

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