There are 2 scenarios for obtaining HANA checks in an EWA.
- Scenario 1: EWA for an ABAP system with a HANA database.
- Scenario 2: EWA for a standalone HANA database system or a non-ABAP system with a HANA database.
For more information about the prerequisites for each of these scenarios, refer to:
SAP Note 1958910 - EarlyWatch Alert For HANA Database.
Before You Start
- A standalone HANA database can be identified by SAP Product displayed on the EWA cover page: e.g. "SAP HANA PLATFORM EDITION 2.0"
- It is not necessary to generate an EWA report for a standalone HANA database if it is already associated with an ABAP system (e.g. it is the main database for an ABAP system). HANA checks are automatically included in ABAP EWA reports, so it would be redundant to have a separate EWA report for only the HANA database checks.
Missing HANA Checks in the EWA
How do you verify if there are missing HANA checks in the EWA?
- A common problem is that the overall rating of the EWA report is missing or grey due to missing HANA DB content.
- Check the Service Data Quality chapter in the EWA for missing HANA DB data alerts.
- You can check the alert's impact on the the overall rating of the report by verifying its priority level.
- Compare the content in the current EWA report to a previous week's report.
What should you do to ensure that all HANA DB data is collected in the EWA?
- Refer to SAP Note 1958910 - EarlyWatch Alert For HANA Database.
- Ensure all the steps have been followed such as the minimum software packages.
- This step would also include applying the latest version of the note if you are using a specific version of ST-SER 701_2010_1 (i.e. support packages: SAPKITLOSN or SAPKITLOSM).
- Refer to the "Service Data Quality" section in the EWA for specific instructions and SAP Notes to resolve the data collection issue.
- To have the latest data collectors available, it is recommended to apply from time to time the latest version of SAP Note 1985402 and 2344673 on the managed system (if the managed system is ABAP) and on the Solution Manager (if the managed system is non-ABAP).
- If SAP Note 1985402 is unavailable, refer to the workaround in SAP KBA 2536044.
- If SAP Note 1985402 and 2344673 do not resolve the missing data, ensure ST-PI is updated to the latest version. Check ST13 - RTCCTOOL if ST-PI is outdated.
- For missing content related to SAP Note 2344673 such as missing SQL chapters in the EWA report:
• The chapters might be missing because of an issue in data collection. The function named HDB_COLL_MULTI_STMT ends in a time limit exceeded error.
• A service plug-in upgrade is required for ST-PI 740 SP11 (or ST-PI 2008_1_700 SP 21) before implementing the correction described in the note, see bullet point 14 in the note.
• A workaround involves increasing timeout parameter rdisp/max_wprun_time and rdisp/scheduler/prio_normal/max_runtime (in case they are not set to 0). Parameters are explained in SAP Note 25528 and can be adjusted in transaction RZ11.
- Check that the SOLMAN_SETUP - Managed System Configuration - SID - Configure System - Full Configuration Incl. Service Delivery/EWA is complete without any RED alerts.
- Ensure that the connection test in DBACOCKPIT for the specific SID connection is successful. This connection must be defined in DBCO.
- Check in transaction LMDB and select Technical System type HANA.
- While in LMDB, check that the attribute 'Remote Database Connection' has the value of the remote database connection name. This information is the one listed in DBACOCKPIT for this specific system.
- It is important that the value for this attribute is not typed. It must be selected from the value list / drop down menu - see yellow highlight in below screenshot to get to the value list. The value list is based on the database connections configured in DBCO.
- Check the SDCCN log of the Managed System (or in case of a HANA standalone system, use Solution Manager SDCCN) by running t-code SDCCN - 'Done' tab and open the corresponding log for the HANA EWA session.
In the "Done" tab of SDCCN, click on the truck icon of the session. In the download tree of SDCCN, look for the "DBREMOTE" node.
Please note: this step is only relevant to Scenario 2. Please review the scenarios listed at the top of this page.
If you cannot find the information for "DBREMOTE", review and apply the following SAP Note(s) depending on the ST-PI or ST version you are using:
- ST-PI: 2008_1_700, 2008_1_710, or 740
SAP Note 2281878 - HANA EWA Session is missing HANA Database information Part I for ST-PI.
- ST 710: Solution Manager 7.1
SAP Note 2283516 - HANA EWA Session is missing HANA Database information Part II for ST 710.
ST 720: Solution Manager 7.2
Refer to SAP Note 2445371 - DBREMOTE is missing in the download of SDCCN
- ST-PI: 2008_1_700, 2008_1_710, or 740
Issues with the EWA Content
ABAP EWA report is showing unwanted HANA database data
- An unrelated HANA database appears in an ABAP EWA Report
- Multiple HANA databases (in some cases 40+) are shown in one EWA report.
How many databases do we typically see in an EWA report?
A typical EWA report will include checks for the main database. Please note that it is not possible to remove checks about the main database from a system's EWA report.
What should I do if I have multiple HANA databases reported in the EWA report?
- Check if the additional HANA database reported in the EWA is relevant to the system. (E.g. Does it make sense to include checks about this secondary HANA database in this EWA report?)
- If the additional HANA database is irrelevant to the system or not desired in the EWA, please follow the instructions below for steps to remove content about the secondary HANA database from the EWA report.
How do I remove content about an unrelated HANA database from an ABAP EWA report?
- Please note: The following steps must be performed in the ABAP system and not in Solution Manager. This is because data collection occurs on the ABAP managed system before it is transferred to Solution Manager.
- You cannot remove HANA database data in the EWA if it is the main database of your managed system. You can only remove HANA database data in the EWA for 'Side-By-Side' HANA Databases:
i.e. SLT (component DMIS) is used, or HANA databases that appear in the
EWA Landscape chapter > Products and Components in current Landscape > under "Other Main Instances".
- The EWA will contain data from additional HANA databases if database connections to those remote systems are defined in transaction DBCO. Check in DBCO if you have database connections to multiple HANA database systems.
- If you don't want to see the database information about a secondary HANA system in the EWA, check in transaction DBACOCKPIT for corresponding entries to the database connections defined in DBCO.
- If the entries do not exist in DBACOCKPIT, you must create at least one of the non default database entry. It is not necessary to create entries for all the unwanted databases.
- On the managed system, create a DBACOCKPIT entry for one of the system that is not the default HANA database. That is, create an entry with a valid connection name. Then enter NON_EWA_ in the description field.
Based on the coding as outlined below, the NON_EWA_ entry is read for non-default HANA databases.
TRY. CLEAR ls_hana_id. SELECT dbcname FROM db6navsyst INTO ls_hana_id-conn WHERE dbsys = 'HDB' AND ('DESCRIPTION LIKE ''NON_EWA_%'' ') AND dbcname <> space. "Field 'DESCRIPTION' only " available for higher SP Levels!! * APPEND ls_hana_id TO pt_hana_id. ENDSELECT.
If you are not familiar with DBACOCKPIT, you can refer to:
SAP KBA 2222220 - FAQ: SAP HANA DBACOCKPIT
→ Section: How can I configure a remote SAP HANA database in DBACOCKPIT?
...or open an incident in HAN-DB for more help with DBACOCKPIT.
If the entries already exist in DBACOCKPIT for a non default HANA database, simply highlight the entry and click "Change" or double-click on the entry, write in the description field "NON_EWA_", and save.
d. Then set the actual HANA database entry as 'DEFAULT' in DBACOCKPIT.
- Most configuration changes are reflected in the next automated EWA report on Monday, which is why we recommend waiting for the next scheduled EWA to see the changes. You can also try the steps below on the managed system:
Use t-code SE37 and input /SDF/COLL_MULTI_HANA_DWL and then enter M_DATABASE in the field MOD_ID1. Check if multiple entries are still shown.
You can try running an ad-hoc EWA report to see if the HANA database data is excluded from the report, otherwise wait for the next scheduled EWA:
SAP HANA database: No Log Backups are scheduled. Non successful or not scheduled Data Backups have been detected.
Refer to section 'Missing HANA Checks in the EWA' at the top of this WIKI page to ensure all the mandatory configuration steps are followed.
Ensure the parameters outlined in SAP Note 1642148 are implemented.
Verify in HANA Studio that data and log backup are successful.
Run SE37 on the ABAP system and verify if /SDF/OCS_GET_STAT_INFO could be called. Verify if SAP Note 2271942 is applicable for the ABAP system. If required, implement the note.
See also: 2661900 - EWA - Log and Data Backup
Incorrect HANA database client version in EWA report.
- To resolve this issue, refer to 2540985.
- Refer also to 2386699 - Wrong HANA Client version on Application server.
- EWA is Missing "SAP HANA I/O Performance Counters" - Refer to 2653595
- EWA - Memory Allocation of Tables - Refer to 2727687
- EarlyWatch Alert with HANA - Download Overview and Requirements - Refer to 2517313
- Red EarlyWatch Alert (EWA) for S4HANA/HANA with missing HANA critical version and HotNews - Refer to 2692722
Monitoring data from your SAP HANA database could not be read because the related download function module of your ST-PI software component is not up to date
- Follow the steps above from the section - What should you do to ensure that all HANA DB data is collected in the EWA?
- Ensure that LMDB has the remote database entry.
- Apply the latest version of SAP Note 1985402.
- Apply the DBCON recommendation according to SAP Note 1892593.
- Check in SM21 of Solution Manager (for standalone HANA database) or SM21 of the relevant ABAP system for authorization errors. Look for errors around the time that SDCCN EWA task runs which is every Monday morning at 4:00am. Filter by the SDCCN user. This is the user that runs job /BDL/TASK_PROCESSOR. To find the user, open this job in SM37 and click on the option 'Step' to find the actual user.
Example of authorization error from transaction SM21
Database error 258 at EXE
> insufficient privilege: Not authorized
Refer to SAP note 2272874 and add the authorization to the SDCCN user that is running job /BDL/TASK_PROCESSOR
HANA 1511 or 1610 or 1611 EWA is not shown in System Monitoring area of the Work Center.
This is a known issue in ST 7.1 SP14 and will be resolved in 7.1 SP15. For the workaround, refer to 2341945.