IT24524: RARE TIMING ISSUE MAY CAUSE INSTANCE CRASH ON BACKUP COMPLETION

APAR status

• Closed as program error.

Error description

• Instance crash can occur due to timing issue with the ending
  db2med process after the completion of a backup.
  
  Stack will show as being similar to:
  _Z28sqloDiagnoseFreeBlockFailureP8SMemFBlkb
  sqlofmblkEx
  _Z22sqleCleanUtilFakeAgentP8sqeAgent
  _Z32sqluMCStartBackupMediaControllerPcj
  sqloEDUEntry
  
  Cleaned up stack would be:
  sqloDiagnoseFreeBlockFailure(SMemFBlk*, bool)
  sqlofmblkEx
  sqleCleanUtilFakeAgent(sqeAgent*)
  sqluMCStartBackupMediaController(char*, unsigned int)
  sqloEDUEntry
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 Users                                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 11.1.4.4 or later.                            *
  ****************************************************************
  

Problem conclusion

• First fixed in Db2 11.1.4.4
  

Temporary fix

Comments

APAR Information

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

  IT24232

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

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSY

     UP