IBM Support

Guardium Windows S-TAP monitoring DB2 Database goes inactive and needs to be restarted frequently

Troubleshooting


Problem

This scenario is based on the usage of the Windows S-TAP monitoring DB2 Database. 
The concern arises after Guardium® Administrator receives Windows S-TAP inactive alert frequently and needs to go and manually restart the Windows S-TAP to resume the DAM activities.

Symptom

  1. Windows S-TAP stops suddenly and post restart works fine until the next stoppage
  2. Post executing the Windows S-TAP diagnostics, it was evident from the diag_out.txt file that the Windows S-TAP was not keeping up with the DB2 database traffic
    image 7011
  Log Name: Application
  Source: DB2 Tap
  Date: 2020-10-27T07:36:24.000
  Event ID: 12
  Task: Transmitter
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: <SERVER_HOST_NAME>
  Description: 
One or more log events have been dropped.  STAP is not reading from the server fast enough. 

Document Location

Worldwide

[{"Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"ARM Category":[{"code":"a8m0z000000Gp0IAAS","label":"STAP"}],"ARM Case Number":"TS004382744","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Version(s)"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
11 November 2020

UID

ibm16365117