orkungedik/SAP-basis-dataset huggingface dataset:
## 5.1 On-Premise Deployment
In an on-premise deployment, SAP HANA runs on dedicated hardware.
On-premise SAP HANA is deployed through the following offerings:
- As an appliance , SAP HANA combines software components with proven SAP-optimized hardware provided by SAP's hardware partners. This approach is valid for Intel-based hardware platforms only.
- Compared with the appliance delivery approach, SAP HANA tailored data center integration (TDI) is a more open and flexible approach, designed to serve your needs regarding the integration of SAP HANA in the data center. The requirements for this deployment option are as follows:
- The server is certified and belongs to the allowed hardware.
- The storage solution has successfully passed SAP HANA hardware certification.
- The components of SAP HANA can only be installed by certified hardware partners, or any person holding certification on certified hardware running an approved operating system. See the SAP Education resources for information about the SAP HANA certification exams.
##  Note
The supported hardware for SAP HANA depends on the deployment method used (appliance or TDI). For more information, see the Related Information in this section and under SAP HANA Hardware and Software Requirements in the SAP HANA Master Guide .
## Related Information
Certified Appliance Hardware (also applicable for compute servers in TDI environments)
SAP Certified and Supported SAP HANA Hardware
SAP HANA Tailored Datacenter Integration (TDI)
SAP HANA Tailored Data Center Integration 2017 - Overview
SAP HANA Tailored Data Center Integration - Frequently Asked Questions
SAP Certified Enterprise Storage Hardware for SAP HANA
Certified and Supported SAP HANA Hardware - Supported Intel Systems
SAP Note 1943937
SAP Note 2493172
SAP Note 1900823
SAP HANA Network Requirements
## SAP HANA on IBM Power Systems
SAP Note 2055470
SAP Note 2218464
## General Links
SAP Education and Course Directory
Certification at SAP
## 6 SAP HANA Implementation and Operation
The implementation and operation of SAP HANA depends on the chosen use case and the technical deployment.
## 6.2 Installing SAP HANA
The installation of SAP HANA comprises several steps. The central part is the installation of the SAP HANA Platform Edition. You need to check specific installation information, depending on the data provisioning technology you use and the other components you want to add to your SAP HANA landscape.
## SAP HANA Platform Edition
For information about installing SAP HANA, see the SAP HANA documentation on SAP Help Portal:
- SAP HANA Server Installation and Update Guide This guide describes how to install and update an SAP HANA system with the SAP HANA lifecycle management tools. See the SAP HANA Platform page on SAP Help Portal.
##  Note
SAP HANA installations are performed using the SAP HANA database lifecycle manager (HDBLCM). SAP HANA installations cannot be performed using the Software Provisioning Manager (SWPM).
- SAP HANA Client Installation and Update Guide See the SAP HANA Platform page on SAP Help Portal.
- SAP HANA Studio Installation and Update Guide See the SAP HANA Platform page on SAP Help Portal.
## Data Provisioning Technologies
You can find the documentation for the data provisioning technologies on various publication channels:
- SAP HANA Installation Guide - Trigger-Based Replication (SLT) See the SAP HANA Platform page on SAP Help Portal.
- SAP HANA Direct Extractor Connection Implementation Guide See the SAP HANA Platform page on SAP Help Portal.
● SAP HANA smart data access SAP HANA smart data access is part of SAP HANA. However, it is not installed during the installation of the SAP HANA Platform Edition. For more information about installing SAP HANA smart data access, see SAP HANA Smart Data Access in the SAP HANA Administration Guide . For IBM Power Systems, only the following data sources are supported: SAP HANA, SAP IQ, SAP Adaptive
Service Enterprise, and Oracle Database 12C. For more information, see SAP HANA Smart Data Access in
- the SAP HANA Administration Guide .
- ETL-based replication (SAP Data Services)
- See the SAP Data Services page on SAP Help Portal.
- Log-based replication (SAP Replication Server) See the SAP Replication Server page on SAP Help Portal.
- SAP HANA smart data integration See the SAP HANA Smart Data Integration page on SAP Help Portal.
## Related Information
SAP Data Services SAP Replication Server SAP HANA Smart Data Integration and SAP HANA Smart Data Quality SAP HANA Real-Time Replication SAP HANA Platform
## 6.3 Administrating SAP HANA
The SAP HANA Administration Guide provides information about administering SAP HANA system landscape.
## 6.5.1  SAP HANA Appliance
SAP HANA comes as an appliance combining software components from SAP optimized on proven hardware provided by SAP's hardware partners.
This approach offers you well-defined hardware designed for the performance needs of an in-memory solution out of the box. The appliance delivery is the first choice if you are looking for a preconfigured hardware set-up and a preinstalled software package for a fast implementation done by your chosen hardware partner and fully supported by both, the partner and SAP.
You can decide to implement SAP HANA using the appliance delivery model, meaning preconfigured software and hardware bundled by an SAP hardware partner, or you can opt for the SAP HANA tailored data center integration approach, which allows you more flexibility when integrating your SAP HANA system with your existing storage solution. For more information see SAP HANA Tailored Data Center Integration .
## Related Information
SAP HANA Tailored Data Center Integration [page 46]
## 6.5.1.2 Service and Support
If errors occur in any software component of SAP HANA, SAP is the main point of contact. SAP distributes all issues within the support organization by default, as is the case for other SAP applications.
If the customer has defined special support agreements with the hardware partner (such as a special Service Level Agreement (ESA)), the customer should contact the hardware partner directly in the case of obvious hardware or operating system issues.
To investigate SAP HANA-related problems, SAP support requires a support connection to all servers in the SAP HANA landscape. For more information about establishing a service connection for SAP HANA, see SAP Note 1635304: Central note for HANA support connections .
##  Note
You need a valid user to access SAP Support Portal and related SAP Notes.
## Related Information
<!-- image -->
## 6.5.1.4 Change Management
Change management describes the permitted changes allowed to the standard configuration of an SAP HANA appliance.
The following sections provide information on permitted configuration changes to the SAP HANA software, operating system, and so on. You will also find information about the changes that are not supported by SAP or SAP hardware partners.
SAP allows changes in configuration parameters in the SAP HANA database, when this is recommended in SAP documentation, SAP Notes or by an SAP employee (for example, Consulting, Development, or Support).
To guarantee optimal performance and the highest stability, SAP HANA hardware and technology partners can deliver systems with settings that differ from the SAP standard system.
Customer-specific changes to operating system parameters and ports are permitted in agreement with the relevant SAP HANA hardware or technology partners.
SAP Note 1731000 describes configuration changes that resulted in problems in customer environments and in SAP or hardware partner lab environments.
To guarantee supportability from SAP, all changes that differ from the SAP standard system should be documented. This facilitates later root cause analysis if errors occur.
## Related Information
SAP Note 1731000
## 6.5.1.4.1 Updating and Patching the Operating System
The customer is generally responsible for implementing operating system patches. If the customer has a special agreement with the hardware partner, support for operating system patching may be the responsibility of the hardware partner.
For a list of hardware platforms and supported operating system releases, see SAP Note 2235581 - SAP HANA: Supported Operating Systems . For configuration information for the supported operating system releases, see SAP Note 1944799 - SAP HANA Guidelines for SLES Operating System Installation and SAP Note 2009879 - SAP HANA Guidelines for Red Hat Enterprise Linux (RHEL) Operating System .
SAP supports additional changes to the configuration of the operating system, provided these changes do not contradict the currently applicable SAP HANA documentation, or their incompatibility with SAP HANA is already known. These incompatible configuration changes, which are known in customer environments and/or are known to have caused problems to the laboratories of SAP or to SAP HANA hardware or to technology partners, are described in SAP Note 1731000 .
OS security patches may be installed immediately after they are available; however, the original packages of the distributors must be used, that a customer is entitled to within the framework of a valid support contract with the distributor or an authorized OEM.
Customer-specific changes to operating system parameters and ports are permitted in agreement with the relevant SAP HANA hardware or technology partners. To guarantee supportability on the SAP side, all changes that deviate from the SAP standard system should be documented. This facilitates later root cause analysis if errors occur.
Any updates related to kernel or runtime libraries (glibc) need to be validated and approved by SAP beforehand. Support Package Stacks (SPSs) can be downloaded and applied to the SAP HANA system only according to agreements with the respective hardware partner.
On rare occasions, SAP HANA might require a certain operating system patch. In this case, you must ensure that the configuration settings of the operating system persist. Do not change configuration settings when you patch the operating system unless explicitly stated in the corresponding SAP release note. SAP will state any dependencies in the relevant SAP Note published when a revision is released which requires such modifications.
##  Note
In some cases, customers may have outsourced the administration of their landscapes. In such a case, the outsourced service provider should only change any settings after consultation with the hardware support provider. The customer is responsible for any complete upgrade of the operating system and the use of tools for distributing operating system patches in a distributed system landscape.
SUSE offers enhanced support for SUSE Linux in collaboration with SAP Linux Lab ('SUSE Priority Support for SAP'). This support offer facilitates communication and ensures high quality.
## Related Information
SAP Note 2235581
SAP Note 1944799
SAP Note 2009879
SAP Note 1731000
## 6.5.1.4.2 Updating and Patching SAP HANA Appliance Software
The SAP HANA appliance is shipped with the latest available support package stack and the customer is usually responsible for implementing any subsequent updates and patches.
The SAP hardware partners ships the SAP HANA appliance pre-configured with the most recent support package stack that is available. The customer is responsible for the subsequent implementation of SAP HANA patches, revisions, or support packages and support package stacks.
In general the following points apply:
- Any system connected to the SAP HANA system, as a source or as a client, may require a minimum SAP HANA support package stack to be implemented. Unless explicitly stated, we recommend applying the latest SAP HANA support package stack after applying an update to the connected system.
- The SAP HANA support packages are cumulative. You can update directly from any older SAP HANA support package to any newer SAP HANA support package.
- New SAP HANA support packages mainly cover software improvements. SAP recommends that you download and install these new SAP HANA support packages if SAP support has to resolve issues with SAP HANA versions previously installed in your landscape. However, customers do not necessarily need to update their SAP HANA landscape with the newest SAP HANA support packages if their SAP HANA landscape works correctly.
- New SAP HANA support packages and patches will be produced and shipped at SAP's sole discretion. There is no periodic cycle for releasing and patching the SAP HANA software. The new SAP HANA support package stacks will be communicated to customers and hardware partners by means of SAP Notes.
An automated update of your SAP HANA system is performed using SAP HANA database lifecycle manager (HDBLCM).
##  Note
It is strongly recommended after the initial setup and before every system update, that you perform a full data and file system backup (including a configuration backup).
##  Note
Special support agreements may exist with the hardware partner which include services such as patching.
## Related Information
Updating an SAP HANA System Landscape [page 48]
## 6.5.1.4.3 Updating and Patching File System Components
The customer is responsible for implementing patches for the shared file system.
If the customer has a special agreement with the hardware partner, the hardware partner is responsible for providing support for file system patching.
## 6.5.1.4.4 Updating and Patching Storage Components
The customer is responsible for implementing patches for the storage components.
If the customer has a special agreement with the hardware partner, the hardware partner is responsible for providing support for the storage components.
## 6.5.1.4.5 Updating and Patching Firmware of Underlying Hardware Components
The customer is responsible for implementing patches for the firmware of underlying hardware components.
If the customer has a special agreement with the hardware partner, the hardware partner is responsible for providing support for the firmware of underlying hardware components.
## 6.5.2  SAP HANA Tailored Data Center Integration
SAP HANA tailored data center integration offers you more openness and freedom of choice to configure the layer for SAP HANA depending on your existing data center layout.
In addition to SAP HANA as a standardized and highly optimized appliance, you can use the tailored data center integration approach, which is more open and flexible, to run SAP HANA in datacenters. This option enables a reduction in hardware and operational costs through the reuse of existing hardware components and operational processes.
## Roles and Responsibilities
With the appliance model SAP distributes all support requests regarding any component of SAP HANA to the correct part of the support organization. With tailored data center integration the customer is responsible for defining support agreements with the various partners and organizing all aspects of support.
## Service and Support
Customers should work with their hardware partners to ensure hardware support requirements are fulfilled.
A supportability tool called the SAP HANA HW Configuration Check Tool is provided by SAP, which allows you to check if the hardware is optimally configured to meet the requirements of SAP HANA. For more information, see the SAP HANA Administration Guide .
## Installation
A number of requirements have to be fulfilled before you can proceed with the installation of SAP HANA tailored data center integration.
- The server must be certified and is listed in the hardware directory.
- All storage devices must have successfully passed the hardware certification for SAP HANA.
- Only software installed by certified hardware partners, or any person holding certification, is recommended for use on the SAP HANA system. Do not install any other software on the SAP HANA system. The components of SAP HANA can only be installed by certified hardware partners, or any person holding certification. Furthermore, it must be installed on validated hardware running an approved operating system.
For more information, see the blogs SAP Certified Technology Associate: C\_HANATEC\_13 - by the SAP HANA Academy and Recent changes in the SAP HANA Technology certification program 2016 in the Related Information section.
## Change Management
- Updating and patching the operating system With tailored data center integration the customer is responsible for updating and patching the operating system.
- Updating and patching the SAP HANA software With tailored data center integration the customer is responsible for installing, updating, and patching the SAP HANA software.
## Related Information
SAP Certified and Supported SAP HANA Hardware
Product Availability Matrix (PAM)
Partner Information Center
SAP Training and Certification Shop
SAP HANA TDI - Overview
SAP Note 2055470
SAP Note 2218464
Recent changes in the SAP HANA Technology certification program 2016
SAP Certified Technology Associate: C\_HANATEC\_13 - by the SAP HANA Academy
## 6.6 Updating an SAP HANA System Landscape
This section gives you an overview of the activities you have to perform when you update SAP HANA Platform 1.0 (all supported SPS) to SAP HANA Platform 2.0 SPS 00 and when you update SAP HANA Platform 2.0 to a higher release.
##  Caution
A direct update of SAP HANA Platform 1.0 to SAP HANA 2.0 SPS 00 for IBM Power Systems is not possible.
The goal of the update activities is that an SAP HANA landscape that has been updated to SAP HANA 2.0 has a comparable state to a newly installed SAP HANA 2.0 landscape.
The update activities are split into the following areas:
- Update an SAP HANA system You perform an update on your SAP HANA system with the SAP HANA database lifecycle manager
(HDBLCM).
- Update dependent components
##  Note
Plan to have a business downtime during the update process.
##  Note
For information about updating the capabilities available for your license and installation scenario, see the documentation for the capabilities you are using.
##  Note
With an SAP HANA SPS you also perform updates for SAP HANA revisions and SAP HANA maintenance revisions. For more information, see SAP Note 2378962 - SAP HANA 2.0 Revision and Maintenance Strategy .
## Related Information
<!-- image -->
SAP HANA 2.0 Revision Strategy SAP Note 2378962 Update Dependent Components [page 57]
## 6.6.1  Prerequisites
Before starting the update for the components in your SAP HANA landscape several prerequisites have to be fulfilled.
Make sure you fulfill the following prerequisites:
- If you are performing an offline update, you have all the necessary installation files for the individual components.
- You have a valid, permanent SAP license for the SAP HANA database.
- You have user names and passwords for the following users:
- &lt;sid&gt;adm user
- sapadm user
- S-user for the SAP Support Portal
- You have carefully read the update instructions for the individual components.
- You have made the necessary preparations to perform backups for the SAP HANA database and the other components.
## 6.6.2  Update Process
Before updating the SAP HANA components, make sure that no read or write processes are running on the SAP HANA database. Perform the update process in offline mode during a business downtime. After the update, you have to restart SAP HANA and its components.
##  Caution
Updating from SAP HANA Platform 1.0 (all supported SPS) to SAP HANA Platform 2.0 SPS 00 also involves upgrading the operating system and possibly changing the hardware.
Updating an SAP HANA Platform 2.0 system might also involve upgrading the operating system and possibly changing the hardware.
This is the general sequence of the steps you have to perform:
1. Stop all processes.
2. We strongly recommend a system backup.
3. Perform an update. When updating to SAP HANA Platform 2.0 SPS 00 or higher, it may be necessary to upgrade the operating
system. For more information, see SAP Note 2235581 - SAP HANA: Supported Operating Systems .
4. Update the dependent components.
5. Perform the post-update steps.
6. Restart all processes.
## Related Information
<!-- image -->
SAP Note 2235581
SAP Note 2372809
Update an SAP HANA 1.0 System with the SAP HANA Database Lifecycle Manager [page 51]
Update an SAP HANA 2.0 System with the SAP HANA Database Lifecycle Manager [page 57]
Upgrade the Operating System [page 50]
## 6.6.2.1 Upgrade the Operating System
The different versions of the SAP HANA Platform are only supported on specific operating system versions. For information about supported operating system versions for SAP HANA, see "SAP Note 2235581 - SAP HANA: Supported Operating Systems".
When updating to SAP HANA Platform 2.0 SPS 00, you may need to upgrade the operating system. For information about the upgrade, refer to the documentation of the operating system vendor. For the operating system, we recommend that you choose a new installation as the upgrade procedure. We recommend the following procedures:
- RHEL For RHEL 7.2 we recommend a new installation.
- SLES For SLES 12 SP1 we recommend a new installation.
## Related Information
<!-- image -->
SAP Note 2235581
SAP Note 2372809
## 6.6.2.2 Update an SAP HANA 1.0 System with the SAP HANA Database Lifecycle Manager
An update of your SAP HANA system from the local host is performed using the SAP HANA database lifecycle manager.
##  Caution
The following update scenarios are valid for Intel-based hardware platforms only.
For information about updating IBM Power Systems, see SAP Note 2380257 SAP HANA Platform 2.0 SPS 00 Release Note .
##  Caution
For a general description of the upgrade recommendations, see SAP Note 2407244 - Ensuring OS/HANA compatibility during upgrade of HANA/OS .
We recommend that you update to SAP HANA Platform 1.0 SPS 12 first and then update to SAP HANA Platform 2.0 SPS 00. An update to SAP HANA Platform 1.0 SPS 10/11 should only be performed if a specific operating system version is needed.
A multiple-container system can only be updated to SAP HANA Platform 2.0 SPS 00 from SAP HANA Platform 1.0 SPS 12 (Revision 122.04).
When updating to SAP HANA Platform 2.0 SPS 00, it might be necessary to upgrade the operating system. Check which update option for the SAP HANA system is compatible with the method that you choose for upgrading the operating system.
For information about the SAP HANA database lifecycle manager, see Updating the SAP HANA System and Installing or Updating SAP HANA Components in the SAP HANA Server Installation and Update Guide .
##  Note
Update all SAP HANA studio installations. Use the same revision as the SAP HANA database.
## Related Information
SAP Note 1948334
SAP Note 2380257
SAP Note 2407244
SAP Note 2503043
Upgrade the Operating System [page 50]
## 6.6.2.2.1 Update an Existing SAP HANA System
The recommended approach for updating SAP HANA Platform 1.0 (all supported SPS) to SAP HANA Platform 2.0 SPS 00 is to update on an existing SAP HANA system.
## 6.6.2.2.1.1  Update an SAP HANA System from 1.0 SPS 10 - 1.0 SPS 12 to SAP HANA Platform 2.0 SPS 00
Update an SAP HANA system from SAP HANA Platform 1.0 SPS 10 - SAP HANA Platform 1.0 SPS 12 to SAP HANA Platform 2.0 SPS 00:
1.
##  Note
With SAP HANA Platform 2.0, the metadata persistency layout has been changed. Furthermore an older column store persistence format has been deprecated and is not supported anymore. Therefore you need to pay special attention before updating your existing SAP HANA 1.0 system to SAP HANA Platform 2.0.
Run the procedure HANA2\_PERSISTENCE\_MIGRATION\_HELPER as described in SAP Note 2372809.
2. Stop the SAP HANA system and all applications that use the SAP HANA system.
3. Perform a system backup.
4. To prevent the SAP HANA system from starting during the operating system upgrade, set the autostart parameter in the profile to 0 (=off).
The profile can be found here: /hana/shared/&lt;SID&gt;/profile/ &lt;SID&gt;\_HDB&lt;instance\_number&gt;\_&lt;hostname&gt;
5. Upgrade the operating system to RHEL 7.2 or SLES 12 SP1.
2. For more information, see Upgrade the Operating System in the SAP HANA Master Guide .
6. Update the SAP HANA system to SAP HANA 2.0 SPS 00.
## Related Information
SAP Note 2372809
Upgrade the Operating System [page 50]
## 6.6.2.2.1.2  Update an SAP HANA System from 1.0 SPS 07 1.0 SPS 09 to SAP HANA Platform 2.0 SPS 00
Update an SAP HANA system from SAP HANA Platform 1.0 SPS 07 - SAP HANA Platform 1.0 SPS 09 to SAP HANA Platform 2.0 SPS 00:
1. Stop the SAP HANA system and all applications that use the SAP HANA system.
2. Perform a system backup.
3. To prevent the SAP HANA system from starting during the operating system upgrade, set the autostart parameter in the profile to 0 (=off).
The profile can be found here: /hana/shared/&lt;SID&gt;/profile/
&lt;SID&gt;\_HDB&lt;instance\_number&gt;\_&lt;hostname&gt;
4. Update the SAP HANA system to SPS 10, SPS 11, or SPS 12.
5.
##  Note
With SAP HANA Platform 2.0, the metadata persistency layout has been changed. Furthermore an older column store persistence format has been deprecated and is not supported anymore. Therefore you need to pay special attention before updating your existing SAP HANA 1.0 system into SAP HANA Platform 2.0.
Run the procedure HANA2\_PERSISTENCE\_MIGRATION\_HELPER as described in SAP Note 2372809.
6. Upgrade the operating system to RHEL 7.2 or SLES 12 SP1. For more information, see Upgrade the Operating System in the SAP HANA Master Guide
7. Update the SAP HANA system to SAP HANA 2.0 SPS 00.
## Related Information
SAP Note 2372809
Upgrade the Operating System [page 50]
## 6.6.2.2.1.3  Update an SAP HANA Platform 1.0 SPS 06 System or Lower to SAP HANA Platform 2.0 SPS 00
Update an SAP HANA Platform 1.0 SPS 06 system or lower to SAP HANA Platform 2.0 SPS 00:
1. Stop the SAP HANA system and all applications that use the SAP HANA system.
2. Perform a system backup.
3. To prevent the SAP HANA system from starting during the operating system upgrade, set the autostart parameter in the profile to 0 (=off).
The profile can be found here: /hana/shared/&lt;SID&gt;/profile/
&lt;SID&gt;\_HDB&lt;instance\_number&gt;\_&lt;hostname&gt;
4. Update the SAP HANA system to SAP HANA Platform 1.0 SPS 06 (version 69.07) according to SAP Note 2175754. This is the minmum version of SAP HANA that is required, in order to update to SAP HANA Platform 1.0 SPS 10.
.
5. Update the SAP HANA system to SPS 10, SPS 11, or SPS 12.
## 6.  Note
With SAP HANA Platform 2.0, the metadata persistency layout has been changed. Furthermore an older column store persistence format has been deprecated and is not supported anymore. Therefore you need to pay special attention before updating your existing SAP HANA 1.0 system to SAP HANA Platform 2.0.
Run the procedure HANA2\_PERSISTENCE\_MIGRATION\_HELPER as described in SAP Note 2372809.
7. Upgrade the operating system to RHEL 7.2 or SLES 12 SP1. For more information, see Upgrade the Operating System in the SAP HANA Master Guide
8. Update the SAP HANA system to SAP HANA 2.0 SPS 00.
## Related Information
SAP Note 2372809
Upgrade the Operating System [page 50]
## 6.6.2.2.2 Update an SAP HANA System Using System Replication
Update an SAP HANA system using system replication:
1. Perform a system backup of the secondary site.
2. On the secondary site, update the SAP HANA system to SAP HANA Platform 1.0 SPS 10, SPS 11, or SPS 12 if the SAP HANA system is lower than SAP HANA Platform 1.0 SPS 10.
3. On the secondary site, upgrade the operating system to RHEL 7.2 or SLES 12 SP1.
4. On the secondary site, update to SAP HANA 2.0 SPS 00.
5. On the secondary site perform a takeover.
6. On the old primary site, update the SAP HANA system to SAP HANA Platform 1.0 SPS 10, SPS 11, or SPS 12 if the SAP HANA system is lower than SAP HANA Platform 1.0 SPS 10.
## 7.  Note
With SAP HANA Platform 2.0, the metadata persistency layout has been changed. Furthermore an older column store persistence format has been deprecated and is not supported anymore. Therefore you need to pay special attention before updating your existing SAP HANA 1.0 system to SAP HANA Platform 2.0.
Run the procedure HANA2\_PERSISTENCE\_MIGRATION\_HELPER as described in SAP Note 2372809.
8. On the old primary site, upgrade the operating system or RHEL 7.2 or SLES 12.1. For more information, see Upgrade the Operating System in the SAP HANA Master Guide .
9. On the old primary site, update to SAP HANA 2.0 SPS 00.
10. Register the old primary site to the old secondary site so that system replication is ready.
.
## Related Information
SAP Note 2372809 Upgrade the Operating System [page 50]
## 6.6.2.2.3 Update an Existing SAP HANA System with Unregister and Register
Update an SAP HANA system using unregister and register:
1.
##  Note
In SAP HANA Platform 2.0, the metadata persistency layout has been changed. Also, an older column store persistence format has been deprecated and is no longer supported. You therefore need to pay special attention to what you need to do before updating your existing SAP HANA 1.0 system to SAP HANA Platform 2.0.
Run the procedure HANA2\_PERSISTENCE\_MIGRATION\_HELPER as described in SAP Note 2372809.
2. Stop the SAP HANA system and all applications that use the SAP HANA system.
3. Perform a system backup.
4. To prevent the SAP HANA system from starting during the operating system upgrade, set the autostart parameter in the profile to 0 (=off).
The profile can be found here: /hana/shared/&lt;SID&gt;/profile/
&lt;SID&gt;\_HDB&lt;instance\_number&gt;\_&lt;hostname&gt;
5. Update the SAP HANA system to SAP HANA Platform 1.0 SPS 12.
6. Unregister the SAP HANA system with the resident hdblcm. This removes all operating system integration, such as symlinks and OS users. For more information, see Copying and Moving a System Using Platform LCM Tools in the SAP HANA Administration Guide .
7. If the SAP Host Agent is installed in /usr/sap/hostctrl , uninstall it as the root user with:
/usr/sap/hostctrl/exe/saphostexec -uninstall
Alternatively, you can remove the /usr/sap/hostctrl directory.
The SAP Host Agent administrator user sapadm will be removed when the operating system is reinstalled, and the SAP Host Agent becomes unusable without this user. The SAP Host Agent will be installed again, and the sapadm user created, when the SAP HANA system is registered in a later step.
8. Unmount the /hana/shared , data , and log file systems:
- If it is not possible to unmount a file system, use the fuser command to find out which processes still access files on the file system:
fuser -m /hana/shared
Use the ps command to find out what those processes are, and terminate them.
- If a file system cannot be unmounted even though the fuser command shows no processes accessing it, it can be accessed from a remote computer. See your operating system documentation for more details.
9. Upgrade the operating system to RHEL 7.2 or SLES 12 SP1. For more information, see Upgrade the Operating System in the SAP HANA Master Guide .
10. Mount the /hana/shared , data , and log file systems.
11. Register the SAP HANA system with the resident hdblcm. This creates the operating system integration, such as symlinks and OS users.
12. Update the SAP HANA system to SAP HANA 2.0 SPS 00.
## Related Information
```
SAP Note 2372809 Upgrade the Operating System [page 50]
```
## 6.6.2.2.4 Update with Backup and Restore on a New SAP HANA System
You can perform an update with backup and restore from SAP HANA 1.0 (all supported SPS) to SAP HANA 2.0 SPS 00 on a new SAP HANA system:
1.
##  Note
With SAP HANA Platform 2.0, the metadata persistency layout has been changed. Furthermore an older column store persistence format has been deprecated and is not supported anymore. Therefore you need to pay special attention before updating your existing SAP HANA 1.0 system into SAP HANA Platform 2.0.
Run the procedure HANA2\_PERSISTENCE\_MIGRATION\_HELPER as described in SAP Note 2372809.
2. Stop the old SAP HANA system and all applications that use the SAP HANA system.
3. On the old SAP HANA system, perform a system backup.
4. On the new host, install operating system RHEL 7.2 or SLES 12 SP1. For more information, see Upgrade the Operating System in the SAP HANA Master Guide .
5. Move the backup files from the old SAP HANA system to the new host.
6. On the new host, install SAP HANA Platform 1.0 SPS 10 or SPS 11 or SPS 12.
7. On the new SAP HANA system, perform a recovery using the backup files from the old SAP HANA system.
8. Update the new SAP HANA system to SAP HANA 2.0 SPS 00.
## Related Information
SAP Note 2372809 Upgrade the Operating System [page 50]
## 6.6.2.3 Update an SAP HANA 2.0 System with the SAP HANA Database Lifecycle Manager
An update of your SAP HANA system from the local host is performed using the SAP HANA database lifecycle manager.
##  Caution
The following update scenarios are valid for Intel-based hardware platforms only.
For information about updating IBM Power Systems, see SAP Note 2551355 - SAP HANA Platform 2.0 SPS 03 Release Note .
##  Caution
For a general description of the upgrade recommendations, see SAP Note 2407244 - Ensuring OS/HANA compatibility during upgrade of HANA/OS .
For information about the SAP HANA database lifecycle manager, see Updating the SAP HANA System and Installing or Updating SAP HANA Components in the SAP HANA Server Installation and Update Guide .
##  Note
Update all SAP HANA studio installations. Use the same revision as the SAP HANA database.
## Related Information
```
SAP Note 1948334 SAP Note 2551355 SAP Note 2460914 SAP Note 2404375 SAP Note 2380257 SAP Note 2407244 SAP Note 2503043 Upgrade the Operating System [page 50]
```
## 6.6.2.4 Update Dependent Components
Dependent components need to be updated.
- SAP HANA Client Update all SAP HANA clients that are not located on an SAP HANA system. Use the same revision as the SAP HANA database.
- SAP HANA Studio
Update all SAP HANA studio installations that are not located on an SAP HANA system. Use the same revision as the SAP HANA database:
- If you are using a complete SPS installation media, use the SAP HANA studio version on this media.
- If you are downloading an individual SAP HANA studio installation media, make sure you use an SAP HANA studio version that matches with your SAP HANA database version. Check the version number in the file name of the SAP HANA studio installation media.
- SAP HANA Data Provisioning Technologies Components replication technologies in use. For detailed update and installation information, see the guide for your data
- Update the SAP HANA data provisioning technologies components depending on your scenario and the provisioning technology.
- Update Business Intelligence (BI) Clients Using SAP HANA Update the Business Intelligence (BI) clients you are using for SAP HANA.
## Related Information
SAP HANA Platform on SAP Help Portal
SAP Note 1906576
## 6.6.2.5 Post-Update Steps
Perform the necessary post-update steps.
##  Note
After an upgrade to a new SAP HANA SPS it is recommended to redeploy the calculation views. For more information, see SAP Note 1962472 - Redeployment of calculation views recommended when upgrading to a new SPS .
## Related Information
<!-- image -->
SAP Note 1962472
## 6.6.3  Update to Higher Revisions of the SAP HANA Database
After the release of an SPS of the SAP HANA software, new revisions of the SAP HANA database are released. Use the SAP HANA database lifecycle manager to perform an update from the local host.
## 6.7 SAP HANA Lifecycle Management
SAP HANA lifecycle management covers two aspects: platform lifecycle management for customizing and updating your SAP HANA platform and application lifecycle management for managing SAP HANA content products and transports.
<!-- image -->
## Platform Lifecycle Management Aspects
You can customize platform lifecycle management aspects of your SAP HANA system by accessing the SAP HANA database lifecycle manager from three user interfaces: the graphical user interface, the command-line interface, or the Web user interface in a stand-alone Web browser, in the SAP HANA studio, or via the SAP HANA cockpit.
SAP HANA platform lifecycle management encompasses the installation and update of an SAP HANA server, mandatory components, and additional components, as well as the post-installation configuration. The concepts and procedures for SAP HANA platform installation and update are described in the SAP HANA Server Installation and Update Guide on SAP Help Portal.
A number of system configuration features are integrated into the SAP HANA database lifecycle manager, such as:
- The initial configuration of your SAP HANA platform to integrate it into your landscape. For example, by registering it in a system landscape directory, or configuring the inter-service communication.
- Adapting the topology of your SAP HANA platform by adding or removing additional SAP HANA hosts.
- Reconfiguring the system.
System configuration as it pertains to SAP HANA lifecycle management is described in the SAP HANA Platform Lifecycle Management section of this SAP HANA Administration Guide .
## Application Lifecycle Management Aspects
SAP HANA application lifecycle management aspects can be accessed in different user interfaces: an interface that runs as an SAP HANA XS application in a web browser, a command-line tool hdbalm, integrated in SAP HANA studio, or via the SAP HANA cockpit.
SAP HANA application lifecycle management supports you in all phases of the lifecycle of an SAP HANA application or add-on product, from modelling your product structure, through application development, transport, assembly, to installing and updating products that you have downloaded from SAP Support Portal or which you have assembled yourself.
All application lifecycle management tasks are documented in the guide SAP HANA Application Lifecycle Management on SAP Help Portal.
System administrators use SAP HANA application lifecycle management mainly to install and update SAP HANA applications or add-on products. Therefore, these tasks are documented in this SAP HANA Administration Guide . T asks related to SAP HANA development are documented in the SAP HANA Developer Guide - For SAP HANA Studio ( on SAP Help Portal) under SAP HANA Application Lifecycle Management .
## 7 Additional Information
This section provides additional information.
## 7.3 SAP License Key
You must install a permanent SAP license for the SAP HANA database.
When you install your SAP system, a temporary license (90 days) is automatically installed. Before the temporary license expires, you must apply for a permanent license key from SAP.
We recommend that you apply for a permanent license key as soon as possible after installing your system.
##  Note
For more information, see section Managing SAP HANA Licenses in the SAP HANA Administration Guide .
## 7.4 Software Download
In the SAP Software Downloads, you have access to the installation media and components for SAP HANA.
##  Caution
It is essential to keep a copy of all installation media which may be required, for example, for disaster recovery purposes. Installation media which has been superseded is routinely removed from the Software Center and there is no guarantee that all database revisions will be permanently available.
## Installation Media and Components for SAP HANA
## Installation Media for an SAP HANA SPS
1. Open the SAP Software Downloads .
2. Go to INSTALLATIONS &amp; UPGRADES , if not already chosen.
3. Open &gt; By Alphabetical Index (A-Z) .
4. Choose H .
5. Choose SAP HANA PLATFORM EDITION .
6. Go to DOWNLOADS , if not already opened.
7. Choose SAP HANA PLATFORM EDITION 2.0 .
8. Open DOWNLOADS , if not already opened.
9. Choose INSTALLATION .
10. Download the items you need.
##  Remember
The items you have downloaded must be available on the host where the SAP HANA system will be installed or already is installed.
## Support Packages and Patches for SAP HANA
1. Open the SAP Software Downloads .
2. Choose SUPPORT PACKAGES &amp; PATCHES , if not already chosen.
3. Open &gt; By Alphabetical Index (A-Z) .
4. Choose H .
5. Choose SAP HANA PLATFORM EDITION .
6. Choose DOWNLOADS , if not already chosen.
7. Choose SAP HANA PLATFORM EDITION 2.0 .
8. Choose DOWNLOADS , if not already chosen.
9. Open the required component and download the items you need.
##  Remember
The items you have downloaded must be available on the host where the SAP HANA system will be installed or is already installed.
## Responsibilities
The responsibility for acquiring and installing SAP HANA depends on the chosen deployment model:
- If a customer chooses the SAP HANA Tailored Datacenter Integration , then the components of SAP HANA must be installed on validated hardware by a certified administrator or official SAP HANA hardware partner.
- If a customer chooses an SAP HANA appliance , then the components of SAP HANA can only be installed by certified hardware partners on validated hardware running a specific operating system. Any other system or content developed with systems of this type is not supported by SAP. For more information, see the information page for the product version. Support Package Stacks (SPS) can be downloaded and applied to appliances in accordance with agreements with the respective hardware partner.
##  Note
The SAP HANA Client is also available separately under the terms of the SAP Developer License Agreement, from the SAP Development Tools public download site. The Developer Agreement licenses the
software "as is", without warranty or any other obligations on the part of SAP . Other than what is made available on the SAP Community Website (SCN) by SAP at its sole discretion and by SCN members, SAP does not offer support for software that is the subject of the Developer Agreement.
## Related Information
<!-- image -->
SAP Software Downloads SAP Developer License Agreement SAP Development Tools
## 7.5 SAP HANA Revision Strategy
SAP HANA software is released in two categories of software bundles - support package stacks (SPSs) and revisions.
For more information, see SAP HANA 2.0 Revisions Strategy on SAP Help Portal and SAP Note 2551355 - SAP HANA Platform 2.0 SPS 03 Release Note .
## Related Information
SAP HANA 2.0 Revision Strategy
SAP Note 2378962
SAP Note 2551355
## 2 SAP HANA System Replication: Basic Concepts
Before configuring your system replication landscape, learn about basic concepts and possible setups.
## What do I need to know before configuring system replication?
Learn which operation and replication modes are supported. The selected operation mode determines what types of data packages are sent to the secondary system. The operation mode determines also which technique (data retention or log retention) is used to achieve a resync whenever system replication is out of sync.
The network connection between the primary and the secondary systems is also important, because it impacts the overall performance of the systems involved in a system replication landscape. While the network throughput requirements of the communication channel used in SAP HANA system replication are influenced by the used operation modes, the selected replication modes impact the network latency requirements.
Finally, in system replication landscapes you can run also other systems (for example, DEV, QA systems, or even productive systems) on the secondary system's hardware while the primary system is in production.
## Where can I find more information?
The following SAP Notes are relevant for a full understanding of the basic concepts described in this chapter: SAP Notes
<!-- image -->
<!-- image -->
<!-- image -->
<!-- image -->
|   SAP Note | Title                                                                                                                       |
|------------|-----------------------------------------------------------------------------------------------------------------------------|
|    1999880 | FAQ: SAP HANASystem Replication                                                                                             |
|    1969700 | SQL Statement Collection forSAPHANA                                                                                         |
|    1681092 | Multiple SAP HANADBMSs(SIDs) on one SAP HANAsystem                                                                          |
|    2211663 | The license changes in an SAP HANAdatabase after the deregistration of the secondary site from a system replication setting |
|    2447994 | SAP HANADynamic Tiering Support for SAP HANASystem Replication                                                              |
## Related Information
Introduction [page 9]
Replication Modes for SAP HANA System Replication [page 12] Operation Modes for SAP HANA System Replication [page 14] Data Transferred to the Secondary System [page 16] Resync Optimization [page 19] Network Recommendations [page 27] Secondary System Usage [page 31]
## 2.4 Data Transferred to the Secondary System
The selected operation mode determines what types of data packages are sent to the secondary system.
When system replication is configured, the following types of data packages can be sent to the secondary system:
- Initial full data shipping When system replication is configured, a full set of data created as an SAP HANA in-place snapshot on the disk of the primary system is initially sent.
● Delta data shipping When using the delta\_datashipping operation mode, the data that has changed since the last full or the last delta data shipping is transported from the data area of the primary system to the data area of the secondary system. The default time is every 10 minutes. When using logreplay and logreplay\_readaccess , delta data shippings are not required.
- Continous redo log shipping Every committing write transaction on the primary system generates redo log buffers, which are
continuously sent to the secondary system.
The following graphic illustrates this traffic on the transportation channel between the primary and the secondary system for the delta\_datashipping operation mode:
<!-- image -->
The following graphic illustrates this traffic on the transportation channel between the primary and the secondary system for the logreplay and logreplay\_readaccess operation modes:
<!-- image -->
##  Note
With the ini file parameter datashipping\_parallel\_channels (default 4), the full and the delta data shipping are done using parallel network channels. You can change it on the secondary system in the global.ini section [system replication] . For more information about configuration parameters, see SAP HANA System Replication Configuration Parameters .
## Related Information
SAP HANA System Replication Configuration Parameters [page 62] Troubleshoot System Replication [page 209] System Replication Network Connection [page 187]