Show TOC

Function documentationUsing the Reporting DSOs Reorganization Program

 

In Interactive Reporting, history data of monitored metrics are written into the SAP Solution Manager Business Warehouse. The data flow in BW is that the data is first aggregated and written into DataStore objects (DSOs), and then moved from the DSOs into InfoCubes, by jobs. For further information, see Passing and Saving MAI Data in Business Warehouse.

Monitoring and Alerting Infrastructure (MAI) metrics are first written into the two following DSOs:

  • 0CCMBUFF contains the aggregate monitoring data down to hourly values. It is written into InfoCubes by the hourly job CCMS_CPH_RAW_DATA_UPDATE.

  • 0CCMAGGR contains the aggregate monitoring data from daily values. It is written into InfoCubes by the daily job CCMS_CPH_AGGR_DATA_UPDATE.

The DSOs should contain the latest aggregate for each metri. The above jobs delete obsolete aggregates from the DSOs, as well as providing data to the InfoCubes. The agorithms are optimized for performance, not the complete deletion of obsolete data records under all conditions. It is possible, under certain conditions, that obsolete data records could build up in the DSOs, leading to poorer performance and greater memory usage. Such a build-up of obsolete data records could occur, for example, for the following reasons:

  • The jobs to copy the aggregates from the DSOs and the InfoCubes do not run reliably.

  • The data provision of the metrics is unreliable.

  • A lot of once-only metrics are copied into BW, i.e. measured values which are incorrectly interpreted as independent metrics, not as the chronological development of a metric.

In such cases, use this program to reorganize the DSOs, i.e. to delete obsolete data records. The program can calculate how many obsolte data records the DSOs contain, to decide whether they should be reorganized.

If you perform a reorganization for some or all aggregates in this program, the data records for all metrics, up to the latest aggregate, are written into the InfoCubes, and all aggregates in the DSOs whose configured lifetime has been exceeded, are deleted.

Activities

Call Program

To reorganize reporting DSOs, call the transaction MAI_TOOLS. Go to expert mode, and, in the Analysis tab, choose Reorganization of Reporting DSOs.

Call data in selection screen

When you call the program, a selection screen appears. If you choose (Execute) in this screen, without making any other entries, the DSOs for all saved aggregates are reorganized. This is usually the appropriate setting.

You can restrict the aggregates which are reorganized. See the basic principles of aggregation, under Aggregation.

Note Note

Aggregation is part of the Central Performance History documentation, one of the predecessor products of interactive reporting. The principles of aggregation, especially its methods (reduction of resolution and combination of intervals) have not changed.

End of the note.

To do so, proceed as follows:

  1. In the field Date Granularity specify whether to reorganize daily, weekly or monthly values.

  2. In the field Time Granularity specify whether to reorganize values in daily, weekly or monthly resolution.

  3. The program outputs a DSO reorganization log (see DSO Reorganization Log below). If you want to check the DSOs for obsolete data records, but not perform the reorganization, set the Only Analyze flag.

DSO Reorganization Log

The following data is output for each granularity:

Display

Note

Number of Metrics

There cannot be less data records than metrics in the DSOs, but this difference should be as small as possible. Ideally, all data records except the latest one are deleted for all metrics, every time this job runs, and the number of metrics is the same as the number of data records.

In practice, there are usually more data records than metrics, depending on when the analysis is performed; a factor of 2 is unproblematic, but 4 clearly indicates problems.

Number of data records

Metrics with the timestamp of the last measurement in the current period

Obsolete metrics arise in the DSOs mainly in two situations:

  • The metric data provision is unreliable, so the newest aggregate of the metric cann aleady be old.

  • One-off metrics are written into BW.

  • The jobs to copy the aggregates from the DSOs and the InfoCubes do not run reliably.

Set the lifetime of the aggregates in the SAP Solution Manager configuration (transaction SOLMAN_SETUP), in Start of the navigation path Technical Monitoring Next navigation step Configure Infrastructure Next navigation step Housekeeping End of the navigation path.

Metrics with the timestamp of the last measurement in a previous period (not obsolete, still within the lifetime of the aggregate)

Obsolete metrics, which are older than the lifetime of the aggregate

Obsolete metrics, which are considerably older than the lifetime of the aggregate

Number of metrics with at least 50 data records

These values determine whether metrics with more than one or two data records in the DSOs occur often or seldom.

Number of metrics with at least 10 data records

Number of metrics with at least 5 data records

Number of metrics with at least 2 data records

Number of metrics with at least one data record

Number of metrics and data records deleted, or to be deleted (in Only Analyze mode).

Number of metrics and data records moved into InfoCubes or to be moved (in Only Analyze) mode.

Number of invalid metrics or data records, with duplicate keys

If there are metrics with duplicate keys, there is a technical problem. In this case, create a message in component SV-SMP-MON-REP.