IC88932: SERVER START MIGHT FAIL IN DB2 CRASH RECOVERY WITH SQL1036 FOR TIVOLI STORAGE MANAGER SERVER

APAR status

• Closed as program error.

Error description

• Tivoli Storage Manager server might be affected by DB2 APARs
  IC77236 or IC79941
  
  The DB2 APARs document the following symptom:
  
  Crash recovery may fail with SQL1036 if the mirror log is more
  recent than the same active log due to lost
  I/O on the active file.
  
  You will encounter the following error in the db2diag.log:
  
  2011-06-21-12.03.38.277038+000 I36717E526          LEVEL:
  Warning
  PID     : 14200                TID  : 46912933718336PROC :
  db2sysc
  INSTANCE: u1                   NODE : 000          DB   : TSMDB1
  EDUID   : 19                   EDUNAME: db2loggr (TSMDB1)
  FUNCTION: DB2 UDB, data protection services, sqlpgole,
  probe:1200
  DATA #1 : <preformatted>
  Primary and mirror logpath log file headers are not consistent.
  Primary log file: '/activelog/S0000021.LOG'
  Mirror log file: '/mirrorlog/S0000021.LOG'
  
  2011-06-17-15.22.05.323252+000 E378877E832  Error (OS)
  PID     : 14179                TID  : 46912933718336PROC :
  db2sysc
  INSTANCE: u1                   NODE : 000          DB   : TSMDB1
  EDUID   : 19                   EDUNAME: db2loggr (TSMDB1)
  FUNCTION: DB2 UDB, oper system services, sqloseek, probe:100
  MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
            DIA8411C A file "" could not be found.
  CALLED  : OS, -, lseek                            OSERR: EBADF
  (9)
  DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes
  0x00002AAAC4BFCC70 : FFFF FFFF 0000 0000
  ........
  DATA #2 : File Offset, 8 bytes
  0
  DATA #3 : unsigned integer, 8 bytes
  2
  DATA #4 : String, 105 bytes
  Search for ossError*Analysis probe point after this log entry
  for further
  self-diagnosis of this problem.
  
  The issue is that db2 must use the mirror log file (because the
  active log has less data due to a lost I/O),
  but then db2 uses the filehandle for the active log when
  checking the file size.
  
    Tivoli Storage Manager Versions Affected: all V6
    Initial Impact: Low
    Additional Keywords: TSM DBMarkedBad
  

Local fix

• Make a backup of the log file in the active log path, and delete
  it from the active log path.
  

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.1.6, 6.2.6, and 6.3.3.           *
  *                 Note that this is subject to change at       *
  *                 the discretion of IBM.                       *
  ****************************************************************
  *
  

Problem conclusion

• The 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

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• 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