This page contains some hints for troubleshooting when for example some dashboards or views are empty.
As starting point you should classify the problem:
Most pre-defined dashboards per system type are populated with metrics from the Monitoring and Alerting infrastructure that is also providing the content for System Monitoring. As a result, if any metrics do not report data, the first check is to verify if system monitoring is working correctly and if metrics in System Monitoring report data. If System Monitoring is not working correctly, please open a support ticket with component SV-FRN-APP-SYM.
Starting with FRUN 3.0 Self Monitoring alerts are available for RCA Capabilities to inform you when for a capability data is expected but not available.
With report RCA_DEACTIVATE_CAPABILITIES you can do some mass changes without disabling/enabling the capability for each system separately.
You can enter in the selection fields several capabilities (wildcard * is possible) and/or limit the execution to LMDBIDs.
These options are available
In case you have multiple systems and capabilities to be changed the report should be executed in background. To avoid that too many parallel requests are executed the time between two executions can be configured (default 1s).
In general you can check table RCA_INBOUND_LOG in FRUN via SE16, MESSAGE_TYPE="E" will filter on errors and and the date ( field UTC_DATE) . Here you can see errors of data that are sent to FRUN. When changing the user parameters in SE16 (Menu: Settings-> User Parameters -> ALV Grid Display) you can see the detailed error messages and can download the table.
However there might be already problems in collecting data either in the agent application, in the managed system or on the way.
HANA Metrics are collected via an operation of the SAP Hostagent. Check in Agent Administration for the HANA system if the collectors are running:
ABAP work process samples (/SDF/SMON) are collected via a RFC from the SDA usually with user SDAGENT. Check in Agent Administration for the ABAP system if the collector is running:
If the collector is missing in the collector framework there are several reasons:
Any HANA statement details view in System Analysis shows the statement text “Statement not available” or nothing.
Ad-Hoc SQL views trigger SQL statements as ad hoc calls directly towards the SAP Host Agent on the managed HANA system. The statements are delivered as part of the SAP Host Agent.
For any errors executing Ad-Hoc SQL statements:
This error can occur if https is used to communicate from Focused Run to the SAP Host Agent on the managed HANA system and authentication takes place via X509 cerificates. Check the SM59 destination to find out.
If this configuration applies you have to adjust the profile of the SAP Host Agent an maintain the subject of the SSL client from transaction STRUST in FRUN.
1. In transaction STRUST select "SSL Client (Standard)". For the "own certificate" copy the subject line, e.g.
CN=SID.wdf.sap.corp, OU=SID SSL client SSL Client Standard, O=SAP, C=DE
2. In the SHA profile (/usr/sap/hostctrl/exe/host_profile) add a line line this:
service/sso_admin_user_0 = CN=SID.wdf.sap.corp, OU=SID SSL client SSL Client Standard, O=SAP, C=DE
(0 is the index for the entry. If you have multiple increase to 1 etc.)
The page ABAP Performance does not display any data which could have multiple reasons: