Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
In my last blog, we learned how to gather diagnostic files using Windows S-TAP Must Gather. Today's goal is to explain the list of files that can be gathered by Windows S-TAP Must Gather.Let me show a typical example output of new Windows S-TAP Must Gather. The actual output may be different. It depends on the Guardium products and files in the target database server.
Windows S-TAP Must Gather V2 started generating its own log files. This helps when there is a problem in running the script.
These files are stored into diag directory in the zip file.
Windows S-TAP Must Gather executes some Windows commands to get environment information from the DB server where the Windows S-TAP is installed. It'll generate the following files:
Windows S-TAP Must Gather V2 started storing the real copy of Guard_Tap.ini file.
The file is stored under ini directory in the zip file.
Windows S-TAP generates driver log files and stores them into %WINSTAP%Logs directory, where %WINSTAP% is the Windows S-TAP installed directory, and the default is "C:\Program Files\IBM\Windows S-TAP\Logs".These are typical driver log files generated by Windows S-TAP.
These files are stored into the root directory in the zip file.
Windows S-TAP generates startup log at the same directory as the driver logs exist. It's a brief log that's collected only during starting up Windows S-TAP. When Windows S-TAP debug log is enabled, this file won't be created because it's a subset of debug log.
, where %HOSTNAME% is the host name of the database server, and %TIMESTAMP% is the timestamp of the file created with YY-MM-DD_hhmmss format.Windows S-TAP Must Gather also copies these files to the root directory of the output zip file.
When you run Windows S-TAP Must Gather from GUI, you'll find some additional files in the must gather zip file.
Windows S-TAP Must Gather also copies these files to the root directory of the output zip file.[NOTE] When you enable Windows S-TAP debug log by editing guard_tap.ini and restart Windows S-TAP, the debug log will be generated at %WINSTAP%\Bin\StapBuffer directory. This file won't be included in Windows S-TAP Must Gather because the file could be huge. You must send the file separately from Windows S-TAP Must Gather if it's requested by Technical Support.
Windows S-TAP and all Guardium Windows agents generate installer log at the root directory of the SystemDrive drive (e.g. C:\) when it's installed. These are example installer log files.
Installer log is created every time the product is installed. If the installer log exist, it'll be renamed to the original name plus timestamp (e.g. IBM Windows S-TAP0517202232.ctl)Windows S-TAP Must Gather copies all these files to the install directory of the output zip file.
If Windows GAM is installed in the database server, Windows S-TAP Must Gather will check if the following files exist under the GAM installed directory.
Note that GAM was called Guardium Resource Monitor when this feature was first released, so the file names remain using "resmon". The resmon.ini file exists by default, and resmon_log.txt is created at the first time when GAM service starts.Windows S-TAP Must Gather copies all these files to the Guardium Agent Monitor directory of the output zip file.
If Windows GIM is installed in the database server, Windows S-TAP Must Gather copies the following files to the Guardium Installation Manager directory of the output zip file.
If Windows FAM is installed in the database server, Windows S-TAP Must Gather copies the following files to the Windows Fam Monitor directory of the output zip file.
If Windows CAS is installed in the database server, Windows S-TAP Must Gather copies all these files to the CAS directory of the output zip file.
My next blog post will pick up some major diagnostic files and share troubleshooting examples.
Copy
By
SATOSHI KAWASE
posted