Results 1 to 12 of 12
  1. #1
    Join Date
    Dec 2010
    Posts
    123

    Unanswered: scheduled TSM backup failure

    presently i am woking on db2 8.1, on aix 5.3 one of our server tsm online backup is scheduled for every day, from so many days its working properly but since 3 days its not working, i worked out on that, i found the following error in diag log
    Failed to archive log file S0005454.LOG to TSM chain 0 from 0.
    /db2/failarchpath/Test/db2inst1/JCRDB/NODE0000/C0000000/ with rc = 11.

    By using rc=11 , i found reason as

    The server does not have any space available to store the object”


    my doubt is "how to find path for archive logs"?
    how to find which file system is full???

    i dont have root access in which crontab is scheduled,

    Is ARCHIVE LOG PATH and LOGTARGET mention in the online backup command both indicates same path???
    Thanks in advance.............................
    Last edited by ravichandrapratap; 02-15-11 at 08:03.

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    RC = 11 may not be the real RC coming back from TSM. What else is logged in the db2diag.log?

  3. #3
    Join Date
    Dec 2010
    Posts
    123
    Quote Originally Posted by BELLO4KA View Post
    RC = 11 may not be the real RC coming back from TSM. What else is logged in the db2diag.log?

    it is showing rc = 11 only in diaglog, i did not found any info,. .........
    my doubt is "how to find path for archive logs"?
    how to find which file system is full???

    i dont have root access in which crontab is scheduled,

    Is ARCHIVE LOG PATH and LOGTARGET mention in the online backup command both indicates same path???
    Thanks in advance.............................
    help me out
    Last edited by ravichandrapratap; 02-16-11 at 07:47.

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    Are you sure there are no other errors logged that show some other RC?

    I'm not sure what you mean by "how to find path for archive logs" and "ARCHIVE LOG PATH and LOGTARGET mention in the online backup command both indicates same path"


    You're archiving logs to TSM. Unless specified with LOGARCHMETH1 db cfg parameter or in dsm.sys, the logs will be archived using the default management class. Talk to your TSM admin. They can review the activity logs on the TSM server for errors.

    LOGTARGET is something you can specify during db restore and this parameter has nothing to do with the error you're getting.

  5. #5
    Join Date
    Dec 2010
    Posts
    123
    Quote Originally Posted by BELLO4KA View Post
    Are you sure there are no other errors logged that show some other RC?

    I'm not sure what you mean by "how to find path for archive logs" and "ARCHIVE LOG PATH and LOGTARGET mention in the online backup command both indicates same path"


    You're archiving logs to TSM. Unless specified with LOGARCHMETH1 db cfg parameter or in dsm.sys, the logs will be archived using the default management class. Talk to your TSM admin. They can review the activity logs on the TSM server for errors.

    LOGTARGET is something you can specify during db restore and this parameter has nothing to do with the error you're getting.
    Thnx for your valuable suggestions , if i am trying backup manually i am getting following error
    SQL2428N The BACKUP did not complete because one or more of the requested log files could not be retrieved.
    how can i find which LOGS are MISSING????????

    can anybody suggest me further procedure????
    Last edited by ravichandrapratap; 02-18-11 at 05:11.

  6. #6
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    Quote Originally Posted by ravichandrapratap View Post
    SQL2428N The BACKUP did not complete because one or more of the requested log files could not be retrieved.
    how can i find which LOGS are MISSING????????

    This info will be logged in the diag.log and it can happen for a number of reasons (ie. someone moving the needed logs to another location, a db2 bug, etc...). I can't tell without knowing your db2level and looking at db cfg and complete diag.log. You can specify "exclude logs" on the backup command if you don't require this option.

  7. #7
    Join Date
    Dec 2010
    Posts
    123
    Quote Originally Posted by BELLO4KA View Post
    This info will be logged in the diag.log and it can happen for a number of reasons (ie. someone moving the needed logs to another location, a db2 bug, etc...). I can't tell without knowing your db2level and looking at db cfg and complete diag.log. You can specify "exclude logs" on the backup command if you don't require this option.
    Thanks you so much for ur response, i am providing required data
    Pls find the following data,

    $ db2level
    DB21085I Instance "db2inst1" uses "32" bits and DB2 code release "SQL08027"
    with level identifier "03080106".
    Informational tokens are "DB2 v8.1.1.128", "s061108", "U810098", and FixPak
    "14".
    Product is installed at "/usr/opt/db2_08_01".
    db2 get db cfg


    Dynamic SQL Query management (DYN_QUERY_MGMT) = DISABLE

    Discovery support for this database (DISCOVER_DB) = ENABLE

    Default query optimization class (DFT_QUERYOPT) = 5
    Degree of parallelism (DFT_DEGREE) = 1
    Continue upon arithmetic exceptions (DFT_SQLMATHWARN) = NO
    Default refresh age (DFT_REFRESH_AGE) = 0
    Default maintained table types for opt (DFT_MTTB_TYPES) = SYSTEM
    Number of frequent values retained (NUM_FREQVALUES) = 10
    Number of quantiles retained (NUM_QUANTILES) = 20

    Backup pending = NO

    Database is consistent = NO
    Rollforward pending = NO
    Restore pending = NO

    Multi-page file allocation enabled = YES

    Log retain for recovery status = RECOVERY
    User exit for logging status = YES

    Data Links Token Expiry Interval (sec) (DL_EXPINT) = 60
    Data Links Write Token Init Expiry Intvl(DL_WT_IEXPINT) = 60
    Data Links Number of Copies (DL_NUM_COPIES) = 1
    Data Links Time after Drop (days) (DL_TIME_DROP) = 1
    Data Links Token in Uppercase (DL_UPPER) = NO
    Data Links Token Algorithm (DL_TOKEN) = MAC0

    Database heap (4KB) (DBHEAP) = 4800
    Size of database shared memory (4KB) (DATABASE_MEMORY) = AUTOMATIC
    Catalog cache size (4KB) (CATALOGCACHE_SZ) = (MAXAPPLS*4)
    Log buffer size (4KB) (LOGBUFSZ) = 32
    Utilities heap size (4KB) (UTIL_HEAP_SZ) = 5000
    Buffer pool size (pages) (BUFFPAGE) = 1000
    Extended storage segments size (4KB) (ESTORE_SEG_SZ) = 16000
    Number of extended storage segments (NUM_ESTORE_SEGS) = 0
    Max storage for lock list (4KB) (LOCKLIST) = 1000

    Max size of appl. group mem set (4KB) (APPGROUP_MEM_SZ) = 30000
    Percent of mem for appl. group heap (GROUPHEAP_RATIO) = 70
    Max appl. control heap size (4KB) (APP_CTL_HEAP_SZ) = 20000

    Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = (SHEAPTHRES)
    Sort list heap (4KB) (SORTHEAP) = 4096
    SQL statement heap (4KB) (STMTHEAP) = 16384
    Default application heap (4KB) (APPLHEAPSZ) = 16384
    Package cache size (4KB) (PCKCACHESZ) = (MAXAPPLS*8)
    Statistics heap size (4KB) (STAT_HEAP_SZ) = 4384

    Interval for checking deadlock (ms) (DLCHKTIME) = 10000
    Percent. of lock lists per application (MAXLOCKS) = 10
    Lock timeout (sec) (LOCKTIMEOUT) = 30

    Changed pages threshold (CHNGPGS_THRESH) = 60
    Number of asynchronous page cleaners (NUM_IOCLEANERS) = 11
    Number of I/O servers (NUM_IOSERVERS) = 11
    Index sort flag (INDEXSORT) = YES
    Sequential detect flag (SEQDETECT) = YES
    Default prefetch size (pages) (DFT_PREFETCH_SZ) = AUTOMATIC

    Track modified pages (TRACKMOD) = OFF

    Default number of containers = 1
    Default tablespace extentsize (pages) (DFT_EXTENT_SZ) = 32

    Max number of active applications (MAXAPPLS) = 60
    Average number of active applications (AVG_APPLS) = 10
    Max DB files open per application (MAXFILOP) = 64

    Log file size (4KB) (LOGFILSIZ) = 1000
    Number of primary log files (LOGPRIMARY) = 12
    Number of secondary log files (LOGSECOND) = 20
    Changed path to log files (NEWLOGPATH) =
    Path to log files = /db2/database/db2inst1/NODE0000/SQL00005/SQLOGDIR/
    Overflow log path (OVERFLOWLOGPATH) =
    Mirror log path (MIRRORLOGPATH) =
    First active log file = S0004642.LOG
    Block log on disk full (BLK_LOG_DSK_FUL) = NO
    Percent of max active log space by transaction(MAX_LOG) = 0
    Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0

    Group commit count (MINCOMMIT) = 1
    Percent log file reclaimed before soft chckpt (SOFTMAX) = 100
    Log retain for recovery enabled (LOGRETAIN) = RECOVERY
    User exit for logging enabled (USEREXIT) = OFF

    HADR database role = STANDARD
    HADR local host name (HADR_LOCAL_HOST) =
    HADR local service name (HADR_LOCAL_SVC) =
    HADR remote host name (HADR_REMOTE_HOST) =
    HADR remote service name (HADR_REMOTE_SVC) =
    HADR instance name of remote server (HADR_REMOTE_INST) =
    HADR timeout value (HADR_TIMEOUT) = 120
    HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC

    First log archive method (LOGARCHMETH1) = TSMB2DATA
    Options for logarchmeth1 (LOGARCHOPT1) =
    Second log archive method (LOGARCHMETH2) = OFF
    Options for logarchmeth2 (LOGARCHOPT2) =
    Failover log archive path (FAILARCHPATH) = /db2/failarchpath/JCRDB/
    Number of log archive retries on error (NUMARCHRETRY) = 5
    Log archive retry Delay (secs) (ARCHRETRYDELAY) = 20
    Vendor options (VENDOROPT) =

    Auto restart enabled (AUTORESTART) = ON
    Index re-creation time and redo index build (INDEXREC) = SYSTEM (RESTART)
    Log pages during index build (LOGINDEXBUILD) = OFF
    Default number of loadrec sessions (DFT_LOADREC_SES) = 1
    Number of database backups to retain (NUM_DB_BACKUPS) = 12
    Recovery history retention (days) (REC_HIS_RETENTN) = 366

    TSM management class (TSM_MGMTCLASS) = DB2DATA
    TSM node name (TSM_NODENAME) =
    TSM owner (TSM_OWNER) =
    TSM password (TSM_PASSWORD) =

    Automatic maintenance (AUTO_MAINT) = ON
    Automatic database backup (AUTO_DB_BACKUP) = OFF
    Automatic table maintenance (AUTO_TBL_MAINT) = ON
    Automatic runstats (AUTO_RUNSTATS) = ON
    Automatic statistics profiling (AUTO_STATS_PROF) = OFF
    Automatic profile updates (AUTO_PROF_UPD) = OFF
    Automatic reorganization (AUTO_REORG) = ON

    in Diag.log, i am not getting any error other thne the following error, i am getting following error repeadly

    2011-02-21-10.48.38.761441+330 I632258679C279 LEVEL: Error
    PID : 1282224 TID : 1 PROC : db2logmgr (JCRDB) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1050
    RETCODE : ZRC=0x0000000B=11

    2011-02-21-10.48.38.761575+330 I632258959C280 LEVEL: Error
    PID : 1282224 TID : 1 PROC : db2logmgr (JCRDB) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogVendor, probe:1820
    RETCODE : ZRC=0x0000000B=11

    2011-02-21-10.48.38.761708+330 I632259240C414 LEVEL: Error
    PID : 1282224 TID : 1 PROC : db2logmgr (JCRDB) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
    MESSAGE : Failed to archive log file S0004373.LOG to TSM chain 0 from
    /db2/failarchpath/JCRDB/db2inst1/JCRDB/NODE0000/C0000000/ with rc =
    11.

    2011-02-21-10.48.38.761822+330 E632259655C419 LEVEL: Warning
    PID : 1282224 TID : 1 PROC : db2logmgr (JCRDB) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgCleanFailArchPath, probe:4940
    DATA #1 : <preformatted>
    Unable to archive log file 4373 from failarchpath /db2/failarchpath/JCRDB/db2inst1/JCRDB/NODE0000/C0000000/ for LOGARCHMETH1 due to rc 11.

    SQL2428N The BACKUP did not complete because one or more of the requested log files could not be retrieved.
    presently the logs are not archiving to tsm, they are archiving to failarchpath
    the logs are found in failarchpath, they can't retrieve while backup from failarchpath????
    how can i find which LOGS are MISSING??
    Last edited by ravichandrapratap; 02-21-11 at 07:53.

  8. #8
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    There should be another probe logged by sqlpInitVendorDevice, probe:1030?

  9. #9
    Join Date
    Dec 2010
    Posts
    123
    Quote Originally Posted by BELLO4KA View Post
    There should be another probe logged by sqlpInitVendorDevice, probe:1030?

    Posts: 1,163
    There should be another probe logged by sqlpInitVendorDevice, probe:1030??????
    i can't understand wat u said, can u pls explain me clearly........

  10. #10
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    Check if your db2diag.log has a line that contains:

    FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1030

  11. #11
    Join Date
    Dec 2010
    Posts
    123
    Quote Originally Posted by BELLO4KA View Post
    Check if your db2diag.log has a line that contains:

    FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1030

    Yes u r correct , i found FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1030[/QUOTE]

    WHAT probe:1030 INDICATES????


    pls find the diag.log output as follows:

    2011-02-24-15.15.45.962033+330 I933760912C532 LEVEL: Error
    PID : 1048806 TID : 1 PROC : db2logmgr (RELEASE) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1030
    MESSAGE : sqluvint failed! Vendor rc:
    DATA #1 : Hexdump, 40 bytes
    0x2FF20470 : 0000 16A9 3432 3720 3538 3031 0000 0000 ....427 5801....
    0x2FF20480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x2FF20490 : 0000 016B 0000 0000 ...k....

    2011-02-24-15.15.45.962210+330 I933761445C281 LEVEL: Error
    PID : 1048806 TID : 1 PROC : db2logmgr (RELEASE) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpInitVendorDevice, probe:1050
    RETCODE : ZRC=0x0000000B=11

    2011-02-24-15.15.45.962389+330 I933761727C282 LEVEL: Error
    PID : 1048806 TID : 1 PROC : db2logmgr (RELEASE) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogVendor, probe:1820
    RETCODE : ZRC=0x0000000B=11

    2011-02-24-15.15.45.962571+330 I933762010C430 LEVEL: Error
    PID : 1048806 TID : 1 PROC : db2logmgr (RELEASE) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
    MESSAGE : Failed to archive log file S0000363.LOG to TSM chain 0 from
    /home/db2inst1/failarchpath/RELEASE/db2inst1/RELEASE/NODE0000/C0000000
    / with rc = 11.

    2011-02-24-15.15.45.962723+330 E933762441C434 LEVEL: Warning
    PID : 1048806 TID : 1 PROC : db2logmgr (RELEASE) 0
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgCleanFailArchPath, probe:4940
    DATA #1 : <preformatted>
    Unable to archive log file 363 from failarchpath /home/db2inst1/failarchpath/RELEASE/db2inst1/RELEASE/NODE0000/C0000000/ for LOGARCHMETH1 due to rc 11.

    I am founding the above output for almost all databases in my instance

    If i use db2adutl query db release ,
    i found that logs are not archiving TSM server..they all are storing in failarchpath....


    What i have to do nw?????????????Pls provide me some guidance..
    Last edited by ravichandrapratap; 02-24-11 at 07:35.

  12. #12
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    This gives the RC coming back from TSM -> 5801

    5801 E: DSM_RC_CRYPTO_ICC_ERROR Unexpected error in cryptography library.

    You can find the explanation here:
    http://publib.boulder.ibm.com/infoce...rcms589408.htm


    Ask your TSM admin if there was any recent TSM (client) upgrade. Try to restart the instance to see if that resolves the errors.

Posting Permissions

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