IT45278: ANR0158W ON TABLE DEPLOY_CLIENTS WITH HIGH CONSUMPTION OF ACTIVITY LOG

8.1.25.000-IBM-SPSRV-WindowsX64-340
8.1.25.000-IBM-SPSRV-Linuxx86_64-340
8.1.25.000-IBM-SPSRV-Linuxs390x-340
8.1.25.000-IBM-SPSRV-Linuxppc64le-340
8.1.25.000-IBM-SPSRV-AIX-340

APAR status

• Closed as program error.

Error description

• When "SET DEPLOYPKGUpdates OFF" is configured on the HUB and
  SPOKE server, the autodeploy
  
  may generate the following error in the activity log:
  
  ANR0158W Database operation UPDATE for table            
  
                          Deploy.Clients failed with operation
  code 4522 and    
  
                          tracking id 1137d64d0. The data for
  column 5 is:      
  
                          (int16)0.                              
                 
  
   ANR0103E cddeploy.c(3436): Error 4522 updating row in  
  
                          table "Deploy.Clients".                
                 
  
   ANR0105E cddeploy.c(3519): Error setting search bounds  
  
  
                          for table "CD.Client.Packages".        
                 
  
   ANR0171I dbiconn.c(2293): Error detected on 0:105,      
  
  
                          database in evaluation mode.
  
                                           
  
  IBM Storage Protect server is trying to remove entries from the
  deploy_clients table for spoke servers that are disabled for
  client deployment and
  
  
  It is using a different transaction than the one being
  inserted into this table, resulting in lock contention in DB2.
  
  This behavior can be confirmed on db2diag.log showing
  NUM_LOG_SPAN:
  
  MESSAGE : ADM1541W Application "dsmserv" with application handle
  "0-17096" and
  
  application id "*LOCAL.tsmbdc2.240114024458" executing under
  
  authentication id "TSMXXXX " has been forced off of the database
  for
  
  violating database configuration parameter NUM_LOG_SPAN (current
  
  
  value "225"). The unit of work will be rolled back.
  
  On show locks output from Servermon It will be observed:
  
  This shows the deadlock between the two transactions running on
  the same thread in the server:
  
  Tsn=0:123558165, Resurrected=False, InFlight=True,
  Distributed=False, Persistent=True, Addr 1485babd0
   
  *Start ThreadId=339*, Timestamp=12/16/23 23:39:12,
  Creator=cddeploy.c(6086)
   
  Last known in use by ThreadId=339
   
  Participants=1, summaryVote=ReadOnly
   
  EndInFlight False, endThreadId 0, tmidx 0, processBatchCount 0,
  mustAbort False.
   
    Participant DB: voteReceived=False, ackReceived=False
  
   
      DB: Txn 11ff857f0, ReadOnly(NO), connP=1402de8b0,
  *applHandle=17096*, openTbls=1:
  
   
      DB: --> OpenP=12562ce70 for table=TSMMon.Status.
   
      DB: --> RegSql=CDSTMT_PRUNE_DEPLOYCLIENTS_SERVER DELETE for
  table=Deploy.Clients, executed(No).
  
  Tsn=0:123558108, Resurrected=False, InFlight=True,
  Distributed=False, Persistent=True, Addr 141053330
    *Start ThreadId=339*, Timestamp=12/16/23 23:39:11,
  Creator=cddeploy.c(6018)
   
  Last known in use by ThreadId=339
   
  Participants=1, summaryVote=ReadOnly
   
  EndInFlight False, endThreadId 0, tmidx 0, processBatchCount 0,
  mustAbort False.
   
    Participant DB: voteReceived=False, ackReceived=False
   
      DB: Txn 16047e790, ReadOnly(NO), connP=163279190,
  *applHandle=30181*, openTbls=2:
   
      DB: --> OpenP=1221495f0 for table=TSMMon.Status.
   
      DB: --> OpenP=147888170 for table=Deploy.Clients.
   
   
  
  Appl id holding the oldest transaction     = 30181
  Application handle                         = 30181
  
  Application status                         = UOW Waiting
  
   
   
  
  Locks being waited on :
  AppHandl [nod-index] TranHdl    Lockname                   Type
        Mode Conv Sts CoorEDU    AppName  AuthID   AppID          
               
  
  *30181*    [000-30181] 1169       000200E2000000000008001C52
  RowLock    ..X       G   129569     dsmserv  TSMxxxx 
  *LOCAL.tsmbdc2.240114013644    
  
  *17096*    [000-17096] 982        000200E2000000000008001C52
  RowLock    ..U       W   203182     dsmserv  TSMxxxx 
  *LOCAL.tsmbdc2.240114024458      
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Storage 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.25. Note that this is     *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  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