IT34271: "QUERY SYS" or "Query STG" COMMAND MAY TAKE A LONG TIME TO RETURN FOR USERS USING CLOUD STORAGE POOL(S)

8.1.12.000-IBM-SPSRV-WindowsX64
8.1.12.000-IBM-SPSRV-Linuxx86_64
8.1.12.000-IBM-SPSRV-Linuxs390x
8.1.12.000-IBM-SPSRV-Linuxppc64le
8.1.12.000-IBM-SPSRV-AIX
8.1.10.200-IBM-SPSRV-WindowsX64
8.1.10.200-IBM-SPSRV-Linuxx86_64
8.1.10.200-IBM-SPSRV-Linuxs390x
8.1.10.200-IBM-SPSRV-Linuxppc64le
8.1.10.200-IBM-SPSRV-AIX
8.1.10.200-IBM-SPOC-WindowsX64
8.1.10.200-IBM-SPOC-Linuxx86_64
8.1.10.200-IBM-SPOC-Linuxs390x
8.1.10.200-IBM-SPOC-LinuxPPC64le
8.1.10.200-IBM-SPOC-AIX
IBM Spectrum Protect Server V8.1.10.X interim fix downloads
IBM Spectrum Protect Server V8.1.11.X interim fix downloads
IBM Spectrum Protect Server V8.1 Fix Pack 12 (V8.1.12) Downloads

APAR status

• Closed as program error.

Error description

• Spectrum Protect Server command  "query sys" or "q uery stgpool"
  command may take a long time to return or appears hang for cloud
  type storage pool.
  
  
  Support /Customer diagnostics:
  
  Example of "q sys" slow condition. After execute the "q sys"
  command, the command appears hang,
  
  1:  "show thread",   shows:
  
  Thread 15463525, Parent 15463524: SmAdminCommandThread, Storage
  1232, AllocCnt 8164403 HighWaterAmt 262800
   tid=85ff, ptid=bfe, det=0, zomb=0, join=0, result=0, sess=0,
  procToken=0, sessToken=5977310
       Stack trace:
         0x0900000000219b40 semop
         0x0900000004bf41d0 sqloSSemV
         0x09000000057ab558
  sqlccipcsend__FP17SQLCC_COMHANDLE_TP12SQLCC_COND_T
         0x0900000004bee790 sqlccsend
         0x090000000516f800 sqljcSend__FP10sqljCmnMgr
         0x0900000005138308 sqljrDrdaArCommit__FP14db2UCinterface
         0x0900000005365090
  CLI_sqlCommit__FP15CLI_CONNECTINFOP19CLI_ERRORHEADERINFO
         0x0900000005417840
  SQLTransact2__FP19CLI_ENVIRONMENTINFOP15CLI_CONNECTINFOsP5sqlcaP
  19CLI_ERRORHEADERINFO
         0x09000000054189d8 SQLEndTran
         0x00000001001beca4 dbiEndTxn
         0x000000010014c290 DoEndFuncCallbacks
         0x000000010014a600 tmAbortX
         0x00000001008138fc SdGetChunkCount
         0x0000000100812e70 sdQueryContainer
         0x00000001011c3d10 AdmUseExtCmdTab
         0x00000001008dd18c AdmCommandLocal
         0x00000001008da5f0 admCommand
         0x00000001008f6490 IPRA.$PreFlushDataForSQL
         0x00000001008f5564 IPRA.$ScrubCmdInput
         0x00000001008ed434 IPRA.$PreProcessQuery
         0x00000001008f0fb0 AdmSQLExecute
         0x00000001008dd18c AdmCommandLocal
         0x00000001008da5f0 admCommand
         0x00000001008d620c AdmQuerySys
         0x00000001008dd18c AdmCommandLocal
         0x00000001008da5f0 admCommand
         0x0000000100e47b74 SmAdminCommandThread
         0x00000001000106f0 StartThread
       Holding mutex descP->tableMutex (0x829cdaf50), acquired at
  output.c(1857)
       Acquiring mutex OUTV->mutex (0x110f128d0) at output.c(2678)
  
  
  The thread was doing :
  
  
         0x00000001008138fc SdGetChunkCount
         0x0000000100812e70 sdQueryContainer
  
  2: the server instrumentation trace with collectstmt shows the
  thread stuck at:
  SELECT
  CNTRID,POOLID,DIRID,TYPE,CNTRNAME,MAXSIZE,STATE,FILESIZE,LASTWR,
  FREESPACE,LASTAUDIT,CLOUDSIZE FROM "TSMDB1"."SD_CONTAINERS"
  ORDER BY CNTRNAME FOR READ ONLY OPTIMIZE FOR 10 ROWS WITH UR
  --15463525
  
  
   This SQL is driven from the QUERY SYSTEM command. Depending on
  the number of cloud containers,  this select may take more than
  one hour to return.
  
  Platform /Version affected:
  
  Spectrum Protect Server on all supported version/platforms with
  Cloud container storage
  Additional keywords
  TS004258211 hang qsys cloud container
  

Local fix

• Execute commands in 'q sys" one by one and skip the query for
  cloud stgpool(s) as an alternate to "q sys" command
  

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 levels 8.1.10.200, 8.1.11.100, and  *
  * 8.1.12. 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

• R81A PSY

     UP

• R81L PSY

     UP

• R81W PSY

     UP