rs_dump_stats

Extracts Replication Server statistics collected in the RSSD by admin stats to a comma-delimited format.

Syntax

rs_dump_stats [‘comment’]

Parameters

comment – is an optional description of the statistics being displayed. It appears on the first line of the output file.

Examples

Example 1 – Extracts Replication Server statistics with comment “Stats from 01/31/2006.”

rs_dump_stats ‘Stats from 01/31/2006’

The columns of counter data are, in order:

The timestamp of the observation period
The number of observations made of the counter during the observation period
The total of observed values
The last observed value
The maximum observed value

Depending on the counter category (see the Replication Server Administration Guide Volume 2 > Performance Tuning > Monitor Performance Using Counters for a description of counter categories), there may be close correlation between the number of observations and total observations, and between the last and maximum observed values. For example, an observer counter simply counts the number of observations of an event—such as the number of times a message is read from a queue. For an observer counter, the number of observations and the total of observed values are the same. Similarly, the last and maximum observed values are both 1 (unless no messages were read in the observation period, in which case both values would be 0).

Note: Comments to the right of the output are included to explain the example. They are not part of the rs_dump_stats output.

Comment: Stats from 01/31/2006	== Provided label
Oct 17 2005  3:13:47:716PM	== End of the first observation period
Oct 17 2005  3:14:24:730PM	== End of the last observation period
2	== Number of observation periods
0	== Number of minutes in each obs period.
0 if less than one.(Calculated as the number of minutes between the first
and last obs period, divided by the number of observations.)
16384                         == Number of bytes in an SQM Block to
                              aid calculations
64                            == Number of blocks in an SQM Segment
                              to aid calculations
CM                            == Module Name. See rs_help_counter
                              for a complete list.
13                            == Instance ID. See admin stats for an
                              explanation.
-1                            == Inst Val/Mod Type. Further instance
                              qualification when needed.
dCM                           == Instance description.
CM: Outbound database connection
requests                      == Counter description.
CMOBDBReq                     == Counter display name.
13003           , , 13,  -1   == Counter ID and instance qualifying
                              information.
Oct 17 2005  3:13:47:716PM,  52,  
52,  1,  1                    == Counter data. One row output for
                              each observation period. See below for
                              explanation.
Oct 17 2005  3:14:24:730PM,  42,  
42,  1,  1
ENDOFDATA                     == End of output for the previous
                              counter
CM: Outbound non-database 
connection requests           == Start of output for the next counter
CMOBNonDBReq
13004           , , 13,  -1
Oct 17 2005  3:13:47:716PM,  2,  2,  1,  1
Oct 17 2005  3:14:24:730PM,  2,  2,  1,  1
ENDOFDATA
.
.
.
CM: Time spent closing an ob fadeout conn
CMOBConnFadeOutClose
13019           , , 13,  -1
Oct 17 2005  3:13:47:716PM,  0,  0,  0,  0
Oct 17 2005  3:14:24:730PM,  2,  6,  2,  4
ENDOFDATA
DIST                          == Start of output for the next
                              module/instance
102
-1
DIST, 102 pds03.tpcc
DIST: Commands read from inbound queue
CmdsRead
30000           , , 102,  -1
Oct 17 2005  3:13:47:716PM,  1,  1,  1,  1
Oct 17 2005  3:14:24:730PM,  1,  1,  1,  1
ENDOFDATA
.
.
.
DSIEXEC: Number of 'message' results
DSIEResMsg
57127           , , 103,  7
Oct 17 2005  3:13:47:716PM,  1,  1,  1,  1
Oct 17 2005  3:14:24:730PM,  1,  1,  1,  1
ENDOFDATA
(return status = 0)            == End of output

Usage

You can capture the output of rs_dump_stats in a text file that can then be analyzed in a spread sheet or other analysis tool.
If the text file containing the output of rs_dump_stats is too large to load in to the analysis tool, you can split the file into multiple files.
- Each new file must contain the first seven rows and the last row of the original file.
- Between the first seven rows and the last row of each new file, insert all rows associated with a given module instance.
Depending on the analysis tool, it is usually unnecessary to include all instances of one module in the same file.
rs_dump_stats does not remove or alter statistics saved in the RSSD.
rs_dump_stats lists counters with no observations, but does not display counter data rows for them. rs_dump_stats displays counter data rows for all counters with at least one observation during the sample period.