Did this article resolve your question/issue?



Script for gathering ONLY database information (not OS information) on Unix.


TitleScript for gathering ONLY database information (not OS information) on Unix.
URL Namescript-for-gathering-only-database-information-not-os-information-on-unix
Article Number000181138
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x, 11.x
Question/Problem Description
Script for gathering ONLY database information (not OS information) on Unix.
How to gather performance analysis
Improved Gather Script for UNIX
What is the gather script?
What is the promon gather script for UNIX?
How to collect performance information from a Progress / OpenEdge database.
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
The attached script can be used to gather database information for performance analysis data gathering.  Without the OS performance data collection the information from the gather output will not be sufficient to identify performance problems cause by the OS or hardware.
  • This script should only be used with a Enterprise database license installed.
  • Before running the script set the DLC variable or execute the script in a proenv environment which sets DLC automatically.
  • This script is not intended to be used to collect stack trace information.  The lines which would normally collect stack trace information have been removed as has any command which would normally collect OS performance metric information.
When running as non-root account, remove the following lines:
if [ $me != "root" ]
echo "You are not logged in as root."
echo "Root permissions are needed to run "
echo "some of the utilities in this script."
This gather script is provided 'as is', but is essentially for trouble-shooting online situations when they're happening. Typically hang situations.
Running running latch statistics in production can be harmful to database performance and stability, something you need to be aware of.
If you really need this information, then Ideally you want to seperate the "Activity: Latch Counts" with very short sampling interval.

The Latch Statistics applies to : (line 303 - 328)

echo 4 >>gatherin.txt #Administrative Functions
echo 4 >>gatherin.txt #Adjust Latch Options
echo 2 >>gatherin.txt #Enable latch activity collection
echo 3 >>gatherin.txt #Enable latch timing collection
.... <inclusive>
echo 4 >>gatherin.txt #Administrative Functions
echo 4 >>gatherin.txt #Adjust Latch Options
echo 2 >>gatherin.txt #Disable latch activity collection
echo 3 >>gatherin.txt #Disable latch timing collection
When utilizing this script for troubleshooting performance problems with the 'perf' parameter, the script should be executed twice, once when the database performance is ideal and again when the performance is perceived as not acceptable. The output from each execution can be used for comparison. 

References to Other Documentation:

Progress Article(s):
000076189, How to run a promon gather script on Unix with Workgroup Database license?
000045180, Script to gather system performance information on Unix (without collecting promon database output). 
000011030, How to run a promon gather script on Windows?   
000015928, Cannot get the promon gather script on Linux to run without errors.   
000051233, How to run a promon gather script on Windows with Workgroup Database license?   
000012342, How to run a PROMON restricted option for dumping MUX latches.
Last Modified Date4/24/2017 1:09 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.