IT27789: DEACTIVATE DATA WITH WAIT=YES MIGHT CAUSE SERVER TO CRASH

8.1.8.000-IBM-SPOC-Linuxs390x
8.1.8.000-IBM-SPSRV-Linuxppc64le
8.1.8.000-IBM-SPCMS-WindowsX64
8.1.8.000-IBM-SPCMS-WindowsI32
8.1.8.000-IBM-SPCMS-Linuxx86_64
8.1.8.000-IBM-SPOC-WindowsX64
8.1.8.000-IBM-SPOC-Linuxx86_64
8.1.8.000-IBM-SPOC-LinuxPPC64le
8.1.8.000-IBM-SPOC-AIX
8.1.8.000-IBM-SPSRV-WindowsX64
8.1.8.000-IBM-SPSRV-Linuxx86_64
8.1.8.000-IBM-SPSRV-Linuxs390x
8.1.8.000-IBM-SPSRV-AIX
IBM Spectrum Protect Server V8.1 Fix Pack 8 (V8.1.8) Downloads

APAR status

• Closed as program error.

Error description

• Execute Deactivate Data with wait=yes might cause server to
  crash.  Decommission Node, Decommission VM, and Validate Aspera
  commands are also affected, and can crash when run with
  wait=yes.
  
  L2/Customer diagnostics:
  
  1: core stack1:
  pthread_kill(??, ??) at 0x900000000580f14
  _p_raise(??) at 0x900000000580764
  raise.raise(??) at 0x900000000039568
  abort() at 0x900000000055f64
  masterSynchSignalHandler() at 0x90000002798bd78
  global_lock_ppc_mp() at 0x900000000592eb4
  pthread_cond_signal(??) at 0x90000000058b3a0
  pkSignalCondition(??) at 0x1000099fc
  OutQueueData(??, ??, ??) at 0x100034a9c
  IPRA.$StdPutMsg(??, ??, ??, ??, ??, ??, ??, ??) at 0x10002f438
  outRptfTrFL(0x0, 0x615800006158, 0x1d5714bb8, 0x3db0000f032,
  0x827f2, 0x1716de2c1, 0x1d5711914, 0x1d57119c6) at 0x100032104
  procEndProcessEx(??, ??) at 0x1000ca01c
  IPRA.$EndDeactivateBackup(0x17167fbf8) at 0x1006793d4
  DeactivateBackupThread(??) at 0x1006797f8
  StartThread(0x0) at 0x10000e590
  2: core stack2:
  
  
  AcquireXLatchTracked(0x11001ac28, 0x1f2, 0x8a100000020,
  0x11132db98) at 0x100209088 [untrusted: ./usr/bin/dsmserv]
  OutGetMsgP(??, ??, ??, ??, ??, ??) at 0x100469784 [untrusted:
  ./usr/bin/dsmserv]
  IPRA.$StdPutMsg(??, ??, ??, ??, ??, ??, ??, ??) at 0x100031fc8
  [untrusted: ./usr/bin/dsmserv]
  outRptfTrFL(0x40082, 0x615800006158, 0x24a4bebb8, 0x3db0000f032,
  0x53e, 0x12f00f441, 0x24a4bb914, 0x24a4bb9c3) at 0x100033be4
  [untrusted: ./usr/bin/dsmserv]
  procEndProcessEx(??, ??) at 0x1000dd718 [untrusted:
  ./usr/bin/dsmserv]
  IPRA.$EndDeactivateBackup(0x12e994b78) at 0x100e26b50
  [untrusted: ./usr/bin/dsmserv]
  DeactivateBackupThread(??) at 0x100e26f88 [untrusted:
  ./usr/bin/dsmserv]
  StartThread(0x0) at 0x10000f5fc [untrusted: ./usr/bin/dsmserv]
  
  3: core statck 3:
  
  global_lock_ppc_mp() at 0x90000000057c4b4
  pthread_cond_signal@AF28_12(??, ??) at 0x90000000057490c
  pthread_cond_signal(??) at 0x9000000005731e8
  pkSignalCondition(??) at 0x10000a9fc
  OutQueueData(??, ??, ??) at 0x100036d2c
  IPRA.$StdPutMsg(??, ??, ??, ??, ??, ??, ??, ??) at 0x100030e68
  outRptfTrFL(0x40082, 0x615800006158, 0x8, 0x3d90057c594, 0x1,
  0x114fff741, 0x137218914, 0x1372188f8) at 0x100033be4
  procEndProcessEx(??, ??) at 0x1000dd6a4
  IPRA.$EndDeactivateBackup(0x114ffc378) at 0x100e26950
  DeactivateBackupThread(??) at 0x100e26d88
  StartThread(0x0) at 0x10000f5fc
  
  
  
   Prior to the  crash happen, the following messages logged in
  activity log:
  ANR2017I Administrator ADMIN issued command: DEACTIVATE DATA
  NODENAME TODate=today-30 wait=yes
  ANR0984I Process N for DEACTIVATE DATA started in the FOREGROUND
  at <timestamp>
  
  Platform/Version affected:
  Spectrum Protect Server v7.1.3 or above on all supported
  platforms
  
  Additional keywords:
  TS001660910    TS001608236    DeactivateBackup DecommissionNode
  DecommissionVM ValidateAspera
  

Local fix

• use wait=no to run DEACTIVATE data one at a time
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Spectrum Protect server users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 8.1.8. Note that this is      *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms for reported release:  AIX, Linux, and
  Windows.
  Platforms fixed:  AIX, 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