Results 1 to 7 of 7
  1. #1
    Join Date
    Jan 2010
    Posts
    8

    Cool Unanswered: unable to archive log file

    Greetings
    We are experiencing an issue with backing up db2 to TSM for CMOD. The OS is AIX 7.1 and DB2 v9.7.0.4", "s110330", "IP23236", and Fix Pack 4. The db2 instance is for CMOD and has been backing up to TSM except when this issue pops up. I found a link that seems to fit see below. The issue is I am not sure how to implement and if it is applicable. I am primarily an AIX Admin, with lite db2 training for db2 with TSM and CMOD. I would be happy to help with scripts or and AIX questions.

    Thanks
    Mike Cantrell

    IBM DB2 log backups are failing with No Archive copygroup - United States

    2014-08-26-12.51.22.216683-300 E4300235A456 LEVEL: Warning
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3150
    MESSAGE : ADM1848W Failed to archive log file "S0007819.LOG" to "TSM chain 0"
    from "/db2db/archive1/NODE0000/SQL00001/SQLOGDIR/".

    2014-08-26-12.51.22.217425-300 E4300692A557 LEVEL: Error
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 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 S0007819.LOG to TSM chain 0 from /db2db/archive1/NODE0000/SQL00001/SQLOGDIR/.

    2014-08-26-12.51.22.217791-300 I4301250A444 LEVEL: Warning
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgRetryFailedArchive, probe:4780
    MESSAGE : Still unable to archive log file 7819 due to rc -2045771739 for
    LOGARCHMETH1 using method 2 and target .

    Product name: "DB2 Enterprise Server Edition"
    License type: "Authorized User Option"
    Expiry date: "Permanent"
    Product identifier: "db2ese"
    Version information: "9.7"
    Enforcement policy: "Soft Stop"
    Number of licensed authorized users: "25"
    Last edited by spmcant; 08-26-14 at 15:02.

  2. #2
    Join Date
    Apr 2012
    Posts
    1,034
    Provided Answers: 18
    What is the TSM api code (it's not shown in your first post) ?
    I think "-2045771739" is not a valid TSM api return code.

    You might see the TSM API error code elsewhere in the db2diag.log (Vendor rc=...) but if not then it also should be in the TSM client error log file (check the location+name of this file in the $DSMI_DIR/dsm.sys for your nodename or a generic default one).

    Is the LOGARCHMETH1 value = TSM (db2 get db cfg for $database-name | grep LOGARCHETH1 ) , or does it also specify a management class?

  3. #3
    Join Date
    Jan 2010
    Posts
    8
    The backup has been working for years and just recently started having this issue occasionally.

    First log archive method (LOGARCHMETH1) = TSM
    Options for logarchmeth1 (LOGARCHOPT1) =
    Second log archive method (LOGARCHMETH2) = OFF
    Options for logarchmeth2 (LOGARCHOPT2) =
    Failover log archive path (FAILARCHPATH) =
    Number of log archive retries on error (NUMARCHRETRY) = 5
    Log archive retry Delay (secs) (ARCHRETRYDELAY) = 20
    Log pages during index build (LOGINDEXBUILD) = OFF

    2014-08-26-21.27.02.215699-300 E9416587A346 LEVEL: Error
    PID : 27525178 TID : 1 PROC : db2vend
    INSTANCE: archive1 NODE : 000
    EDUID : 1
    FUNCTION: DB2 UDB, database utilities, sqluvint, probe:405
    DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
    TSM RC=0x00000035=53 -- see TSM API Reference for meaning.

    2014-08-26-21.27.02.216864-300 E9416934A866 LEVEL: Error
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 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
    0x0A00020010069090 : 0000 0035 3430 3520 3533 0000 0000 0000 ...5405 53......
    0x0A000200100690A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0A000200100690B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

    2014-08-26-21.27.02.217347-300 I9417801A429 LEVEL: Error
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogVendor, probe:1820
    RETCODE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR
    "A vendor device reported a media error."

    2014-08-26-21.27.02.217691-300 E9418231A456 LEVEL: Warning
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3150
    MESSAGE : ADM1848W Failed to archive log file "S0007819.LOG" to "TSM chain 0"
    from "/db2db/archive1/NODE0000/SQL00001/SQLOGDIR/".

    2014-08-26-21.27.02.218412-300 E9418688A557 LEVEL: Error
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 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 S0007819.LOG to TSM chain 0 from /db2db/archive1/NODE0000/SQL00001/SQLOGDIR/.

    2014-08-26-21.27.02.218767-300 I9419246A444 LEVEL: Warning
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgRetryFailedArchive, probe:4780
    MESSAGE : Still unable to archive log file 7819 due to rc -2045771739 for
    LOGARCHMETH1 using method 2 and target .

    2014-08-26-21.27.21.219650-300 E9419691A379 LEVEL: Info
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    DATA #1 : <preformatted>
    Started archive for log file S0007819.LOG.

    2014-08-26-21.27.22.628808-300 E9420071A346 LEVEL: Error
    PID : 27525178 TID : 1 PROC : db2vend
    INSTANCE: archive1 NODE : 000
    EDUID : 1
    FUNCTION: DB2 UDB, database utilities, sqluvint, probe:405
    DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
    TSM RC=0x00000035=53 -- see TSM API Reference for meaning.

    2014-08-26-21.27.22.630074-300 E9420418A866 LEVEL: Error
    PID : 28311576 TID : 4114 PROC : db2sysc 0
    INSTANCE: archive1 NODE : 000
    EDUID : 4114 EDUNAME: db2logmgr (ARCHIVE1) 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
    0x0A00020010069090 : 0000 0035 3430 3520 3533 0000 0000 0000 ...5405 53......
    0x0A000200100690A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0A000200100690B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

  4. #4
    Join Date
    Apr 2012
    Posts
    1,034
    Provided Answers: 18
    TSM api return code 53

    0053 E: DSM_RC_REJECT_ID_UNKNOWN Session rejected: Unknown or incorrect ID entered

    Check the version+fixpack of your *TSM client* in case maintenance is needed.

    Check for additional details in the TSM client log file/error log file.

    Check if any updates need to be made to the $DSMI_DIR/dsm.sys for your nodename as a result of any upgrades to the TSM-SERVER software.

    If this is an intermittent problem, involve your TSM-admin.

  5. #5
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Hi,

    Vendor RC=0x0000000B=11 -- see DB2 API Guide for meaning.
    0011 E: DSM_RC_ABORT_NO_REPOSIT_SPACE Server out of data storage space
    Regards,
    Mark.

  6. #6
    Join Date
    Jan 2010
    Posts
    8
    This link looks to be the issue "http://www-01.ibm.com/support/docview.wss?uid=swg21621572"> Could someome help me understand the solution. The node can log into TSM and the TSM instance is updated daily with new data and q stg shows there is space.







    Archiving of log file may fail after successful DB2 backup
    Technote (troubleshooting)
    Problem(Abstract)
    During a backup of DB2 the retrieve of DB2 log files may fail with the message:
    "ADM1847W Failed to retrieve log file", causing subsequent log archiving to fail.

    Symptom
    In this case the db2diag.log will report the failure of retrieving a log file:

    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.

    FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogVendor,
    probe:3600
    RETCODE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR
    "A vendor device reported a media error."

    FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile,
    probe:4165
    MESSAGE : ADM1847W Failed to retrieve log file "S0003351.LOG" on chain
    "0" to "/db2/SID/log_dir/NODE0000/".

    The current backup of the database then completes.


    Archiving of a new log file starts subsequently, but fails with:

    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.

    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogVendor,
    probe:1820
    RETCODE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR
    "A vendor device reported a media error."

    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile,
    probe:3150
    MESSAGE : ADM1848W Failed to archive log file "S0003374.LOG" to "VENDOR
    chain 0" from "/db2/SID/log_dir/NODE0000/".

    Cause


    This problem is caused by DB2-APAR IC84049 and will be faced, if DB2 is configured to archive the log files twice to Tivoli Storage Manager Server, by specifying the same for both, LOGARCHMETH1 & LOGARCHMETH2.


    Resolving the problem


    The DB2-APAR IC84049 is targeted to be fixed in Fixpack 7 for DB2_9.7.

    To avoid this problem, two copies should be archived using the init<SAP>.utl configuration.

    The option REDOLOG_COPIES should be set to '2' and a second BRARCHIVEMGTCLASS specified instead of changing LOGARCHMETH1 and LOGARCHMETH2 settings.

  7. #7
    Join Date
    Apr 2012
    Posts
    1,034
    Provided Answers: 18
    The swg21621572 technote you mention is most likely not relevant to your symptom, so the resolution (which is specific to SAP) is also not relevant.

    The technote does not show the TSM API return code (it only shows the vendor api generic return code 11 which is *not* the TSM api return code). But the technote clearly explains that the symptom (involving sqlpgRetrieveLogVendor) is specific to the situation when both LOGARCHMETH1 and LOGARCHMETH2 are both set to the same value (and both not OFF).

    Your LOGARCHMETH2 is OFF, according to your earlier post, and that is the normal setting . Unless you've omitted something, your notification-log/db2diag is not showing messages related to log retrieval. Your symptom is intermittent archival failures due to TSM API return code 53.

    Your symptom (TSM api return code +53) is most likely a TSM/netconfig issue (either TSM-client or TSM-server, or network config issue). Often mistaken for the common -53 symptom (note the negative sign). You may get more specific advice on a TSM / ADSM forum, particularly if you show contents of the TSM-client error log around the timestamp of the symptom, and if you post also the TSM-client version+fixpack and TSM-server version+fixpack.


    Are either the DB2-server lpar, or the TSM-server part of an HA configuration?

    Once again: this is most likely not a db2 issue, and you need to involve your TSM-admin and provide the requested information.

Posting Permissions

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