SAP HANA is a powerful in-memory database that requires continuous care and maintenance to ensure optimal performance and stability. In this article, SAP HANA specialists will learn how to effectively use HANA management tools to monitor and administer their databases. The SAP HANA maintenance strategy is based on incremental, non-disruptive innovation updates. New features are introduced once a year, each time a new SAP HANA SPS is released. This usually happens at the beginning of April.
We are happy to support you in the following areas:
Hardware Checks
| SAP-certified hardware for SAP HANA | The certification confirms that a product has successfully passed the SAP certification procedures. However, it is the responsibility of the vendor to ensure that the product functions correctly. At the time of purchase, the hardware must have a valid SAP HANA hardware certification. This certification ensures that the hardware fulfills the required performance characteristics for the operation of SAP HANA. |
| Hardware Configuration Check Tool (HWCCT) | The HWCCT provides a variety of tests and reports to ensure that the hardware meets the minimum performance requirements for SAP HANA operation. SAP strongly recommends using HWCCT as part of a HANA go-live check. The tool checks, among other things: Hardware configuration validation: checks memory and processor configurations. Operating system settings: Validates Linux kernel settings and supported Linux distributions. Data throughput and latency times: Measures data transfer rates and latency between the SAP HANA nodes and external storage systems. Network bandwidth: Checks the available bandwidth between the nodes of a multi-node system. LPAR settings on IBM Power servers: Checks the settings for logical partitions. Important resources: SAP HANA Hardware Directory: SAP HANA Hardware Directory HWCCT Patch Note: SAP Note 2161344 HANA Hardware and Cloud Measurement Tools: SAP Note 2493172 |
| HANA Sizing Report | Accurate sizing is crucial to ensure that the SAP HANA database has sufficient memory and resources to process the workloads efficiently. Sizing is done either via the SAP HANA Quick Sizer or through specific sizing reports during migrations of SAP NetWeaver systems. CPU and memory sizing The sizing of large or complex systems should be carried out by an SAP sizing expert. Various tools are available for this purpose, which provide separate results for CPU and RAM. Customers share these results with their hardware partner to determine the optimal hardware components. |
| Virtualization | SSAP HANA supports operation in virtualized environments, including VMware and other hypervisor technologies. With Multi-Tenant Database Containers (MDC), multiple workloads can be run separately within a single HANA installation. MCOS and MCOD deployment options are also available to realize similar multi-tenant environments. Multi-Tenant Database Containers: SAP Note 2096000 MCOS und MCOD: SAP Note 1681092 |
| Network | In SAP HANA scale-out environments, the individual nodes and services must communicate with each other for different purposes, which is also necessary for single-node systems. The default configurations of Linux and HANA may not be optimal for internal HANA communication, so customization of the relevant parameters is recommended to ensure smooth and error-free communication. Especially for large scale-out systems or multi-database container installations with many client databases, the network settings of Linux and SAP HANA should be optimized to achieve better performance and stability. |
Operation Software Checks
SLES | Wenn Sie SAP HANA auf SLES 15 oder SLES für SAP Applications 15 betreiben, möchten Sie optimale Linux-Einstellungen konfigurieren. SAP HANA umfasst sowohl die Versionen 1.0 als auch 2.0 und muss gemäß SAP Note 1944799 installiert und konfiguriert werden. Die in dieser SAP Note aufgeführten Empfehlungen gelten für alle von SAP HANA unterstützten Service Packs von SLES 15, und es wird empfohlen, stets die neuesten Kernel-Updates und Patches von SUSE zu verwenden, sofern keine spezifischen Gründe dagegen sprechen. |
| RHEL | “RHEL” als Synonym für “Red Hat Enterprise Linux for SAP HANA” und “Red Hat Enterprise Linux for SAP Solutions” verwendet, während “SLES” für “SUSE Linux Enterprise Server” und “SUSE Linux Enterprise Server for SAP Applications” steht. Die angehängte PDF-Datei listet die unterstützten Kombinationen von RHEL-Minor-Releases und SLES-Support-Paketen mit den verschiedenen SAP HANA-Versionen auf, wobei nicht aufgeführte Kombinationen als nicht unterstützt gelten. Es wird empfohlen, die SAP Product Availability Matrix zu konsultieren, da andere SAP-Softwarelösungen möglicherweise strengere Anforderungen an die Betriebssystemversionen haben und zusätzliche Einschränkungen definieren können. |
| OS Lifecycle | SUSE Linux Enterprise Server: SUSE Lifecycle Red Hat Enterprise Linux: Red Hat Lifecycle |
HANA Checks
| Early Watch Alert | The Early Watch Alert offers comprehensive monitoring of the HANA database and provides early indications of potential problems and optimization potential. |
| Update Path | SAP HANA release strategy. When updating SAP HANA, the compatibility and known problems of the target revision must be checked. Specific SAP Notes are available for this purpose, which show the supported update paths and possible incompatibilities. SAP HANA HotNews: SAP Note 2688515 |
| Consistency check | A consistency check should be carried out before and after an upgrade to ensure that all data and configurations are correct and complete. |
| Backup and defragmentation | Regular backups and defragmentation are necessary to ensure data integrity and optimal memory utilization. It is recommended to back up both the database and the configurations before an upgrade. |
| Host Agent | The SAP host agent is an agent that can perform multiple life cycle management tasks such as operating system monitoring, database monitoring and system instance control and provisioning. |
| SAP KERNEL | SAPEXE, which is independent of the database (disp+work, R3trans, tp, etc.) SAPEXEDB, which is dependent on the database (libdbsl, R3load, R3ta, etc.) |
