SAP HANA Technical Operations Manual en

PUBLIC
SAP HANA Platform SPS 06 Document Version: 1.0 - 26-06-2013
SAP HANA Technical Operations Manual
Table of Contents
1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 2 2.1 2.2 2.3 2.4 2.5 Getting Started with SAP HANA Appliance Software (SAP HANA). . . . . . . . . . . . . . . . . . . . . . . . . 4 About Technical Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 What is SAP HANA?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 SAP HANA Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.6.1 Download Patches and Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Administering and Operating SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Roles and Responsibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Service and Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Installation of the SAP HANA Appliance Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Software Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.5.1 2.5.2 2.5.3 2.5.4 2.5.5 2.6 2.7 2.6.1 2.7.1 2.7.2 2.7.3 2.8 2.9 Updating and Patching the Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Updating and Patching SAP HANA Appliance Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Updating and Patching File System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Updating and Patching Storage Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Updating and Patching Firmware of Underlying Hardware Components . . . . . . . . . . . . . . . . . 17 Integrating SAP HANA into a Central Operations Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Initial Administrative Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Regular Administrative Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 On Demand Administrative Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Monitoring the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Administering the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Backup and Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.9.1 2.9.2 2.9.3 Security Features and Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Data Center Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.10 3 3.1
High Availability for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Administering and Operating SAP HANA Data Provisioning Technologies. . . . . . . . . . . . . . . . . . . 31 SAP HANA Data Provisioning Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 3.1.1 3.1.2 3.1.3 SAP Sybase Event Stream Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 SAP HANA Smart Data Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 SAP HANA Replication Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP HANA Technical Operations Manual Table of Contents
3.2
Monitoring the SAP HANA System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.2.1 3.2.2 3.2.3 Monitoring Components for Trigger-Based Replication (SAP LT Replication Server). . . . . . . . 44 Monitoring components for SAP HANA Direct Extractor Connection (DXC). . . . . . . . . . . . . . 45 Monitoring Components for ETL-Based Replication (SAP Data Services). . . . . . . . . . . . . . . . 45 Administrating Components for Trigger-Based Replication (SAP LT Replication Server). . . . . 45 Administrating Components for SAP HANA Direct Extractor Connection (DXC). . . . . . . . . . . 46 Administrating Components for ETL-Based Replication (SAP Data Services). . . . . . . . . . . . . 46
3.3
SAP HANA Administration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.3.1 3.3.2 3.3.3
3.4 3.5
Starting the Software Update Manager (SUM) for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Backup and Recovery of SAP HANA Replication Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.5.1 3.5.2 3.5.3 Backup and Recovery for the Trigger-Based Replication components (SAP LT Replication Server). . . . . 47 Backup and Recovery for the SAP HANA Direct Extractor Connection (DXC). . . . . . . . . . . . . 47 Backup and Recovery for the ETL-Based Replication components (SAP Data Services). . . . . . 48
3.6 4 4.1 4.2 4.3 5
Security for the SAP HANA System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 SAP HANA Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Configuring Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Modeling Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Modeling and Data Provisioning for ETL-Based Replication (SAP Data Services). . . . . . . . . . . . . . . . . . 49 SAP liveCache on SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
SAP HANA Technical Operations Manual Table of Contents
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
1 Getting Started with SAP HANA Appliance Software (SAP HANA)

1.1 About Technical Operations
This Technical Operations Manual provides an end-to-end picture of the administration tools available with SAP HANA and the key tasks that a system administrator needs to perform. Links to the relevant administration documentation of each of the components included in the SAP HANA solution are provided for details and step procedures.
Caution
This guide does not replace the daily operations handbook that we recommend customers to create for their specific production operations.
1.2
What is SAP HANA?
SAP HANA is a modern in-memory platform that is deployable as an on-premise appliance, or in the cloud. As an appliance, SAP HANA combines software components from SAP optimized on proven hardware provided by SAPs hardware partners. In the cloud SAP HANA is offered as a comprehensive infrastructure combined with managed services. SAP HANA can also be deployed through the following cloud offerings: SAP HANA One, SAP HANA Cloud and SAP HANA Enterprise Cloud. The SAP HANA platform is a flexible data source agnostic in-memory data platform that allows customers to analyze large volumes of data in real-time. It is also a development platform, providing an infrastructure and tools for building high-performance applications based on SAP HANA Extended Application Services (SAP HANA XS). It is the foundation of various SAP HANA editions, like the SAP HANA Platform Edition, providing core database technology, and the SAP HANA Enterprise Edition, bundling additional components for data provisioning. The SAP HANA Platform Edition integrates a number of SAP components, including the SAP HANA database, SAP HANA studio, and SAP HANA clients.
1.3
SAP HANA Guides
For more information about SAP HANA landscape, security, installation, and administration, see the resources listed below: Topic Location Quick Link http://help.sap.com/hana_platform:
SAP HANA landscape, deployment, SAP HANA Knowledge Center and installation on the SAP Help Portal
PUBLIC
SAP HANA Technical Operations Manual Getting Started with SAP HANA Appliance Software (SAP HANA)
Topic
Location
Quick Link SAP HANA Master Guide SAP HANA Server Installation Guide SAP HANA Master Update Guide SAP HANA Update and Configuration Guide
SAP HANA administration and security
SAP HANA Knowledge Center on the SAP Help Portal
http://help.sap.com/hana_platform: SAP HANA Technical Operations Manual SAP HANA Administration Guide SAP HANA Security Guide
SAP HANA documentation for previous Support Package Stacks
SAP HANA Knowledge Center on SAP Service Marketplace
https://service.sap.com/hana: SAP HANA SPS 05 Documentation (ZIP) SAP HANA SPS 04 Documentation (ZIP) SAP HANA SPS 03 Documentation (ZIP)
1.4
Related Information
For more information about planning your deployment, see the following: Content Latest documentation for SAP HANA Location https://service.sap.com/hana* http://help.sap.com/hana_platform Sybase product documentation Sizing, calculation of hardware requirements, such as CPU, disk, and memory resources SAP BusinessObjects installation and deployment guides SAP BusinessObjects support Sizing, calculation of hardware requirements - such as CPU, disk and memory resources - with the QuickSizer tool http://sybooks.sybase.com/nav/base.do https://service.sap.com/sizing
https://service.sap.com/bosap-instguides https://service.sap.com/bosap-support https://service.sap.com/quicksizer
PUBLIC
Content Released platforms and technology-related topics such as maintenance strategies and language support Platform Availability Matrix (PAM) Network security High availability Security Unicode SAP systems and their availability Information about Support Package Stacks, latest software versions and patch level requirements
Location https://service.sap.com/pam
https://service.sap.com/securityguide http://scn.sap.com/docs/DOC-7848 https://service.sap.com/security https://service.sap.com/unicode https://service.sap.com/sp-stacks
(*) You need an authorized user ID to access this information. Do you need to register for an SAP Service Marketplace login? Did you forget your password? The following table lists further useful links on SAP Service Marketplace: Content SAP message wizard SAP Notes search SAP Software Distribution Center software download and ordering of software SAP Online Knowledge Products (OKPs) role-specific learning maps Location on SAP Service Marketplace https://service.sap.com/message https://service.sap.com/notes https://service.sap.com/swdc
https://service.sap.com/rkt
1.5
Important SAP Notes
Read the following SAP Notes before you start the installation. These SAP Notes contain the latest information about the installation, as well as corrections to the installation documentation. Make sure that you have the most up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at https://service.sap.com/notes. SAP Note Number
SAP Note 1514967 SAP Note 1848976
Title
SAP HANA: Central Note SAP HANA Appliance Software SPS 06 Release Note
SAP Note Number

SAP Note 1523337 SAP Note 1681092
Title
SAP HANA Database: Central Note Support for multiple SAP HANA databases on a single SAP HANA appliance
SAP Note 1661202 SAP Note 1828400 SAP Note 1577128 SAP Note 1514966 SAP Note 1637145 SAP Note 1793345 SAP Note 1824819 SAP Note 1597355
Support for multiple applications on SAP HANA SAPUI5 tools disappeared after updating HANA Studio Supported clients for SAP HANA SAP HANA: Sizing SAP HANA Database SAP BW on HANA: Sizing SAP HANA Database Sizing for Suite on HANA Optimal settings for SLES 11 SP2 and SLES 11 for SAP SP2 Swap space recommendation for Linux For the SAP HANA system there are no special requirements regarding swap space.
Check the current SAP Notes for the various parts of SAP HANA by searching for any of the following application areas: SAP HANA Platform BC-DB-HDB SAP HANA Database BC-DB-HDB-AFL SAP HANA Application Function Library BC-DB-HDB-AFL-DQ SAP HANA Data Quality Library BC-DB-HDB-AFL-PAL SAP HANA Predictive Analysis Library BC-DB-HDB-AFL-SOP SAP HANA Sales and & Operations Planning BC-DB-HDB-BAC SAP HANA Backup & Recovery BC-DB-HDB-CCM CCMS for SAP HANA BC-DB-HDB-CLI SAP HANA Clients (JDBC, ODBC) BC-DB-HDB-DBA SAP HANA database administration (DBA cockpit) BC-DB-HDB-DXC SAP HANA direct extractor connector BC-DB-HDB-ENG SAP HANA database engine BC-DB-HDB-MDX MDX Engine / MS Excel client BC-DB-HDB-HLM SAP HANA Lifecycle Manager BC-DB-HDB-PER SAP HANA database persistence BC-DB-HDB-PLE Planning Engine BC-DB-HDB-POR DB Porting for SAP HANA BC-DB-HDB-R SAP HANA Integration with R BC-DB-HDB-SCR SAP HANA SQL Script BC-DB-HDB-SCR-CLT SAP HANA SQL Script Editor/Debugger Client
PUBLIC
BC-DB-HDB-SEC SAP HANA Security & User Management BC-DB-HDB-SYS SAP HANA database interface/DBMS BC-DB-HDB-TXT SAP HANA Text & Search Features BC-DB-HDB-XS SAP HANA Application Services BC-DB-HDB-XS-WB Workbench / Team Provider SAP HANA DB BC-DB-LCA SAP HANA liveCache Applications BC-HAN-MOD SAP HANA studio / information modeler BC-HAN-3DM SAP HANA information composer BC-HAN-SRC SAP HANA UI Toolkit BC-CCM-HAG SAP Host Agent SV-SMG-DIA SAP Solution Manager Diagnostics Agent
SAP HANA Lifecycle Management BC-HAN-SL-STP SAP HANA unified installer BC-DB-HDB-INS SAP HANA database installation (hdbinst) BC-HAN-UPD Software Update Manager for SAP HANA BC-DB-HDB-UPG SAP HANA database upgrade (hdbupd)
SAP HANA Enterprise BC-HAN-LOA SAP HANA load controller (log-based replication) BC-HAN-REP Sybase rep. server (log-based replication) BC-HAN-LTR SAP Landscape Transformation (trigger-based replication) BC-HAN-DXC SAP HANA Direct Extractor Connection EIM-DS Data Services (ETL-based replication)
End User Clients BI-BIP, BI-BIP-CMC Business intelligence platform (formerly known as BOE) BI-RA-EXP SAP BusinessObjects Explorer BI-RA-CR, BI-BIP-CRS SAP Crystal Reports BI-RA-XL Dashboard Designer BI-BIP-IDT Information design tool BI-RA-WBI Web Intelligence BI-RA-AO-XLA MS Excel Add-In
The search also supports using the wildcard asterisk (*), so you can, for example, also search for BC-DB-HDB* or similar and you will get results for all sub-components.
Customer Messages
If you encounter any problems with the software, create a customer message on the SAP Service Marketplace at http://service.sap.com/message. In addition, the Customer Interaction Center (CIC) is available 24 x 7 in every region to help you resolve any issues you may run into (https://service.sap.com/supportcenters). The CIC requires a valid S-user number. To create an S-user ID, follow the steps in this guide (https:// service.sap.com/~sapidp/011000358700000905192010E.pdf).
When creating a customer message, you can choose from the above list of components for the relevant software part.
1.6
Software Download
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 such systems is not supported by SAP. For more information, see the information page of the product version. Support Package Stacks (SPS) can be downloaded and applied to appliances according to agreements with the respective hardware partner.
1.6.1
Note
Download Patches and Updates
For more information on applying patches and updates see the section on Change Management. Related Links Change Management [page 14]
1.7
Software Components
The SAP HANA Platform Edition is the foundation of various other SAP HANA editions, like the SAP HANA Enterprise Edition. These editions bundle additional components that customers might require, for example, for data replication. The SAP HANA Platform Edition is composed of the following components: SAP HANA database SAP HANA client SAP HANA client for Microsoft Excel SAP HANA studio SAPUI5 Tools IDE PLUGIN SAP Host Agent Diagnostics Agent SAP HANA information composer SAP HANA AFL SAP HANA LCApps SAP HANA lifecycle manager SAP HANA RDL SAP HANA smart data access SAP HANA INA Toolkit HTML
PUBLIC
SAP HANA unified installer LM structure inst SAP HANA SAP HANA Direct Extractor Connection (DXC)
The SAP HANA Platform Edition is bundled together with other products into editions as license bundles for special purposes. This is a subset of the available editions: SAP HANA Enterprise Edition (containing SAP Data Services and SAP LT Replication Server) SAP Sybase Replication Server, SAP HANA edition Real-time-data edition for SAP HANA (includes SAP Sybase Replication Server, SAP HANA edition) SAP HANA Database edition for BW SAP HANA Limited edition for Apps / Accelerators SAP HANA EDGE edition
Note
SAP HANA information composer is a Web-based environment that allows business users to upload data to the SAP HANA database and to manipulate that data by creating information views. The SAP HANA information composer is installed separately from the SAP HANA system. For more information, see the SAP HANA Information Composer Installation and Configuration Guide.
10
2
2.1
Administering and Operating SAP HANA

Roles and Responsibilities
This section describes the tasks, concepts, responsibilities, and procedures necessary for the ongoing operation of the SAP HANA appliance software. It answers the following questions: Tasks and Responsibilities The following table gives an overview of tasks and who is responsible for the task. What is SAP responsible for and what does SAP support? What do the SAP hardware partners do? What is the customer asked to do? This is explained in more detail in the following sections. Phase
Provisioning/Setup Installation of Hardware Installation of Operating System Installation of SAP HANA Platform Hardware Partner Hardware Partner Hardware Partner
Task
Responsible
Adding additional SAP HANA database Customer instances (MCOS) Data Source Connectivity Maintenance Patching of Firmware Patching of Operating System Patching of SAP HANA platform components Patching of peripheral components Upgrade of Operating System Update of SAP HANA platform components Operations General administration of SAP HANA database Backup and Recovery SAP HANA System Monitoring SAP HANA Database Monitoring Installation of third party software components Support Issue Handling Process Customer (*) Customer (*) Customer Customer Customer (*) Customer Customer Customer Customer Customer Customer Customer Customer SAP, Customer (*), (**) Customer
SAP HANA Technical Operations Manual Administering and Operating SAP HANA
PUBLIC
11
(*) The customer is generally responsible for maintenance of the SAP HANA system. If the customer has a special support agreement with the hardware partner, maintenance may be the responsibility of the hardware partner. (**) SAP is the main point of contact and 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, the customer should contact the hardware partner directly in the case of obvious hardware or operating system issues. If no agreements have been made neither SAP nor the hardware partner are responsible for the installation, maintenance and possible adjustment of external software installed on the SAP HANA system. Schedule - When and how often should each task be performed? What tasks are to be performed during ongoing operation, such as regular checks and periodic tasks? What tasks must be performed on demand and in special situations? Procedures - How can each task be performed? Several tools and transactions can be used for administering and monitoring SAP HANA.
SAP HANA is following the appliance delivery model. Hence it can only be obtained from one of the following certified SAP hardware partners: Hewlett Packard (http://www.hp.com/go/sap/hana) IBM (http://www.ibm.com/solutions/sap/hana) Fujitsu Computers (http://ts.fujitsu.com/hana) CISCO systems (http://www.cisco.com) DELL (http://www.dell.com) Hitachi (http://www.hds.com/solutions/applications/sap-application/sap-hana.html) NEC (http://www.nec.com) Lenovo (http://www.lenovo.com) Huawei (http://enterprise.huawei.com/en/)
For more information on supported software and hardware platforms refer to the SAP Product Availability Matrix (search for "HANA"), the SAP HANA Master Guide on SAP Service Marketplace https://service.sap.com/hana or respective components administration guides at https://help.sap.com/hana.
2.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 Service Marketplace. See SAP Note 1635304.
Note
You need a valid SAP Service Marketplace user to access SMP and related SAP Notes.
12
PUBLIC
2.3
Installation of the SAP HANA Appliance Software
The installation of the SAP HANA appliance software is performed by the SAP hardware partner. Therefore, the SAP hardware partners deliver the SAP HANA appliance software together with corresponding, validated hardware as a prepackaged solution with the most recent support package stack (at the time of shipment of the SAP HANA appliance) to the customer site. The SAP hardware partner may add specific best-practices and SAP HANA software configuration. The installation is finalized by an onsite setup of the SAP HANA components. This includes deploying the SAP HANA system in the customer data center, connectivity to the network, SAP system rename, and SAP Solution Manager connectivity, if applicable. Once the network connection to the SAP HANA system has been established successfully and the SAP HANA system with the most recent support packages is reachable under its desired host name, IP address and SAP system ID from within the customer network, the establishment of data replication/connectivity to data source systems (including the deployment of additional replication components) and the installation of potential BI clients (such as SAP BusinessObjects Explorer on top of BOE) is again the responsibility of the customer or the consulting organization carrying out the SAP HANA project onsite for the customer.
Note
The installation of the SAP HANA server components, in particular the installation of the SAP HANA database shall only be performed by certified hardware partners, on validated hardware, running a specific operating system, as published in the SAP HANA Product Availability Matrix on SAP Service Marketplace (http:// service.sap.com/pam). Any other system or content developed with such systems is not supported by SAP for use in production. SAP HANA studio and clients need to be installed outside of the SAP HANA appliance and can therefore be downloaded and installed by SAP customers directly. Further note, there is a product SAP HANA (platform|enterprise edition), where the SAP HANA database is one component of the product. The product is also comprised of other components. In consequence, do not to use the individual installation tools of the various components to setup a SAP HANA system. The SAP HANA unified installer is the only official tool for installing the SAP HANA product and should always be used to ensure proper system setup. Otherwise Lifecycle Management processes like the Software Update Manager (SUM) for SAP HANA, a tool for updating and patching of the SAP HANA product might fail if the product was not installed completely as a whole.
Installation of additional software

To ensure the smooth operation of an SAP HANA system and to fulfill IT compliances and IT policies, you need to use external software in the SAP HANA appliance. External software is software that was not delivered by SAP or by your HANA appliance hardware partner. SAP permits the installation and operation of external software that is required to fulfill the IT compliance and IT policy that are determined in operation, provided the prerequisites in the following SAP Notes are met. SAP Note Number
1730929
Title
Using external tools in an SAP HANA appliance
PUBLIC
13
SAP Note Number

1730932 1730930
Title
Using backup tools with Backint Using antivirus software in an SAP HANA appliance
Each of these SAP Notes refers to additional documentation about software and software versions that, in the experience of SAP Support, have caused problems in the customer environment or in the laboratories of SAP or the hardware suppliers and are therefore not recommended for use in the HANA appliance. Neither SAP nor the hardware supplier of your HANA appliance are responsible for the installation, maintenance and possible adjustment of the external software if no agreements have been made for this purpose.
2.4
Change Management
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 (e.g. Consulting, Development, or Support). To guarantee optimal performance and the highest stability SAP HANA appliance Hardware partners can deliver systems with properties that differ from the standard. Changes to operating system parameters and ports are only allowed with the agreement of the hardware partner that provided your SAP HANA appliance. SAP Note 1731000 describes configuration changes that resulted in problems in customer environments and in SAP or hardware partner lab environments.
2.5 2.5.1
Software Maintenance Updating and Patching the Operating System
The initially delivered configuration of the operating system should persist. If configuration settings are subsequently changed, significant performance problems may occur. The customer can request a validation of configuration changes for the operating system and for the installation of additional operating system components by the hardware partner depending on the service contract between the hardware partner and the customer. The hardware partner then supports these changes and additional components in accordance with the existing service contract with the customer. No modified Linux version can be used. 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.
14
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. For all other operating system patches, the customer should wait until they are officially released for SAP HANA via a corresponding SAP Note before the operating system is updated with the patches in question. In particular, 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. OS security patches may be imported 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. For more information, see SAP Note 1056161 - SUSE Priority Support for SAP applications and SAP Note 171356 SAP software on Linux: Essential information (SAP Service Marketplace user required).
2.5.2
Updating and Patching SAP HANA Appliance Software
The SAP hardware partners ship SAP HANA pre-configured and with the most recent support package stack at the time when the SAP HANA appliance is shipped. 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 package 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 the customer 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.
PUBLIC
15
New SAP HANA support packages and patches will be produced and shipped at SAPs 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 lifecycle manager, which is the successor to the SAP Software Update Manager (SUM) for SAP HANA. SAP HANA lifecycle manager covers all scenarios previously covered by the SUM (SAP HANA system update, single SAP HANA component updates and deployment of SAP HANA application content), the SAP HANA On-Site configuration tool (renaming SAP HANA systems, adding additional SAP HANA systems, registration in a System Landscape Directory) and can be used to configure SAP Landscape Transformation (LT). SAP HANA lifecycle manager is automatically installed with SAP HANA Unified Installer, as part of the SAP HANA appliance installation. You can access the tool in SAP HANA studio. An additional command line interface is also be available. The following scenarios are supported: SAP HANA standalone maintenance (online): In the SAP HANA studio, start the lifecycle management perspective to set up a connection to the SAP Service Marketplace, automatically download the requested SAP HANA SP-Stack to your SAP HANA system and apply the update. SAP HANA standalone maintenance (offline): Download the requested SP-Stack in advance from SAP Service Marketplace and make it available to your SAP HANA system. In the SAP HANA studio, enter the location of the downloaded SP-Stack and proceed directly with implementing the update. SAP Solution Manager based maintenance: Use Maintenance optimizer in your local SAP Solution Manager to calculate and download SP-Stack in advance and make it available to your SAP HANA system. In the SAP HANA studio, enter the location of the downloaded SPS and proceed with applying the update. For more information, see the SAP HANA Master Update Guide. Additionally see Backing Up and Recovering the SAP HANA Database in the SAP HANA Administration Guide.
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). For the most current information on SAP HANA support packages and patches, see SAP Note 1514967 SAP HANA 1.0: Central Note (SAP Service Marketplace user required). Up to now there are no known dependencies between SAP HANA support package stacks and the SAP HANA hardware and installed firmware. The process for implementing SAP HANA support packages is described on SAP Service Marketplace at https://service.sap.com/ hana (SAP Service Marketplace user required).
Note
Special support agreements may exist with the hardware partner which include services such as patching.
2.5.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.
16
2.5.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.
2.5.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.
2.6
Monitoring the SAP HANA Database
The SAP HANA database can be monitored with the SAP HANA studio. It enables you to check if your SAP HANA system runs as expected and provides possibilities to analyze problems. The SAP HANA studio also houses the SAP HANA modeler and the user management for the SAP HANA database. SAP Solution Manager can be used for basic administration and monitoring of HANA systems within existing SAP landscapes. It is used by SAP support for early problem analysis and as backbone for CTS+ transport integration. SAP HANA also integrates with SAP Landscape and Virtualization Manager (LVM) for basic operation of larger/ more complex SAP landscapes (including starting and stopping and management of dependencies). For more information, see the section Monitoring SAP HANA Systems in the SAP HANA Administration Guide.
2.6.1 Integrating SAP HANA into a Central Operations Concept

SAP HANA and SAP HANA-based applications are supported by SAP Solution Manager. If you already use SAP Solution Manager, the effort for integrating SAP HANA into your existing operations concept is relatively low. You can use its functions for SAP HANA related activities.
Note
SAP recommends to update your SAP Solution Manager to release 7.1, SP05 or higher to optimize the support for SAP HANA. Using SAP Solution Manager for SAP HANA
PUBLIC
17
SAP Solution Manager documentation SAP Solution Manager homepage on SMP Knowledge transfer by Online Knowledge Products SAP Solution Manager SCN community
Note
You need an authorized user ID to access this information. Do you need to register for an SAP Service Marketplace login? Did you forget your password?
2.6.1.1
Connecting SAP Solution Manager to SAP HANA
If you want to use capabilities of SAP Solution Manager, you have to make sure that the two systems know each other. Prerequisite for this is the registration of the SAP HANA system in the System Landscape Directory. From there, SAP Solution Manager gets the information that the SAP HANA system exists. The communication between the systems is based on a central agent infrastructure. The pre-configured agents are delivered by SAP and deployed on the SAP HANA appliance by the hardware partner. The configuration of the connection itself is done as part of the basic configuration of SAP Solution Manager. In the guided procedure for Managed Systems Configuration you just need to set up the correct connection, assign the right agents, enter some parameters, create required users, and do a few more configurations. After this, you can start the collaboration of SAP HANA and SAP Solution Manager. Some of the processes in SAP Solution Manager require additional configuration to specify how they should handle the SAP HANA database. For example, you have to specify in system monitoring which metrics you want to control. Or you have to define your transport landscape (development system -> quality assurance system -> productive system) for change control. Related Links SAP Note 1747682: Managed System Setup for HANA
2.6.1.2
Central Monitoring and Administration
The monitoring and alerting infrastructure of SAP Solution Manager is based on a central agent infrastructure. SAP delivers pre-configured agents for SAP HANA. If these agents have been deployed on SAP HANA and have been connected to SAP Solution Manager, SAP Solution Manager receives all alerts of the HANA DB Studio. These alerts will be displayed in the unified alert inbox. SAP Solution Manager also provides an automated regular status check of your SAP solutions: SAP EarlyWatch Alert (EWA). This tool monitors the essential administrative areas of SAP components and keeps you up to date on their performance and stability. If you have any ABAP-based system besides or on SAP HANA, you can include the SAP HANA database information into the EWA report of this system: Availability of services; size and growth; performance; important alerts; and correct setting of configuration parameters. Besides basic administration tasks, SAP provides specific task lists for SAP HANA, SAP NetWeaver Business Warehouse (BW) on HANA, and SAP LT (Landscape Transformation) Replication Server. These lists describe additional activities for administering these components and provide best practices for individual tasks.
18
PUBLIC
2.6.1.3
Analyzing the Root Cause of Problems
Often, SAP HANA systems are integrated with business applications that either call application accelerators in the SAP HANA database or are deployed on the database. If a problem occurs in this setup, you have to take a systematic approach to identify the precise cause of the fault. This standardized process must first broadly identify the components concerned and then analyze them more closely to arrive at the cause of the fault by process of elimination (top-down approach). End-to-end root cause analysis in SAP Solution Manager provides your support organization with tools and methods that reliably identify the affected component while minimizing the time needed to solve the problem. Besides your business applications, it supports also your SAP HANA database. This is the foundation for resolving problems in a holistic approach. The DBA Cockpit is used in SAP Solution Manager to get a detailed insight into the status of the database. Basically, this is about the same data that you can see in the SAP HANA Studio for your in-memory database. But the DBA Cockpit supports other databases as well. If you have heterogeneous databases in your environment because your business applications still run on traditional databases, the DBA Cockpit enables you to use the same tool for the different databases. Trace analysis records performance-related and functional faults in a specific user activity from the users browser to the data stored in memory or on a storage sub-system. The measurement is triggered in the user interface and automatically activates recording of the relevant traces on every component processed by the user query. After the root cause of a problem has been located, you can use detailed analysis to find a resolution. Workload analysis comprises server-related workload statistics for the connected systems. Exception analysis allows you to centrally analyze all exceptions from connected systems, such as serious error messages in logs or dumps. From here, you can start component-specific tools. And change analysis creates transparency for all changes (technical configuration, code, content) that have been made in the connected system landscape. This is particularly useful in the event of faults that occur once changes have been made to the production landscape.
2.6.1.4
Controlling Change
In integrated system landscapes, it is important to manage all changes in a central system. This is the only way to synchronously execute changes that affect more than one production system. For example, if you use SAP HANA application-specific accelerators (for example, CO-PA) in combination with your SAP ERP back-end, you might need to synchronize changes of the data models on SAP HANA with changes for accessing the changed models from the transactions on SAP ERP. SAP Solution Manager provides central transport functions for the entire system landscape as well as additional support for quality management. The process for transporting changes from a SAP HANA development system to a quality assurance and further on to the productive system starts in SAP HANA Studio. There you retrieve content from the HANA source system and export it to enhanced Change and Transport System (CTS+) in SAP Solution Manager. The exported delivery units are attached automatically to a transport request of CTS+. After you have released this transport request, CTS+ triggers the automatic activation of the change in the SAP HANA repository on the target system (quality assurance or production). Besides supporting the transport and activation of new or changed data models, views, stored procedures, or analytic privileges, SAP Solution Manager offers additional possibilities to improve the quality of changes. You can use change analysis and reporting for getting information about the current status and history of changes.
PUBLIC
19
Configuration validation checks whether the systems of your system landscape (for example, development, quality assurance, and production) are configured consistently and according to the requirements. Quality Gate Management provides an additional quality inspection for projects and ensures changes are transported correctly and synchronously to the production systems. And Change Request Management within SAP Solution Manager controls the entire change execution with detailed process and workflow control. Out of these options, you can select those for controlling changes on SAP HANA that fit best to the quality strategy of your organization. Related Links CTS+ How To Guide on SCN
2.7
Administering the SAP HANA Database
You administer the SAP HANA database using the administration console perspective of the SAP HANA studio. The administration console perspective of the SAP HANA studio allows technical users to manage the SAP HANA database as well as to create and manage user authorizations. For more details, see the SAP HANA Administration Guide For further reference information, see: SAP HANA SQL Reference SAP HANA Database System Views Reference
Related Links SAP HANA Administration Guide SAP HANA SQL Reference SAP HANA Database System Views Reference
2.7.1
Initial Administrative Tasks
It is strongly recommended after the initial setup and after the initial load, that you perform a full data and filesystem backup (including a configuration backup). For more information, see the section Backing Up and Recovering the SAP HANA Database in the SAP HANA Administration Guide. Related Links SAP HANA Administration Guide
2.7.2
Regular Administrative Tasks
Regularly check the system status on the Overview tab page of the administration editor in SAP HANA studio. This displays the most important system information: Overall system state General system information (software versions and so on).
20
The Alerts section shows the latest warnings and messages generated by the statistics server, which is a monitoring tool for the database. It collects statistical and performance information using SQL statements. The bar views provide an overview of important system resources: the amount of available memory, CPUs and storage space is displayed as well as the used amount of these resources. In a distributed landscape, the amount of available resources is aggregated over all servers. Additionally, the resource information of the server with the highest resource consumption is displayed.
The Services tab page (under the Landscape tab) of the administration screen in SAP HANA studio, lets you check that all services belonging to your system are running: preprocessor, name server and index server for each host and one statistics server. A statistics server exists on each host of a distributed landscape; however, the service actually runs on the master host only. Running services are indicated by a green icon. Information about resource usage and possible bottlenecks is also displayed. Regularly perform data backups including configuration backups. There are no general guidelines for backup frequency (this depends on the usage scenario). For more information, see the section Backing Up and Recovering the SAP HANA Database in the SAP HANA Administration Guide.
Related Links SAP HANA Administration Guide
2.7.3

On Demand Administrative Tasks
In case of problems with the SAP HANA database, you can check log and trace files for errors. These log files are available in the SAP HANA studio on the Diagnosis Files tab page of the administration screen. You can turn on and configure several traces from the Trace Configuration tab. For more details see Configuring Traces in the SAP HANA Administration Guide. In certain situations, you have to restart the system (for example, after a power failure). This can be done using the SAP HANA Systems view of the SAP HANA studio. After confirming the restart, you need to enter the operating system user and password before the system is actually restarted. For more details see the SAP HANA Administration Guide. Avoiding LOG FULL (file system full) situations When the log is backed up, the backed up log segments remain on disk until they have been released automatically after a savepoint. After the log has released, the oldest unused log segment can be overwritten with new log entries. If there are no unused log segments, new log segments are created. If the disk becomes full and no more log segments can be created, a log full situation arises. When the log is full, no more logging is possible until the log backup has completed. Automatic log backup prevents log full situations from arising. For more information, see the section Backing Up and Recovering the SAP HANA Database in the SAP HANA Administration Guide. Avoid log backup area becoming full. Regularly archive old log backups to a different location (using operating system commands). Monitor disk space that is used for diagnosis files (these files record errors and changes in system behavior) and can be viewed on the Diagnosis Files tab in SAP HANA studio. We recommend using SAP HANA studio to delete diagnosis files that are no longer needed.
Caution
Do not delete log segments on the operating system level, as the log area will become unusable and the database may stop working.
PUBLIC
21
Before the SAP HANA database or SAP HANA software is upgraded to a new version, perform a data backup including a configuration backup. This allows for the recovery of the system in case the software upgrade fails. After the initial load has finished successfully, a data backup is strongly recommended. For more information, see the section Backing Up and Recovering the SAP HANA Database in the SAP HANA Administration Guide.
Note
For replication scenarios during the initial data load - from ERP into the SAP HANA database log writing should not be switched off.
Note
There is no system table or log file that records the information that log writing has been switched off. For this reason, SAP does not recommend switching off the log during initial load. It is not possible to check when log writing has been switched OFF/ON on customer systems. Related Links SAP HANA Administration Guide
2.8
Backup and Recovery
The backup and recovery functionality in SAP HANA is quite straightforward. The payload of all data volumes of all services (name server, index server, statistics server) that belong to a database is written to service-specific backups. Backups can be written to the file system or using a third-party backup tool. An administrator can back up the database with only a few clicks and the system does the rest automatically: all the relevant service-specific data is backed up, regardless of whether your system has a single node or multiple nodes.
In-Memory Data and Persistent Storage

The SAP HANA database holds the bulk of its data in memory for maximum performance, but still uses persistent storage to provide a fallback in case of failure. During normal database operation, data is automatically saved from memory to disk at regular savepoints. Additionally, all data changes are captured in the redo log. With each committed database transaction, the redo log is saved from memory to disk and also log backups for SAP HANA are available. If a failure occurs, for example a power outage, the database can be restarted in the same way as any disk-based database, and it is returned to its last consistent state by replaying the redo log since the last savepoint.
22
PUBLIC
Recovery
Using data and log backups (and if available log entries from the log volumes), the SAP HANA database can be recovered. A recovery may be necessary in one of the following situations: Data area is unusable Log area is unusable Logical error
Note
The recovery process of the SAP HANA database causes the database to be shut down. During recovery, the system is therefore not accessible for end-users or applications. For more information, see the section Backing Up and Recovering the SAP HANA Database in the SAP HANA Administration Guide. Related Links SAP HANA Administration Guide
2.9
Security
How you implement SAP HANA determines what you need to consider from a security perspective. SAP HANA can be implemented in the following main ways: As a data mart for reporting and analytics As the primary database in a traditional 3-tier architecture, for example, in SAP NetWeaver Business Warehouse (SAP NetWeaver BW) or SAP Business Suite installations As a platform for providing database and application services to native SAP HANA-based applications
For more information about the security-relevant information that applies to SAP HANA in your scenario, see the SAP HANA Security Guide. Related Links SAP HANA Security Guide
2.9.1
Security Features and Functions
SAP HANA provides security-related features that enable you to implement different security policies and meet compliance requirements. Depending on the scenario in which SAP HANA is used, only some of these features might actually be needed, others might be provided in other architecture layers. SAP HANA supports standard interfaces to enable integration with customer security network and data center infrastructures.
PUBLIC
23
Authentication and Single Sign-On (SSO)

The identity of every database user accessing the database is verified through a process called authentication. The SAP HANA database supports several authentication mechanisms: SQL access: User name and password (including password policy), Kerberos, Security Assertion Markup Language (SAML bearer token) HTTP access (SAP HANA XS): User name and password (including password policy), SAP logon tickets, SAML, and X.509 certificates SAP HANA never stores passwords in plain text. To enforce password quality, a password policy can be defined for user name/password access.
User and Role Management

Every user who wants to work directly with the SAP HANA database must have a database user with the necessary privileges.
24
Depending on the scenario, the user accessing the SAP HANA database may either be a technical user or an individual end user. Independent of the SAP HANA scenario, there will always be direct access to SAP HANA by database administrators. For user and role management, you can use either the SAP HANA studio or SQL commands.
Authorization
All access to data and execution of actions in the database requires authorization. The user must have both the privilege(s) to perform the operation and the privilege(s) to access the object (for example, a table) to which the operation applies. Privileges can be granted to database users either directly, or indirectly through roles. A role is a set of privileges. Roles are the standard mechanism of granting privileges as they allow you to implement both fine-grained and coarse-grained reusable hierarchies of user access that can be modeled on business roles. Several standard roles are also delivered with the SAP HANA database (for example, MODELING, MONITORING). You can use these as templates for creating your own roles. It is also possible to create roles as design-time objects in the repository of the SAP HANA database. There is a privilege concept for both design time (developer use case) and runtime. The following privilege types exist: System privileges: Authorize execution of administrative actions for the entire SAP HANA database SQL privileges: Authorize access to data and operations on database objects Analytic privileges: Authorize read access to analytic views at runtime and provide row-level access control based on the dimensions of the relevant view Package privileges: Authorize access in the repository (modeling environment) at design time Application privileges: Authorize access to SAP HANA XS application functions
Secure Communication
Network traffic can be encrypted using SSL (v.3), both between the SAP HANA database and clients, as well as between hosts in a distributed SAP HANA system.
Encryption
The SAP HANA database can encrypt data at rest (data volumes). Encryption works at the page level and uses the AES256 encryption algorithm.
PUBLIC
25
Auditing
The auditing feature of the SAP HANA database allows you to track actions performed in the database: who did what (or tried to do what), and when. SAP HANA provides audit actions for critical security events and for access to sensitive data. Both successful and unsuccessful events can be logged. The audit trail is written to Linux syslog. Auditing can be configured in SAP HANA studio or using SQL statements. Auditing can be enabled and disabled for the entire database only. Audit policies define which actions in the database are logged: They can be explicitly enabled or disabled. Audited user(s) can be specified. They are stored in the database catalog.
Security Administration
Many security-related features are integrated into the SAP HANA studio, for example, user and role management, definition of analytic privileges, creation of audit policies, and configuration of password policy. Most administration tasks can also be carried out using SQL commands.
Application Services Security

The security concept of SAP HANA XS is fully integrated with the SAP HANA security model. User and role management: SAP HANA database users and privileges/roles are used. Authorization: User needs access to SAP HANA database objects. To provide even finer grained access control in SAP HANA XS, application privileges can also be defined. Authentication and single sign-on: User name and password, SAP logon tickets, SAML, X.509 certificates Communication encryption: Secure Sockets Layer (SSL) Data encryption: Inherits SAP HANA data volume encryption Audit logging: The SAP HANA audit logging infrastructure is used.
There are additional functions available to secure Web applications developed on SAP HANA XS, including protection against XSRF, SQL injection, and XSS,
2.9.2
Data Center Integration
SAP HANA supports standard interfaces to enable integration with customer security network and data center infrastructures. There is detailed information available for secure set-up of the SAP HANA appliance and network integration.
26
Operating System
SAP HANA is based on SUSE Linux Enterprise 11 for SAP and includes security pre-configurations (for example, minimal network services). The SAP HANA database runs with a restricted operating system user. Operating system access using SSH, for example, is not required for the day-to-day operations of SAP HANA.
Security Patches
SAP HANA security patches are published as part of the general SAP security patch strategy (SAP Security Notes). SAP HANA security patches are delivered as SAP HANA revisions and can be applied via SUM for SAP HANA. Operating system security patches are provided and published by SUSE and can be applied by customers as soon as they become available.
PUBLIC
27
Network Integration
Network communication (purpose, ports) used by SAP HANA are documented in the SAP HANA Security Guide and in the SAP HANA Master Guide. This guide includes recommendations for the use of firewalls and how to separate internal and external communication. SSL is supported for network communication channels. Related Links SAP HANA Security Guide SAP HANA Master Guide
2.9.3
Compliance
SAP HANA takes an end-to-end approach to enable application compliance. This is based on the built-in database security features and the secure pre-configuration of the whole software stack (for example, operating system). This is extended by integration with existing security infrastructures via standard/documented interfaces and the option to use third-party tools that are required for data center operations. This is complemented by an end-toend documentation covering the whole software life cycle, including an exhaustive security guide and recommendations for a secure setup.
28
PUBLIC
Deletion
As part of the technical infrastructure for applications, SAP HANA provides delete functions for records in all types of tables. These functions can be leveraged by applications to implement their specific deletion requirements.
2.10 High Availability for SAP HANA

SAP HANA is fully designed for high availability. It supports recovery measures ranging from faults and software errors, to disasters that decommission an entire data center. High availability is the name given to a set of techniques, engineering practices and design principles that support the goal of business continuity. This is achieved by eliminating single points of failure (fault tolerance), and providing the ability to rapidly resume operations after a system outage with minimal business loss (fault resilience). Fault recovery is the process of recovering and resuming operations after an outage due to a fault. Disaster recovery is the process of recovering operations after an outage due to a prolonged data center or site failure. Preparing for disasters may require backing up data across longer distances, and may thus be more complex. The key to achieving high availability is redundancy, including hardware redundancy, network redundancy and data center redundancy. SAP HANA provides several levels of defense against failure-related outages: 1. Hardware Redundancy SAP HANA appliance vendors offer multiple layers of redundant hardware, software and network components, such as redundant power supplies and fans, enterprise grade error-correcting memories, fully redundant network switches and routers, and uninterrupted power supply (UPS). Disk storage systems use batteries to guarantee writing even in the presence of power failure, and use striping and mirroring to provide redundancy for automatic recovery from disk failures. Generally speaking, all these redundancy solutions are transparent to SAP HANA's operation, but they form part of the defense against system outage due to single component failures. Software SAP HANA is based on SUSE Linux Enterprise 11 for SAP and includes security pre-configurations (for example, minimal network services). Additionally, the SAP HANA system software also includes a watchdog function, which automatically restarts configured services (index server, name server, and so on), in case of detected stoppage (killed or crashed). Persistence SAP HANA persists transaction logs, savepoints and snapshots to support system restart and recovery from host failures, with minimal delay and without loss of data. Standby and Failover Separate, dedicated standby hosts are used for failover, in case of failure of the primary, active hosts. This improves the availability by significantly reducing the recovery time from an outage.
2.
3. 4.
SAP HANA High Availability Support

As an in-memory database, SAP HANA is not only concerned with maintaining the reliability of its data in the event of failures, but also with resuming operations with most of that data loaded back in memory as quickly as possible. SAP HANA supports the following recovery measures from failures: Disaster recovery support:
PUBLIC
29
Backups: Periodic saving of database copies in safe place. Storage replication: Continuous replication (mirroring) between primary storage and backup storage over a network (may be synchronous). System replication: Continuous update of secondary system by primary system, including in-memory table loading. Service auto-restart: Automatic restart of stopped services on host (watchdog). Host auto-failover: Automatic failover from crashed host to standby host in the same system.
Fault recovery support:
Using Secondary Servers for Non-Productive systems

With SAP HANA system replication you can use the servers on the secondary system for non-productive SAP HANA systems under the following conditions: Table pre-load is turned off in the secondary system. The secondary system uses its own disk infrastructure. In the case of single node systems this means, the local disk infrastructure needs to be doubled. The non-productive systems are stopped with the takeover to the productive secondary.
Related Links SAP HANA Administration Guide
30
3 Administering and Operating SAP HANA Data Provisioning Technologies

3.1 3.1.1 SAP HANA Data Provisioning Technologies SAP Sybase Event Stream Processor
SAP Sybase Event Stream Processor is used for real-time processing of high velocity and high volume data streams modeled as event streams. It is targeted for a variety of applications, for example for financial trade and risk monitoring, monitoring machine/sensor data, and tailoring responses to user actions. Input data streams can come from a variety of sources such as data feeds, business applications, sensors, IT monitoring infrastructure, and so on. You can develop custom input adapters for additional sources. ESP transforms the input data streams into output data streams by applying event-driven continuous queries. It can be used, for example, to filter, aggregate and enrich raw data, to detect patterns, and to combine data from different sources. ESP can capture output streams in the SAP HANA database at very high speeds. For details see the SAP Sybase Event Stream Processor documentation on the Sybase product documentation page. Related Links Sybase Product Documentation
3.1.2
SAP HANA Smart Data Access
SAP HANA smart data access enables remote data to be accessed as if they are local tables in SAP HANA, without copying the data into SAP HANA. Not only does this capability provide operational and cost benefits, but most importantly it supports the development and deployment of the next generation of analytical applications which require the ability to access, synthesize and integrate data from multiple systems in real-time regardless of where the data is located or what systems are generating it. Specifically, in SAP HANA, you can create virtual tables which point to remote tables in different data sources. Customers can then write SQL queries in SAP HANA, which could operate on virtual tables. The SAP HANA query processor optimizes these queries, and executes the relevant part of the query in the target database, returns the results of the query to SAP HANA, and completes the operation. Related Links SAP HANA Security Guide (see "Secure Storage of Passwords in SAP HANA" and "Secure Internal Credential Store") SAP HANA Administration Guide (see "About SAP HANA Smart Data Access") SAP Note 1868209: Additional information about SPS06 and smart data access SAP Note 1868702: Information about installing the drivers that SAP HANA smart data access supports
SAP HANA Technical Operations Manual Administering and Operating SAP HANA Data Provisioning Technologies
PUBLIC
31
3.1.3 3.1.3.1
SAP HANA Replication Technologies Introduction
In-memory reporting and analyzing of business data requires the replication of the data from a source system to the SAP HANA database. This section provides an overview of the possible replication methods that are available for the SAP HANA appliance. It also describes the application fields and lists the main components required for each method.
The figure above focuses on the task of loading business data from a source system to the SAP HANA database. The methods for performing data replication are shown in the figure below. The main components involved in all replication scenarios are: SAP HANA appliance, consisting of the SAP HANA database and SAP HANA studio, which is used to administer the appliance. User interfaces, such as SAP BusinessObjects Dashboards or Web Intelligence, are not part of the appliance software. Source system Software components supporting the data replication
The software components that support different methods of data replication are described in the following replication scenarios.
32
PUBLIC
The figure above gives an overview of the alternative methods for data replication from a source system to the SAP HANA database. Each method handles the required data replication differently, and consequently each method has different strengths. It depends on your specific application field and the existing system landscape as to which of the methods best serves your needs. Trigger-Based Replication Trigger-Based Data Replication Using SAP Landscape Transformation (LT) Replication Server is based on capturing database changes at a high level of abstraction in the source ERP system. This method of replication benefits from being database-independent, and can also parallelize database changes on multiple tables or by segmenting large table changes. ETL-Based Replication Extraction-Transformation-Load (ETL) Based Data Replication uses SAP Data Services to specify and load the relevant business data in defined periods of time from an ERP system into the SAP HANA database. You can reuse the ERP application logic by reading extractors or utilizing SAP function modules. In addition, the ETL-based method offers options for the integration of third-party data providers. Extractor-Based Data Acquisition The SAP HANA Direct Extractor Connection (DXC) is a means for providing out-of-the-box foundational data models to SAP HANA, which are based on SAP Business Suite entities. DXC is also a data acquisition method. The rationale for DXC is essentially simple, low TCO data acquisition for SAP HANA leveraging existing delivered data models. Log-Based Replication (for non-SAP systems)
PUBLIC
33
SAP Sybase Replication Server (SRS) is a sophisticated transactional data movement product that moves and synchronizes data across the enterprise without the limitation of geographical distance, to meet demanding requirements in the enterprise such as guaranteed data delivery, real-time business intelligence and zero operational downtime. SRS facilitates this by non-intrusively handling data at the source and target, while ensuring high performance and transactional integrity. Related Links Product Availability Matrix (PAM) (search for SAP HANA)
3.1.3.2 Trigger-Based Replication (SAP Landscape Transformation (LT) Replication Server)

The Trigger-Based Replication method uses the SAP Landscape Transformation (LT) Replication Server component to pass data from the source system to the SAP HANA database target system.
Initial Load and Simultaneous Delta Replication The initial load of business data is initiated using the SAP HANA studio. The initial load message is sent from the SAP HANA system to the SLT system, which in turn passes the initialization message to the ERP system. Furthermore, the SLT system initiates the set-up of replication log tables in the database of the ERP system for each table to be replicated. After the transaction tables are completed, the SLT system begins a multi-threaded replication of data to the target system, which enables high speed data transfer.
34
The initial load of data can be executed while the source system is active. The system load that this process causes can be controlled by adjusting the number of worker threads performing the initial replication. In parallel to the initial load, by means of database-specific triggers, the SLT system begins detecting any data changes that occur while the initial load process is running. These changes are already recorded in logging tables during the initial load phase and are propagated during the replication phase to the target SAP HANA system after the initial load has been completed. The multi-version concurrency control (MVCC) of the SAP HANA database prevents issues that might be caused by the overlapping of the initial load process and new database transactions Continuous Delta Replication After Initial Load After the initial load process has completed, the SLT system continues to monitor the transaction tables in the ERP system, and replicates data changes in the source system to the SAP HANA system in near real time. Required Software Components This replication method requires the following component: SAP Landscape Transformation: this controls the entire replication process by triggering the initial load and coordinating the delta replication.
Installation considerations The SLT system can be installed in the ways shown below. You can select between these options depending on your current system landscape and the software versions in your landscape: Installation on your ERP system Installation on a standalone SAP system (recommended setup)
Related Links SAP HANA Installation Guide Trigger-Based Replication (SLT)
3.1.3.3
SAP HANA Direct Extractor Connection (DXC)
The SAP HANA Direct Extractor Connection (DXC) is a means for providing out-of-the-box foundational data models to SAP HANA, which are based on SAP Business Suite entities. DXC is also a data acquisition method for SAP HANA. The rationale for DXC is essentially simple, low TCO data acquisition for SAP HANA leveraging existing delivered data models. Customer projects may face significant complexity in modeling entities in SAP Business Suite systems. In many cases, data from different areas in SAP Business Suite systems requires application logic to appropriately represent the state of business documents. SAP Business Content DataSource Extractors have been available for many years as a basis for data modeling and data acquisition for SAP Business Warehouse; now with DXC, these SAP Business Content DataSource Extractors are available to deliver data directly to SAP HANA. DXC is a batch-driven data acquisition technique; it should be considered as a form of extraction, transformation and load although its transformation capabilities are limited to user exit for extraction. A key point about DXC is that in many use cases, batch-driven data acquisition at certain intervals is sufficient (for example, every 15 minutes).
PUBLIC
35
Overview of the DXC Rationale

Leverage pre-existing foundational data models of SAP Business Suite entities for use in SAP HANA data mart scenarios: Significantly reduces complexity of data modeling tasks in SAP HANA Speeds up timelines for SAP HANA implementation projects Ensures that data appropriately represents the state of business documents from ERP Application logic to give the data the appropriate contextual meaning is already built into many extractors Re-uses existing proprietary extraction, transformation, and load mechanism built into SAP Business Suite systems over a simple http(s) connection to SAP HANA No additional server or application needed in system landscape Efficient data acquisition only bring new or changed data into SAP HANA DXC provides a mechanism to properly handle data from all delta processing types
Provide semantically rich data from SAP Business Suite to SAP HANA:
Simplicity/Low TCO:
Change data capture (delta handling):
Default DXC Configuration for SAP Business Suite

DXC is available in different configurations based on the SAP Business Suite system: The default configuration is available for SAP Business Suite systems based on SAP NetWeaver 7.0 or higher such as ECC 6.0. The alternative configuration is available for SAP Business Suite systems based on releases lower than SAP NetWeaver 7.0 such as SAP ERP 4.6, for example.
An SAP Business Suite system is based on SAP NetWeaver. As of SAP NetWeaver version 7.0, SAP Business Warehouse (BW) is part of SAP NetWeaver itself, which means a BW system exists inside SAP Business Suite systems such as ERP (ECC 6.0 or higher). This BW system is referred to as an embedded BW system. Typically, this embedded BW system inside SAP Business Suite systems is actually not utilized, since most customers who run BW have it installed on a separate server, and they rely on that one. With the default DXC configuration, we utilize the scheduling and monitoring features of this embedded BW system, but do not utilize its other aspects such as storing data, data warehousing, or reporting / BI. DXC extraction processing essentially bypasses the normal dataflow, and instead sends data to SAP HANA. The following illustration depicts the default configuration of DXC.
36
An In-Memory DataStore Object (IMDSO) is generated in SAP HANA, which directly corresponds to the structure of the DataSource you are working with. This IMDSO consists of several tables and an activation mechanism. The active data table of the IMDSO can be utilized as a basis for building data models in SAP HANA (attribute views, analytical views, and calculation views). Data is transferred from the source SAP Business Suite system using an HTTP connection. Generally, the extraction and load process is virtually the same as when extracting and loading SAP Business Warehouse you rely on InfoPackage scheduling, the data load monitor, process chains, etc. which are all well-known from operating SAP Business Warehouse.
Note
DXC does not require BW on SAP HANA. Also with DXC, data is not loaded into the embedded BW system. Instead, data is redirected into SAP HANA. Related Links SAP HANA Direct Extractor Connection Implementation Guide Editing DataSources and Application Component Hierarchies
PUBLIC
37
Enhancing DataSources
3.1.3.4
ETL-Based Replication (SAP Data Services)
Extraction-Transformation-Load (ETL) based data replication uses SAP Data Services (referred to as Data Services from now on) to load the relevant business data from the source system, SAP ERP, and replicate it to the target, SAP HANA database. This method enables you to read the required business data on the level of the application layer. You deploy this method by defining data flows in Data Services and scheduling the replication jobs. Since this method uses batch processing, it also permits data checks, transformations, synchronizing with additional data providers, and the merging of data streams.
The figure above gives an overview of the ETL-based replication method. Here, data replication is operated by Data Services. Its main components are the Data Services Designer, where you model the data flow, and the Data Services Job Server for the execution of the replication jobs. An additional repository is used to store the metadata and the job definitions. Data Flow As for any replication scenario you have to define a series of parameters for the two systems involved. Utilizing Data Services you have to set up datastores to define such parameters. You use the Designer to set up datastores. Datastore Setup
38
PUBLIC
Setting up a datastore for the source system SAP ERP, choose SAP Applications for the type of datastore, and specify the address of the system, the user name and password allowing Data Services to access the system. Additional settings depend on the type of SAP ERP objects to be read. For the target system of the replication, the SAP HANA database, you have to set up a separate datastore as done for the source system. Data Flow Modeling Once datastores are set up, Data Services can connect to the source system by RFC. Based on the metadata imported from the ABAP Data Dictionary to Data Services, you can determine the business data to be replicated. Data Services offers replication functions for a variety of data source types. However, for the replication of SAP ERP data to SAP HANA database, we recommend you to use extractors.
Note
You must applySAP Note 1522554 to fully benefit from the extractor support. In the source system, the extractors must be released for the replication access by Data Services. In addition, you have to indicate the primary key, such as the GUID, to enable the correct replication. The extractors must support delta handling.
Choose the extractors that are relevant for the replication job. Model the data flow for each extractor you have selected: indicate the source for the data flow, which is the extractor. For the target of the replication, choose a template table, which is then used in the SAP HANA database to store the replaced data. Data Flow for Initial Load and Update Both the initial load of business data from the source system into SAP HANA database as well as updating the replicated data (delta handling) is done using SAP Data Services. The initial load can be set up modeling a simple data flow from source to target. For the update, in most cases, the data flow is enhanced by a delta handling element, such as Map_CDC_Operation or Table_Comparison Transform. It depends on the environment and the requested setup of the target tables which data flow design best serves your requirements. Although we recommend you to use delta supporting extractors, you can also use SAP ABAP tables. Replication Job Schedule Since you can schedule the replication jobs when using Data Services, this method is suitable where the source system must be protected from additional load during the main business hours. In this way, you can shift the replication workload, for example, to the night. As a result, the data that is available for reporting always represents the state reached by the time when the latest replication job was started. Use the Management Console, which comes with Data Services, to schedule replication jobs. You can choose from different tools and methods for the scheduling. You can also use the Management Console to monitor the replication process. Required Software Components This replication method requires the following main components: SAP HANA database SAP Data Services (contains Information Platform Services)
Related Links
PUBLIC
39
Product Availability Matrix (PAM) (search for SAP HANA) Enterprise Information Management on SAP Help Portal
3.1.3.5 Server)
Log-Based Replication (SAP Sybase Replication
SAP Sybase Replication Server (SRS) is a sophisticated transactional data movement product that moves and synchronizes data across the enterprise without the limitation of geographical distance, to meet demanding requirements in the enterprise such as guaranteed data delivery, real-time business intelligence and zero operational downtime. SRS facilitates this by non-intrusively handling data at the source and target, while ensuring high performance and transactional integrity. SRS enables you to replicate data into an SAP HANA database from these primary databases: Adaptive Server Oracle Microsoft SQL Server DB2 UDB
It also supports the initial load of data as well as continuous real-time transactional replication from these databases to the SAP HANA database. SRS supports replication of data from non-SAP applications.
These are the components required to implement a PrimaryDB-to-SAP-HANA database replication system:
40
PUBLIC
A primary data server (SAP Sybase Adaptive Server, Oracle, DB2 UDB, MSSQL Server) A replicate SAP HANA database data server A Replication Server (with ExpressConnect for SAP HANA database) The Replication Server Options component (this component is not required for ASE Primary DB to SAP HANA): Replication Agent for MSSQL or DB2 or Oracle
Note
License Requirements: You can use these licenses for replication into the SAP HANA database: Separately purchase SAP Sybase Replication Server, SAP HANA edition, for replicating from multiple data sources. This license includes all components required to provision data from UDB DB2, Oracle, or MSSQL into the SAP HANA database. Alternatively, when you buy the Real-time-data edition for SAP HANA, you automatically receive a license for SAP Sybase Replication Server, SAP HANA edition.
Individual components can also be licensed separately for replication from UDB DB2, Oracle, or MSSQL into the SAP HANA database through the SAP Sybase Replication Server, option for SAP HANA. A prerequisite for this is that you must have SAP Sybase Replication Server, enterprise edition. Related Links Sybase Product Documentation
3.1.3.6
Comparison of Replication Methods
This table compares the key features of each replication method. Capability Trigger-Based Replication (SLT Replication) Release coverage SAP R/3 4.6C - SAP ERP 6.0 (EHP06) All other ABAP-based SAP Applications (Basis 4.6CNW7.02) Unicode/Non-Unicode MDMP Yes Partial (If table contains only ASCII characters or language key is included) Yes Yes Partial (1) ETL-Based Replication (Data Services 4.0 SP2) ERP 4.6c - SAP ERP 6.0 Extractor-based Data Acquisition (DXC) SAP Business Suite systems based on NetWeaver ABAP 4.6C or higher
Yes Yes via How to Guide
Transparent Tables
Yes
Yes- via generic Data Source
PUBLIC
41
Capability
Trigger-Based Replication (SLT Replication)
ETL-Based Replication (Data Services 4.0 SP2) Yes
Extractor-based Data Acquisition (DXC) Yes- via generic Data Source No
Cluster & Pool Tables
Yes
Non-SAP Sources
Yes (for SAP supported DBs only) Yes
Yes
Compressed Values DB Table Row Compression DB Table DB Support (Source side)
Yes
Yes- via generic Data Source Yes- via generic Data Source All SAP supported DBs
Yes
Yes
All SAP supported DBs, incl. ASE
All SAP supported DBs, incl. ASE, and others: see PAM for full list (no MaxDB support)
OS Support (Source side)
All SAP supported OS
All OS supported under ERP (NO impact of source OS on Data Services) No Multiple source systems
All OS supported under SAP Business Suite systems Yes Multiple source systems
Transactional Integrity Multi-System Support
No Multiple source systems to multiple SAP HANA instances Yes
Workload balancing (parallelization of replication) Real-time and/or scheduled replication Initial Load & Delta replication
Yes
Yes
Real-time and scheduled (on table level) Initial load, initial load + delta replication for relevant tables
Scheduled
Scheduled or Event driven
Initial load + delta replication (for table based needs delta information through timestamp column or through delta enabled extractors) Not recommended for use with DataSource extractors with delta processing types AIM, AIE,
Initial load + delta replication, for all delta processing types including AIM, AIE, AIED, AIMD, ADD, ADDD, CUBE etc.
42
Capability
Trigger-Based Replication (SLT Replication)
ETL-Based Replication (Data Services 4.0 SP2) AIED, AIMD, ADD, ADDD, and CUBE
Extractor-based Data Acquisition (DXC)
Transformation capabilities
Capabilities for filtering and transforming data, as well as data scrambling. Data filtering can be done either via selective triggers or via replication configuration settings Support dashboard
Complete ETL engine from Limited for extraction, via simple functions to very user exits complex transformations
Access to performance statistics
Via Data Services own Management Console or through the integration with SAP Solution Manager Via Data Services own Management Console or through the integration with SAP Solution Manager
Via Monitoring details Tr: RSMO and via Table View: M_Extractors in SAP HANA studio
Access to trouble shooting Yes feature
Yes, Via Monitoring details Tr: RSMO, via Table View: M_Extractors in SAP HANA studio, and alerts which can be set in statistics server configuration
(1) SAP Data Services will need a fixed code page for each run. In order to process MDMP, the same job will need to get executed multiple times, each time with a different code page and with a WHERE clause on the language key. This would only be manageable for a limited number of code pages. This table gives an overview of the capabilities of SAP Sybase Replication Server (SRS): Feature/Capability SAP Sybase Replication Server (SRS) Applications (SAP/non-SAP) Table/Database Level Replication Extractors/Data Access @Interface Technology Connectivity Optimized to SAP HANA SAP/Non-SAP Data Sources Transformations/Mapping Application-independent, DB-specific. However, SAP Business Suite is not supported. Yes Log-based ODBC Both Yes
PUBLIC
43
Feature/Capability
SAP Sybase Replication Server (SRS)
Real Time Reporting/Distribution Use Cases Bulk Data Loading Delta Loading/CDC SAP HANA Studio Integration User Security/Authorizations Event Streams/Patterns Unicode/Non-Unicode Flexible Deployment topology w/o Geographical restriction Data Definition Language replication (DDL) Publish-subscribe Paradigm Transactional Consistency
Yes Yes Yes Yes Planned Yes Yes Yes (for non-SAP applications) Yes No Yes Yes
3.2

Monitoring the SAP HANA System Landscape
You monitor the extended SAP HANA system landscape by monitoring these SAP HANA components: Monitoring components for trigger-based replication: SAP Landscape Transformation (LT) Replication Server Monitoring components for SAP HANA Direct Extractor Connection (DXC) Monitoring components for ETL-based replication: SAP Data Services
3.2.1 Monitoring Components for Trigger-Based Replication (SAP LT Replication Server)

For information about monitoring the SAP LT (Landscape Transformation) Replication Server, see the SAP Landscape Transformation for SAP HANA - Technical Operations Manual. Related Links SAP Landscape Transformation for SAP HANA - Technical Operations Manual
44
3.2.2 Monitoring components for SAP HANA Direct Extractor Connection (DXC)
For more information about monitoring the SAP HANA Direct Extractor Connection, see SAP HANA Direct Extractor Connection Implementation Guide. Related Links SAP HANA Direct Extractor Connection Implementation Guide
3.2.3 Monitoring Components for ETL-Based Replication (SAP Data Services)

For information about monitoring SAP Data Services, see: SAP Data Services Management Console Guide Information about how to use SAP Data Services Administrator and SAP Data Services Metadata Reports. SAP Data Services Administrator's Guide Information about administrative tasks such as monitoring, life cycle management, security, and so on. SAP Data Services Performance Optimization Guide Information about how to improve the performance of SAP Data Services.
3.3
SAP HANA Administration Overview
You administer the SAP HANA system landscape by administering the SAP HANA components: Administering components for Trigger-Based Replication: SAP LT (Landscape Transformation) Replication Server Administering components for ETL-Based Replication: SAP Data Services Administering components for SAP HANA Direct Extractor Connection (DXC)
3.3.1 Administrating Components for Trigger-Based Replication (SAP LT Replication Server)

For information about administering the SAP LT (Landscape Transformation) Replication Server, see the SAP Landscape Transformation for SAP HANA - Technical Operations Manual.
PUBLIC
45
3.3.2 Administrating Components for SAP HANA Direct Extractor Connection (DXC)
For information about administering the SAP HANA Direct Extractor Connection (DXC), see, SAP HANA Direct Extractor Connection Implementation Guide
3.3.3 Administrating Components for ETL-Based Replication (SAP Data Services)

For information about administrating SAP Data Services components, see the following guides: Management Console Guide SAP Data Services XI 4.0 (14.0.0) SAP Data Services Administration Guide Information platform services Administration Guide SAP Data Services Upgrade Guide
3.4 Starting the Software Update Manager (SUM) for SAP HANA
For information about starting the Software Update Manager (SUM) for SAP HANA see the SAP HANA Automated Update Guide -> Automated Update -> Performing an Automated Update
3.5 Backup and Recovery of SAP HANA Replication Technologies

You backup and recover the SAP HANA system landscape by extending the backup and recovery strategy to include the SAP HANA components as well as the SAP HANA database: Backup and Recovery for the Trigger-Based Replication components: SAP LT (Landscape Transformation) Replicator Backup and Recovery for SAP HANA Direct Extractor Connection (DXC) Backup and Recovery for ETL-Based Replication components: Data Services
46
PUBLIC
3.5.1 Backup and Recovery for the Trigger-Based Replication components (SAP LT Replication Server)
For information about backup and recovery for the SAP LT (Landscape Transformation) Replication Server, observe the following: The SAP LT (Landscape Transformation) Replication Server creates a schema in the SAP HANA database called SYS_REPL where the replication control tables are stored (RS_* tables, to store replication status for example). These tables are part of the normal database backup/recovery. Recovery scenarios: If the database is recovered to the latest consistent state, no further action is necessary, the replication automatically resumes (as the jobs are not running on the SAP HANA hardware). If the database is recovered to an earlier point in time (recovery of data backup with clear log option), initial load and replication have to be started again.
3.5.2 Backup and Recovery for the SAP HANA Direct Extractor Connection (DXC)
The architecture of DXC involves components implemented in the SAP Business Suite system and also in SAP HANA. Thus, a significant amount of configuration data, metadata, and the state of the mechanisms for delta handling (change data capture) are stored in the SAP Business Suite system. Of course, your SAP Business Suite system must be backed up regularly. A schema is created for each SAP Business Suite system connected to SAP HANA via DXC, and for each DataSource a corresponding In-Memory DataStore Object is created in SAP HANA. These In-Memory DataStore Objects are be part of any normal SAP HANA database recovery. Recovery scenarios: In any recovery scenario, data consistency must be maintained between the SAP Business Suite system and SAP HANA. If the SAP Business Suite system is recovered to a point-in-time, in order to ensure that data in the InMemory DataStore Objects in SAP HANA are consistent with the SAP Business Suite system, the data in the In-Memory DataStore Objects in SAP HANA should be deleted and a delta initialization should be performed for all DataSources in use in SAP HANA from that SAP Business Suite system. Similarly, if the SAP HANA database is recovered to a point-in-time, in order to ensure that data in the InMemory DataStore Objects in SAP HANA are consistent with the SAP Business Suite system, the data in the In-Memory DataStore Objects in SAP HANA should be deleted and a delta initialization should be performed for all DataSources in use in SAP HANA from that SAP Business Suite system.
Note
Delta initialization typically involves loading historical data, and can be significantly time-consuming. This should be factored into business continuity planning Related Links SAP HANA Direct Extractor Connection Implementation Guide
PUBLIC
47
Information on Delta Initialization
3.5.3 Backup and Recovery for the ETL-Based Replication components (SAP Data Services)
For information about backup and recovery for SAP Data Services, observe the following: SAP Data Services stores its own metadata in a relational database (currently not the SAP HANA database). This metadata is the definition of the source and target connections, the mappings and transformations, the workflows with load order and so on. Backup this database regularly. If the SAP HANA database needs to be recovered, replication can resume without any further user interaction. Data Services provides batch loading for SAP HANA database, so no further user interaction would be needed. The next time a batch load is started, it will be loaded into the database again.
3.6
Security for the SAP HANA System Landscape
You ensure security for your SAP HANA system landscape by ensuring security of the SAP HANA components: For more information, see: SAP HANA Security Guide SAP HANA Security Guide - Trigger-Based Replication (SLT) SAP HANA Security Guides - ETL-Based Replication (Data Services) SAP Data Services Administrators Guide -> Security SAP Data Services Administrators Guide -> User Rights and management
48
SAP HANA Data Management
You use the SAP HANA modeler, which is accessible as a perspective of the SAP HANA studio, for modeling and managing SAP HANA data. It allows technical users to create new or modify existing models of data. In addition, the initial configuration of the data replication is done in the SAP HANA modeler.
4.1
Configuring Data Replication
Configure data replication to provide the necessary metadata and data to the SAP HANA system. You need to perform the following steps: Load table metadata from the data provider systems (source systems) into the SAP HANA database (target system) for all tables of the source system or for a subset of tables Load data (initial load) from the data provider systems (source systems) into the SAP HANA database (target system) for a selection of tables Start continuous replication of data changes from the data provider systems (source systems) into the SAP HANA database (target system) for a selected subset of tables
Once the metadata and data are loaded to the SAP HANA system, you can create views and reports based on these metadata and data, as described in Modeling Data. For more information, see the SAP HANA Developer Guide, chapters: Importing Metadata Mass Import of Metadata Selective Import of Metadata
Provisioning Data
4.2
Modeling Data
You use the SAP HANA modeler for modeling and managing SAP HANA data. For more information, see the SAP HANA Developer Guide.
4.3 Modeling and Data Provisioning for ETL-Based Replication (SAP Data Services)
When using the ETL-Based Replication technology by SAP Data Services, you can also model ERP data by means of Data Services modeling tools. The following documents describe the modeling and data provisioning steps you have to do in SAP Data services:
SAP HANA Technical Operations Manual SAP HANA Data Management
PUBLIC
49
SAP Data Services Administrators Guide -> Server Management -> To configure SAP HANA ODBC SAP Data Services Reference Guide -> SAP HANA target table options SAP Data Services Reference Guide -> Database datastores -> SAP HANA Designer Guide SAP Data Services Describes how to set up a job in the Designer to connect to any database Reference Guide SAP Data Services Describes the options for setting up connections to the SAP HANA database Supplement for SAP Data Services Describes all interactions with other SAP applications
Related Links Enterprise Information Management on SAP Help Portal
50
SAP HANA Technical Operations Manual SAP HANA Data Management
SAP liveCache on SAP HANA
You can run SAP liveCache on SAP HANA, lowering total cost of ownership and taking advantage of SAP HANA features. SAP liveCache is an in-memory object store technology that is used to speed up material planning scenarios in SAP Supply Chain Management (SCM). It is now offered as an add-on for SAP HANA. There are a number of advantages to running SAP liveCache as part of SAP HANA: Only one database needs to be administered, which reduces setup and maintenance Backup and recovery is simplified: There is no longer a need for separate backups Inconsistencies that could arise from separate backups can be avoided
SAP liveCache can take advantage of existing SAP HANA capabilities like performance and high availability.
Supported Scenarios
The following scenarios are supported: Single host scenario: The SAP HANA database runs on a single host including SAP liveCache Scale out scenario: SAP liveCache runs on a dedicated, separate slave host in a distributed SAP HANA system. In a scale-out system, a standby host must be equipped so that it can take over the operation of any of the failed hosts in the failover group. In the case of a failed host, which was a dedicated liveCache host, with a reduced set of memory or CPU features, it may not be reliably used as a standby host for any hosts in the failover group.
Note
There is no standalone SAP liveCache based on SAP HANA technology. This means that you cannot replace your standalone SAP liveCache based on MaxDB technology with a standalone SAP liveCache based on SAP HANA technology.
Monitoring SAP liveCache in SAP HANA Studio

You can use both the DBACockpit for SAP HANA and the SAP HANA studio to monitor SAP liveCache. The following system views allow you to monitor run time information in the SAP HANA studio: M_LIVECACHE_OMS_VERSIONS M_LIVECACHE_PROCEDURE_STATISTICS M_LIVECACHE_CONTAINER_STATISTICS M_LIVECACHE_SCHEMA_STATISTICS M_LIVECACHE_LOCKS
SAP HANA Technical Operations Manual SAP liveCache on SAP HANA
PUBLIC
51
System Copy
For detailed information on the procedure for copying an SAP Supply Chain Management system with SAP liveCache on SAP HANA see the Administrator's Guide, SAP Enhancement Package 2 for SAP SCM 7.0, Version for SAP HANA. Related Links SAP HANA Database - System Views Reference SAP HANA Administration Guide DBACockpit for SAP HANA Administrator's Guide SAP Enhancement Package 2 for SAP SCM 7.0, Version for SAP HANA
52
SAP HANA Technical Operations Manual SAP liveCache on SAP HANA
www.sap.com/contactsap
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx for additional trademark information and notices.

SAP HANA Technical Operations Manual en

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SAP HANA Technical Operations Manual en

Загружено:

Авторское право:

Доступные форматы

PUBLIC

SAP HANA Platform SPS 06 Document Version: 1.0 - 26-06-2013

SAP HANA Technical Operations Manual

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

SAP HANA Technical Operations Manual Table of Contents

SAP HANA Administration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.3.1 3.3.2 3.3.3

3.6 4 4.1 4.2 4.3 5

SAP HANA Technical Operations Manual Table of Contents

1 Getting Started with SAP HANA Appliance Software (SAP HANA)

What is SAP HANA?

SAP HANA Guides

SAP HANA administration and security

SAP HANA Knowledge Center on the SAP Help Portal

SAP HANA documentation for previous Support Package Stacks

SAP HANA Knowledge Center on SAP Service Marketplace

https://service.sap.com/bosap-instguides https://service.sap.com/bosap-support https://service.sap.com/quicksizer

https://service.sap.com/securityguide http://scn.sap.com/docs/DOC-7848 https://service.sap.com/security https://service.sap.com/unicode https://service.sap.com/sp-stacks

Important SAP Notes

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

SAP Note Number

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Download Patches and Updates

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Administering and Operating SAP HANA

Service and Support

Installation of the SAP HANA Appliance Software

Installation of additional software

SAP Note Number

Software Maintenance Updating and Patching the Operating System

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Updating and Patching SAP HANA Appliance Software

Updating and Patching File System Components

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Updating and Patching Storage Components

2.5.5 Updating and Patching Firmware of Underlying Hardware Components

Monitoring the SAP HANA Database

2.6.1 Integrating SAP HANA into a Central Operations Concept

Connecting SAP Solution Manager to SAP HANA

Central Monitoring and Administration

Analyzing the Root Cause of Problems

Administering the SAP HANA Database

Initial Administrative Tasks

Regular Administrative Tasks

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Related Links SAP HANA Administration Guide

On Demand Administrative Tasks

Backup and Recovery

In-Memory Data and Persistent Storage

Security Features and Functions

Authentication and Single Sign-On (SSO)

User and Role Management

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Application Services Security

Data Center Integration

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

2.10 High Availability for SAP HANA

SAP HANA High Availability Support

Fault recovery support:

Using Secondary Servers for Non-Productive systems

Related Links SAP HANA Administration Guide

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

3 Administering and Operating SAP HANA Data Provisioning Technologies

SAP HANA Smart Data Access