Best Practices when using Supp_Diag tool.

Document ID : KB000009572
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

When running Supp_diag, a concern that may arise is the size of the output CAZ file.
It is not uncommon to have a substantially large .CAZ file generated, often 2-4 GB, with larger files topping out at 6 GB+.

Environment:
This is applicable to SDM r12.x, r14.x and r17.x
Instructions:

There are a few items one can examine prior to running supp_diag:

1.      Check NX_ROOT\bopcfg\www\CATALINA_BASE\logs folder.
Check for any older log files which may be moved over to another folder, or even deleted. 

2.      Check NX_ROOT\log folder for any of the following:
- older trace or bop_logging generated files
- older visualizer*.log files
- performance log files
- Archive/purge log files
- Any folder that could have been created (e.g: backup, bkp, etc)

3.      Check for any NX_ROOT\site\mods backups.
Often, backups of the site/mods directory are prepared locally and retained within the operating site/mods directory itself.  While it is not best practice to retain copies of site/mods, one should keep in mind that supp_diag will collect these backup directories contained within the main site/mods directory, along with the main site/mods directory itself.

Additional Information:

IMPORTANT: Before deleting any files, consult CA Support to confirm those won't be necessary for the case troubleshooting.  One action to consider running is to cd to the SDM install directory, and running dir /s > listing.dat and send the resultant listing.dat to give an overall picture of the SD install directory contents.