IC97721: 'BACKUP DB' PROCESS CAN FAIL WITH ANR2993E DUE TO DB2 APAR IC84049

IBM Tivoli Storage Manager V6.3 Fix Pack 5 (6.3.5.000) Server Downloads

APAR status

• Closed as program error.

Error description

• Tivoli Storage Manager Server "backup db" process can fail if
  logs in archive failover log directory can not be moved back to
  archive log directory
  
  Process can fail with
  
   ANR2993E The database backup terminated with a
  log problem. DB2 sqlcode: -2428. DB2
  sqlerrmc:           .     (SESSION: 1234, PROCESS: 1)
  
   ANR0985I Process 1 for Database Backup
  running in the FOREGROUND completed with completion state
  FAILURE at xx:xx:xx. (SESSION: 1234, PROCESS: 1)
  
   ANR1893E Process 1 for Database Backup
  completed with a completion state of FAILURE. (SESSION:
  1234, PROCESS: 1)
  
  
  Under the archive failover log directory path:
  /archive_failover_log_directoryl/RstDbLog/NODE0000
  there can be seen orphaned log entries with 'older' dates/time
  stamps than would be expected.
  
  In db2diag.X.log entries are seen showing log failing to be
  moved back to archive log directory
  
  2013-10-01-13.21.43.791780+060 E22990128A377      LEVEL: Info
  PID     : 459038               TID  : 2479        PROC : db2sysc
  0
  INSTANCE: tsmdu01              NODE : 000
  EDUID   : 2479                 EDUNAME: db2logmgr (TSMDB1) 0
  FUNCTION: DB2 UDB, data protection services,
  sqlpgArchiveLogFile,
  probe:3108
  DATA #1 : <preformatted>
  Started archive for log file S0012712.LOG.
  
  2013-10-01-13.21.52.012613+060 E22990506A471      LEVEL: Info
  PID     : 459038               TID  : 2479        PROC : db2sysc
  0
  INSTANCE: tsmdu01              NODE : 000
  EDUID   : 2479                 EDUNAME: db2logmgr (TSMDB1) 0
  FUNCTION: DB2 UDB, data protection services,
  sqlpgArchiveLogFile,
  probe:3180
  DATA #1 : <preformatted>
  Completed archive for log file S0012712.LOG to
  /archive_failover_log_directoryarchmeth1/tsmdu01/TSMDB1/NODE0000
  /C0000001/ from
  /active_log_directory/NODE0000/.
  
  2013-10-01-14.13.16.545535+060 I22995937A367      LEVEL: Warning
  PID     : 459038               TID  : 2479        PROC : db2sysc
  0
  INSTANCE: tsmdu01              NODE : 000
  EDUID   : 2479                 EDUNAME: db2logmgr (TSMDB1) 0
  FUNCTION: DB2 UDB, data protection services,
  sqlpgRetrieveLogFile,
  probe:4130
  MESSAGE : Started retrieve for log file S0012712.LOG.
  
  2013-10-01-14.13.24.349870+060 I22996305A434      LEVEL: Warning
  PID     : 459038               TID  : 2479        PROC : db2sysc
  0
  INSTANCE: tsmdu01              NODE : 000
  EDUID   : 2479                 EDUNAME: db2logmgr (TSMDB1) 0
  FUNCTION: DB2 UDB, data protection services,
  sqlpgRetrieveLogFile,
  probe:4148
  MESSAGE : Completed retrieve for log file S0012712.LOG on chain
  1 to
            /archive_failover__logdirectory/RstDbLog/NODE0000/.
  
  2013-10-01-14.19.50.871501+060 E22997543A1021     LEVEL: Error
  (OS)
  PID     : 459038               TID  : 3250        PROC : db2sysc
  0
  INSTANCE: tsmdu01              NODE : 000
  EDUID   : 3250                 EDUNAME: db2lfr (TSMDB1) 0
  FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
  MESSAGE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing
  violation."
            DIA8519C A file sharing violation has occurred,
  filename was
  "".
  CALLED  : OS, -, open
  OSERR   : ETXTBSY (26) "Text file busy"
  DATA #1 : Codepath, 8 bytes
  4:11:12:13:22:36:37:63
  DATA #2 : File name, 51 bytes
  /archive_failover__log_directory/RstDbLog/NODE0000/S0012712.LOG
  DATA #3 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS,
  4 bytes
  SQLO_REVISE, SQLO_READWRITE, SQLO_EXCLUSIVE, SQLO_WRITETHRU
  DATA #4 : Hex integer, 4 bytes
  0x000001A0
  DATA #5 : signed integer, 4 bytes
  100
  DATA #6 : signed integer, 4 bytes
  0
  DATA #7 : String, 105 bytes
  Search for ossError*Analysis probe point after this log entry
  for
  further
  self-diagnosis of this problem.
  
  This is  DB2 APAR IC84049
  
  
  Initial Impact:
  Medium
  
  Tivoli Storage Manager Versions Affected:
  Tivoli Storage Manager Server verson 6.2.x and 6.3.x
  
  
  Additional Keywords:
  tsm62 tsm63 db2 backup db error fails
  

Local fix

• Make a copy of affected logs in Archive Failover Log Directory
  and then delete them, and repeat backup db process.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 6.2.6 and 6.3.5. 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

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP