IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Performance tuning > Tivoli Data Warehouse > Summarization and Pruning Agent
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Enable more detailed trace in log files
The Summarization and Pruning Agent Java internal trace files contain diagnostic messages showing the number of rows read and pruned for each attribute group and agent. The names of these files are of the form hostname_sy_java_timestamp-n.log. For large environments, these trace files might be overwritten during a single Summarization and Pruning Agent processing cycle, and some of the diagnostic information may be lost.
By default, the Java-based internal trace wraps at 5 files, and each file contains 300000 lines. To change the default values, you can specify Java runtime parameters in the Summarization and Pruning Agent configuration file (KSYENV on Windows, sy.ini on UNIX or Linux):
KSZ_JAVA_ARGS=-Dibm.tdw.maxNumberDetailTraceFiles=A -Dibm.tdw.maxLinesForDetailTraceFile=Bwhere:
Consider increasing these log parameters so that you have a few days worth of data in the logs for diagnostic purposes.
- A
- Specifies the maximum number of Java-based internal trace files that can exist at any one time for a single launch.
- B
- Specifies the maximum number of lines per Java-based internal trace file.
Parent topic:
Summarization and Pruning Agent