Content Manager Server Log Utilities for Performance-Related Troubleshooting and Analysis
Published 11 August 2006
Authors: Wei-Dong Zhu
This technote describes the utilities available to analyze Content Manager system logs for performance-related troubleshooting and analysis.
To help you troubleshoot performance-related issues associated with Content Manager system operation, we present four utilities (originally created by the Content Manager development team) to analyze the Content Manager system log files. These utilities include:
These tools are executable files that you can run from a Windows workstation. For some of the tools, we also provide Java and shell script versions including source code that you can run or modify based on your system requirements. To obtain these utilities including the source code, click here and download the SG246949.zip file.
ICMLogSplit splits a Content Manager server log file (by default, it is icmserver.log) into separate files for each user session. It finds the user information field in the log entries and uses this information as the file name.
ICMLSPerf analyzes the Content Manager server log file and summarizes the stored procedures execution information, including stored procedure name, count, Library Server time elapsed within the stored procedure, and application time elapsed within the stored procedure. This information is useful in a single-user environment.
ICMLogDeltaTime reports the elapsed time between the trace records in a Content Manager server log file. The best way to use this is on a server log containing only performance data (tracelevel=-8) or use grep to find records containing msec.
ICMEventTable uses an event monitor log file to produce an output file and a summary file.
The output file has data related to the buffer pool read on temporary data, indexes, temporary indexes, type of read, operation done, return code, and statement being run.
The summary file provides information such as the package accessed, section, count, total time to run the SQL, average time to run the SQL, total Content Manager time, average Content Manager time, maximum reads, average number of rows read, written, and fetched, average buffer pool reads, and the statement that was run. It also provides summary details such as the elapsed time of the test, number of stored procedure calls, SQL statements run, prepare statements, SQL without CLOSE and PREP, transaction time, lock wait time, set statements, commits, and rollbacks.
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.
Follow IBM Redbooks
Follow IBM Redbooks