IC89413: EXPIRATION IS VERY SLOW WHEN PROCESSING AN ARCHIVE DIRECTORY.

APAR status

• Closed as program error.

Error description

• Expiration processing takes a very long time when processing
  against an archive directory.  The actlog shows expiration for a
  single node takes several hours, and it appears hung.
  Extensive time is being spent in db2 processing against the
  ARCH_EXPDIRS view. This tends to happen when a client has
  thousands of files in single directories.
  
  Versions affected: All 6.x Server
  
  Additional Keywords
  dirs directory directories expire expiration perf hang
  performance
  
  
  Additional L2 info:
  Tracing the server with IMEXP DBSTMT traceflags shows the slow
  occurs when runing following SQL statement:
  
  [36][tbcli.c][4187][RdbPrepareAndExecuteStmt]:Executing
  statement 'SELECT
  HL,INSDATE,OBJID,RETINIT_DATE,OBJINFO,BFSIZE,CLNTTYPE,BKSETRET,S
  ETDATATYPE,HELD,VOLDATEGMT,ALIASOF FROM "TSMDB1"."ARCH_EXPDIRS"
  WHERE (NODEID=? AND FSID=? AND OBJTYPE=? AND RETINIT_DATE<=? AND
  MCID=? AND CGID=?) FOR READ ONLY WITH UR --36' submitted from
  imdmgr.c(2692).
  
  Performing fetch for ARCH_EXPDIRS was executed several hours
  later.
  
  [36][tbcli.c][4706][RdbFetchAndGetNextResponse]:Performing fetch
  for imdmgr.c(2692) : 'SELECT
  HL,INSDATE,OBJID,RETINIT_DATE,OBJINFO,BFSIZE,CLNTTYPE,BKSETRET,S
  ETDATATYPE,HELD,VOLDATEGMT,ALIASOF FROM "TSMDB1"."ARCH_EXPDIRS"
  WHERE (NODEID=? AND FSID=? AND OBJTYPE=? AND RETINIT_DATE<=? AND
  MCID=? AND CGID=?) FOR READ ONLY WITH UR --36'
  
  Initial Impact:  Medium
  

Local fix

• Run expiration processing with the SKIPDIRS=YES parameter.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing levels when available.          *
  *                 This problem is currently projected          *
  *                 to be fixed in level 6.3.4.                  *
  *                 Note that this is subject                    *
  *                 to change at the discretion of IBM.          *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Solaris, Linux, and Windows.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP