(DI-2202) Upgrade check report

Owned by SNP
Feb 08, 2022
4 min read

The upgrade check report executes the XPRA upgrade checks immediately after importing the CrystalBridge® Monitoring transport request into the SAP system. This report checks for the software inconsistencies which might affect the functionality of the CrystalBridge® Monitoring. If any inconsistencies are found, this report consolidates them into a consistent state (for example, there might be some new features that might use different structures of DB tables and this report consolidates the data of the old DB structure into the new structure).

In general, the XPRA check is a report which updates, controls, and fixes master data, transactional data, and customizing. It contains the following independent checks.

Table consistency check for Detail table fields

It checks whether the new table with the detail table version for each system is consistent with the table of all detail table versions. If the new table is empty, the check will consolidate it with correct entries. Otherwise, it will check the creation and last change timestamp for each entry and fix them, so they are in the correct time order. Each older version of a detail table must have also an older time of creation. If this check finds an older detail table version with a creation time newer than some other entry (higher version of this table), the creation time of the older version is set to one hour earlier before the creation of the newer version of this table.

Deleting BTC configuration

This check deletes all obsolete BTC properties from all relevant database tables.

Update the system status

The check goes through all collector jobs and verifies, whether there is some job scheduled for a collector job. When the collector job is not running, the status of the affected system is changed to Stop in the System status table.

Correction of system definition

Checks the IP address of all monitored SAP systems with valid RFC destination. If the IP address doesn't match the standard pattern (4 blocks of max. three-digit numbers separated by a dot), it tries to derive some information from a satellite system by the RFC call and fix the entry in the System definition table.

Update the system type

Checks all system definitions whether it contains any unspecified system type. This check considers all system definitions with unspecified system types as SAP System and updates them in their system definition.

Update of the collector job status

Checks the statuses of all collector jobs in a relevant table and marks them as 'Running', 'Stopped' or 'Paused'.

KPI definition update

This check fills columns 'chart lower limit mode' or 'chart upper limit mode' in the KPI definition table. If the 'chart lower limit mode' or 'chart upper limit mode' are not specified, the value in the corresponding column will be set to 'AUTO' (Limit will be calculated from min/max values). Also, the KPI chart type is checked. When the chart type isn't defined for a KPI, the chart type is set to 'LINE' as default.

Update Alert definitions for a KPI

This check fills in information about a KPI assigned to an alert defined in the Alert definition table. All redundant alerts with unassigned KPIs are deleted.

Update an empty Monitoring area

In the case the system type is not specified, the check fills a system type for each KPI defined in the KPI definition table. If the technical name of a KPI starts with 'Z', 'Y' or 'X', the system type is set to 'CUST', otherwise it is set to 'OLD'.

Check of multiple KPIs assigned to one Alert

One alert must be defined only for one KPI. In the case one alert is defined for multiple KPIs, the check finds this alert and creates copies of it, and assigns the newly created alerts to KPIs which were originally not correctly assigned to the one alert. The name of the newly created alert is created as prefix 'X' + name of the original alert + '_order number of the erroneous KPI'.

Manual execution of Upgrade check report

Go to the transaction SE38 and execute the report /DVD/MON_UPGRADE_CHECKS.

If you run the report in Test mode (the first checkbox is selected), no changes are done on the DB level (no data will be updated in DB tables).

You might choose, how the messages will be displayed when this report is finished.

  • Write output (when importing)

    • Displays the messages into spool output. The same option is used, when importing transport requests into the SAP system.

      Write output

  • Log output

    • Displays the messages in logs output.

      Logs output

    • Saves the messages into logs and you might check these messages later on in transaction SLG1:

      • Object: /DVD/MON

      • Sub-object: /DVD/MON_CHECKS

      • External ID: Name of the check (you might keep it empty to display all checks)