hana1 tom en_mp

SAP HANA Technical Operations Manual■ SAP HANA Appliance Software SPS 04

2012-05-08

© 2012 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAPBusinessObjects Explorer, StreamWork, SAP HANA and other SAP products and services mentioned

Copyright

herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and other countries.Business Objects and the Business Objects logo, BusinessObjects,Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects productsand services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase andAdaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase,Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360°, B2B 360° Services areregistered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAPcompany. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National productspecifications may vary.These materials are subject to change without notice. These materials areprovided 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 oromissions with respect to the materials. The only warranties for SAP Group products and servicesare those that are set forth in the express warranty statements accompanying such products andservices, if any. Nothing herein should be construed as constituting an additional warranty.

2012-05-08

Contents

Getting Started with SAP HANA Appliance Software (SAP HANA)........................................5Chapter 1

About this Document...............................................................................................................51.1What is SAP HANA?................................................................................................................51.2SAP HANA Guides..................................................................................................................61.3Related Information..................................................................................................................61.4Important SAP Notes...............................................................................................................81.5Software Download................................................................................................................101.6Download Patches and Updates............................................................................................101.6.1Software Components...........................................................................................................101.7Technical System Landscape.................................................................................................131.8SAP HANA Landscape...........................................................................................................141.8.1

Administering and Operating SAP HANA.............................................................................17Chapter 2

Roles and Responsibilities......................................................................................................172.1Service and Support..............................................................................................................182.2Installation of the SAP HANA Appliance Software..................................................................182.3Starting and Stopping the SAP HANA Database....................................................................192.4Change Management.............................................................................................................202.5Updating and Patching the Operating System........................................................................202.5.1Updating and Patching SAP HANA Appliance Software.........................................................212.5.2Updating and Patching File System Components...................................................................222.5.3Updating and Patching Storage Components.........................................................................222.5.4Administering the SAP HANA Database................................................................................222.6Initial Administrative Tasks.....................................................................................................232.6.1Regular Administrative Tasks.................................................................................................232.6.2On Demand Administrative Tasks..........................................................................................232.6.3Backup and Recovery............................................................................................................242.7In-Memory Data and Persistent Storage................................................................................252.7.1Backup...................................................................................................................................252.7.2Recovery...............................................................................................................................262.7.3Security.................................................................................................................................282.8Auditing and Regulatory Compliance......................................................................................282.8.1

2012-05-083

Authentication........................................................................................................................282.8.2Authorization..........................................................................................................................292.8.3High Availability......................................................................................................................292.9

Administering and Operating SAP HANA Replication Technologies....................................31Chapter 3

SAP HANA Replication Technologies.....................................................................................313.1Introduction............................................................................................................................313.1.1Trigger-Based Replication......................................................................................................333.1.2ETL-Based Replication...........................................................................................................343.1.3Log-Based Replication...........................................................................................................373.1.4Comparison of Replication Methods......................................................................................393.1.5ETL-based Data Acquisition by SAP HANA Direct Extractor Connection................................423.2Monitoring the SAP HANA System Landscape......................................................................433.3Monitoring Components for Trigger-Based Replication (SAP LT Replication Server)..............433.3.1Monitoring Components for ETL-Based Replication (SAP BusinessObjects Data Services)....433.3.2Monitoring Components for Log-Based Replication (Sybase Replication)..............................443.3.3Starting and Stopping SAP HANA..........................................................................................443.4Starting and Stopping the SAP HANA Database....................................................................443.4.1Starting and Stopping Sybase Components...........................................................................453.4.2Starting the Software Update Manager (SUM) for SAP HANA..............................................453.4.3SAP HANA Administration Overview.....................................................................................463.5Administrating Components for Trigger-Based Replication (SAP LT Replication Server)........463.5.1Administrating Components for ETL-Based Replication (SAP BusinessObjects DataServices)................................................................................................................................46

3.5.2

Administrating Components for Log-Based Replication (Sybase Replication).........................463.5.3Backup and Recovery of SAP HANA Replication Technologies..............................................473.6Backup and Recovery for the Trigger-Based Replication components (SAP LT ReplicationServer)...................................................................................................................................47

3.6.1

Backup and Recovery for the ETL-Based Replication components (SAP BusinessObjects DataServices)................................................................................................................................48

3.6.2

Backup and Recovery for the Log-Based Replication components (Sybase Replication)........483.6.3Security for the SAP HANA System Landscape ....................................................................483.7

SAP HANA Data Management..............................................................................................51Chapter 4

Configuring Data Replication..................................................................................................514.1Modeling Data.......................................................................................................................514.2Modeling and Data Provisioning for ETL-Based Replication (SAP BusinessObjects DataServices)................................................................................................................................52

4.3

2012-05-084

Contents

Getting Started with SAP HANA Appliance Software (SAPHANA)

1.1 About this Document

This Technical Operations Manual provides an end-to-end picture of the administration tools availablewith SAP HANA and the key tasks that a system administrator needs to perform. Links to the relevantadministration documentation of each of the components included in the SAP HANA solution areprovided for details and step procedures.

1.2 What is SAP HANA?

• SAP HANA• SAP HANA is a flexible, data-source-agnostic appliance that enables customers to analyze large

volumes of SAP ERP data in real-time, avoiding the need to materialize transformations.

• SAP HANA is a hardware and software combination that integrates a number of SAP componentsincluding the SAP HANA database, SAP LT (Landscape Transformation) Replication Server,SAP HANA Direct Extractor Connection (DXC) and Sybase Replication technology.

• SAP HANA is delivered as an optimized appliance in conjunction with leading SAP hardwarepartners.

• SAP HANA database• The SAP HANA database is a hybrid in-memory database that combines row-based,

column-based, and object-based database technology. It is optimized to exploit the parallelprocessing capabilities of modern multi-core CPU architectures. With this architecture, SAPapplications can benefit from current hardware technologies.

• The SAPHANA database is the heart of SAP’s in-memory technology offering, helping customersto improve their operational efficiency, agility, and flexibility.

2012-05-085

Getting Started with SAP HANA Appliance Software (SAP HANA)

1.3 SAP HANA Guides

For more information about SAP HANA landscape, security, installation, and administration, see theresources listed below:

Quick LinkLocationTopic

https://service.sap.com/hana:

• SAP HANA Master Guide• SAP HANA Installation Guide with SAP HANA

Unified Installer• SAP HANA Master Update Guide• SAP HANA Automated Update Guide

SAP HANA Knowl-edge Center on SAPService Marketplace

SAPHANA landscape,deployment, and instal-lation

http://help.sap.com/hana_appliance:

• SAP HANA Technical Operations Manual• SAP HANA Security Guide

SAP HANA Knowl-edge Center on theSAP Help Portal

SAPHANA administra-tion and security

1.4 Related Information

2012-05-086


https://service.sap.com/hana

https://service.sap.com/~sapidb/011000358700000604552011





http://help.sap.com/hana_appliance

http://help.sap.com/hana/hana1_tom_en.pdf

http://help.sap.com/hana/hana1_sec_en.pdf

For more information about planning your deployment, see the following:

LocationContent

https://service.sap.com/hana*

http://help.sap.com/hana_applianceLatest documentation for SAP HANA

http://sybooks.sybase.com/nav/base.doSybase product documentation

https://service.sap.com/instguidesLatest versions of SAP installation and upgrade guides

https://service.sap.com/sizingSizing, calculation of hardware requirements, such asCPU, disk, and memory resources

https://service.sap.com/bosap-instguidesSAP BusinessObjects installation and deploymentguides

https://service.sap.com/bosap-supportSAP BusinessObjects support

https://service.sap.com/quicksizerSizing, calculation of hardware requirements - such asCPU, disk andmemory resources - with the QuickSizertool

https://service.sap.com/pamReleased platforms and technology-related topics suchas maintenance strategies and language support –Platform Availability Matrix (PAM)

https://service.sap.com/securityguideNetwork security

https://service.sap.com/haHigh availability

https://service.sap.com/performancePerformance

https://service.sap.com/securitySecurity

https://service.sap.com/unicodeUnicode SAP systems and their availability

2012-05-087



http://help.sap.com/hana_appliance

http://sybooks.sybase.com/nav/base.do

https://service.sap.com/instguides

https://service.sap.com/sizing

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

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

https://service.sap.com/quicksizer

https://service.sap.com/pam

https://service.sap.com/securityguide

https://service.sap.com/ha

https://service.sap.com/performance

https://service.sap.com/security

https://service.sap.com/unicode

LocationContent

https://service.sap.com/sp-stacksInformation about Support Package Stacks, latestsoftware versions and patch level requirements

(*) You need an authorized user ID to access this information. Do you need to register for an SAPService Marketplace login? Did you forget your password?

The following table lists further useful links on SAP Service Marketplace:

Location on SAP Service MarketplaceContent

https://service.sap.com/messageSAP message wizard

https://service.sap.com/notesSAP Notes search

https://service.sap.com/swdcSAP Software Distribution Center – software downloadand ordering of software

https://service.sap.com/rktSAPOnline Knowledge Products (OKPs) – role-specificlearning maps

1.5 Important SAP Notes

You must read the following SAP Notes before you start the installation. These SAP Notes contain thelatest 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 SAPService Marketplace at https://service.sap.com/notes.

2012-05-088


https://service.sap.com/sp-stacks

http://service.sap.com/~sapidb/002006825000100141192000E/



https://service.sap.com/message

https://service.sap.com/notes

https://service.sap.com/swdc

https://service.sap.com/rkt

https://service.sap.com/notes

TitleSAP Note Number

SAP HANA: Central Note1514967

SAP HANA Appliance Software SPS 04 Release Note1703675

SAP HANA Database: Central Note1523337

Swap-space recommendation for Linux1597355

Support for multiple SAP HANA databases on a single SAP HANA appliance1681092

Support for multiple applications on SAP HANA1661202

Supported clients for SAP HANA1577128

SAP HANA: Sizing SAP HANA Database1514966

SAP BW on HANA: Sizing SAP HANA Database1637145

Check the current SAP Notes for the various parts of SAP HANA by searching for any of the followingCSS/CSN components:

SAP HANA Platform Edition• BC-HAN SAP HANA appliance software• BC-DB-HDB SAP HANA database• BC-DB-HDB-ENG SAP HANA database engine• BC-DB-HDB-PER SAP HANA database persistence• BC-DB-HDB-SYS SAP HANA database interface/DBMS• BC-DB-HDB-DBA SAP HANA database administration (DBA cockpit)• BC-DB-HDB-MDX MDX Engine (Microsoft Excel client)• BC-HAN-MOD SAP HANA studio / modeler• BC-HAN-3DM Information Composer• BC-HAN-SRC Search• BC-CCM-HAG SAP Host Agent

SAP HANA Lifecycle Management• BC-HAN-INS, BC-INS-NGP SAP HANA unified installer (lmtp)• BC-DB-HDB-INS SAP HANA database installation• BC-HAN-UPD Software Update Manager (SUM) for SAP HANA• BC-DB-HDB-UPG SAP HANA database upgrade

2012-05-089


https://service.sap.com/sap/support/notes/1514967









SAP HANA Enterprise Edition• BC-HAN-LOA SAP HANA load controller (log-based replication)• BC-HAN-LTR SAP Landscape Transformation (trigger-based replication)• BC-DB-HDB-DEC SAP HANA Direct Extractor Connection (DXC) to SAP HANA• BC-HAN-REP Sybase replication server (log-based replication)• EIM-DS Data Services (ETL-based replication)

CSS/CSN search also supports using the wildcard asterisk (*) in searches, so you can, for example,also search for BC-DB-HDB* or similar and you will get results for all sub-components.

1.6 Software Download

The components of SAPHANA can only be installed by certified hardware partners on validated hardwarerunning a specific operating system. Any other system or content developed with such systems is notsupported by SAP. For more information, see the information page of the product version. SupportPackage Stacks (SPS) can be downloaded and applied to appliances according to agreements withthe respective hardware partner.

1.6.1 Download Patches and Updates

Note:For more information on applying patches and updates see the section on Change Management.

Related Topics• Change Management

1.7 Software Components

SAP HANA appliance software is available in different editions:• SAP HANA appliance software platform edition

• SAP HANA appliance software enterprise edition

• SAP HANA appliance software enterprise extended edition

2012-05-0810


The SAP HANA appliance software platform edition is intended for customers who want to useETL-based replication and already have a license for SAPBusinessObjects Data Services. It is comprisedof the following components:• SAP HANA database

• SAP HANA studio

• SAP HANA client

• SAP Host Agent 7.20

• SAP HANA information composer

• Diagnostics Agent 7.3

• SAP HANA client package for Microsoft Excel

• SAP HANA UI for Information Access (INA)

The SAP HANA appliance software enterprise edition is intended for customers who want to useeither trigger-based replication or ETL-based replication and do not already have all of the necessarylicenses for SAP BusinessObjects Data Services. It is comprised of the following components:• SAP HANA database

• SAP HANA studio

• SAP HANA client



2012-05-0811





• SAP HANA Direct Extractor Connection (DXC)

• SAP LT Replication AddOn

• SAP LT Replication Server

• SAP BusinessObjects Data Services 4.0

TheSAPHANA appliance software enterprise extended edition is intended for customers who wantto use the full potential of all available replication scenarios including log-based replication. It is comprisedof the following components:• SAP HANA database

• SAP HANA studio

• SAP HANA client






• SAP HANA Direct Extractor Connection (DXC)

• SAP LT Replication AddOn

• SAP LT Replication Server

• SAP BusinessObjects Data Services 4.0

• Sybase Adaptive Server Enterprise (ASE) 15.5

• Sybase Replication Server 15 (incl. ECDA)

• Sybase Replication Server Agent 15

• SAP HANA load controller

Note:

• The Software Update Manager (SUM) for SAP HANA is installed by the SAP HANA unified installertogether with other SAP HANA components. For a list of components, see SAP HANA InstallationGuide, section "Installed SAP HANA Components and Directories". The Software Update Manager(SUM) for SAP HANA is part of the Software Logistics Toolset (SL Toolset).

• SAP HANA information composer is aWeb-based environment that allows business users to uploaddata to the SAP HANA database and to manipulate that data by creating information views. TheSAP HANA information composer is installed separately from the SAP HANA system. For moreinformation, see the SAP HANA Information Composer – Installation and Configuration Guide.

2012-05-0812




https://service.sap.com/~sapidb/011000358700000993102011E

1.8 Technical System Landscape

The figure below shows an overview of the technical system landscape for the SAP HANA appliancesoftware and its related components, such as the SAP HANA studio and other applications, one ofwhich is the SAPHANA information composer. Note that the figure below shows a sample configurationwith three SAP HANA database servers. The figure also shows some optional components that maybe purchased separately.

2012-05-0813


1.8.1 SAP HANA Landscape

The following two figures show the SAP HANA landscape from an internal and an external view.

The first figure shows the components that make up SAP HANA, including the SAP HANA databaseand SAP HANA studio.

2012-05-0814


The SAP HANA appliance and its position in the system landscape is shown in this figure.

2012-05-0815


2012-05-0816


Administering and Operating SAP HANA

2.1 Roles and Responsibilities

This section describes the tasks, concepts, responsibilities, and procedures necessary for the ongoingoperation 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 SAPresponsible for and what does SAP support? What do the SAP hardware partners do? What is thecustomer asked to do? This is explained in more detail in the following sections.

ResponsibleTask

Hardware PartnerSAP HANA appliance installation

Hardware PartnerHardware

Hardware PartnerOS installation

CustomerOS updates

CustomerSAP HANA updates

CustomerData source connectivity

CustomerBI Client installation

SAPSAP HANA software support

• Schedule - When and how often should each task be performed? What tasks are to be performedduring ongoing operation, such as regular checks and periodic tasks?What tasks must be performedon demand and in special situations?

• Procedures - How can each task be performed? Several tools and transactions can be used foradministering and monitoring SAP HANA.

SAP HANA is following the appliance delivery model. Hence it can only be obtained from one of thefollowing 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)

2012-05-0817


http://www.hp.com/go/sap/hana

http://www.ibm.com/solutions/sap/hana

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)

For more information on supported software and hardware platforms refer to the SAP Product AvailabilityMatrix (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 SAPHANA, SAP is themain point of contact. SAP distributesall 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 specialService Level Agreement (ESA)), the customer should contact the hardware partner directly in the caseof obvious hardware or operating system issues.

To investigate SAP HANA-related problems, SAP support requires a support connection to all serversin the SAP HANA landscape. For more information about establishing a service connection for SAPHANA, see SAP Service Marketplace. See SAP Note 1635304.

Note:You need a valid SAP Service Marketplace user to access SMP and related SAP Notes.

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 withcorresponding, validated hardware as a prepackaged solution with the most recent support packagestack (at the time of shipment of the SAP HANA appliance) to the customer site. The SAP hardwarepartner may add specific best-practices and SAP HANA software configuration. The installation isfinalized by an onsite setup of the SAP HANA components. This includes deploying the SAP HANAsystem in the customer data center, connectivity to the network, SAP system rename, and SolutionManager connectivity.

Once the network connection to the SAP HANA system has been established successfully and theSAP 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, then the establishment of datareplication/connectivity to data source systems (including the deployment of additional replicationcomponents) and the installation of potential BI clients (such as SAP BusinessObjects Explorer on top

2012-05-0818


http://www.cisco.com/

http://www.dell.com

http://www.hds.com/solutions/applications/sap-application/sap-hana.html

http://www.nec.com



https://help.sap.com/hana


of BOE) is again the responsibility of the customer or the consulting organization carrying out the SAPHANA project onsite for the customer.

Note:The installation of the SAP HANA software is to be carried out by the hardware partner only. Any othersystem or content developed with a system not installed by certified hardware partners on validatedhardware is not supported by SAP. This includes deployment of SAP HANA system in the customerdata center, connectivity to the network, adaption of system parameters like SID or passwords tocustomer needs and Solution Manager connectivity if necessary.

HardwareThe hardware, shipped together with the SAP HANA appliance software, is dedicated to its purpose.No other software, including SAP software or multiple instances of SAP HANA appliance software,should be installed unless explicitly stated in the installation documentation.

Installation of additional softwareThe configuration of the shipped and preconfigured SAPHANA systemmust persist. If those configurationsettings are subsequently changed, significant performance problemsmay occur. Any request to validateadditional monitoring tools must be addressed to the responsible SAP hardware partner to ensurefurther supportability.

Monitoring tools exist that are recommended by both SAP and the hardware partners (such as SolutionManager Diagnostics). These tools have been tested and do not interfere with any performancestatements SAP has given. For more information, contact your hardware partner.

If the customer wants to integrate the SAP HANA server into their IT landscape, additional monitoringor support software may be installed. However, the installation of such additional software/applicationson SAP HANA (such as software for monitoring) by means of the SAP HANA customer lies beyond theSAP HANA shipment scope, which has been certified by SAP, and may potentially hamper the properoperation of the SAP HANA system. Hence, the following two requirements must be met:• Performance

SAP HANA hardware partners and customers must make sure that additional software such asmonitoring tools does not affect the performance of the SAP HANA appliance software (for example,as a result of the allocation of significant amounts of memory). For this reason, monitoring agentsmust not be installed on SAP HANA servers if those agents affect the performance negatively.

• Supportability

The customer must have a support contract with the SAP hardware partner for the monitoring toolsto guarantee the further supportability of the SAP HANA server. See SAP Note 784391 – SAPsupport terms and 3rd party Linux kernel drivers (SAP Service Marketplace user required).

For more information about specific monitoring software, contact your software provider.

2.4 Starting and Stopping the SAP HANA Database

2012-05-0819


You start and stop the the SAP HANA database with the SAP HANA studio.

Launch the SAP HANA studio and open the administration console pespective. If the administrationconsole perspective does not open automatically, you can open it manually fromWindow > OpenPerspective > Administration Console. To start or stop the SAP HANA database select it in theNavigator, open the context menu with the right mouse button and select Start... or Stop... respectively.Also see Starting Systems and Stopping Systems in the SAP HANA Database Administration Guide.

2.5 Change Management

The following sections provide information on permitted configuration changes to the SAP HANAsoftware, operating system, and so on. You will also find information about the changes that are notsupported by SAP or SAP hardware partners.

For more information on updating SAP HANA and its components see:• How to update SAP HANA and its components with the Software Update Manager (SUM)

SAP HANA Automated Update Guide

• How to individually patch SAP HANA software components

SAP HANA Master Update Guide

2.5.1 Updating and Patching the Operating System

The initially delivered configuration of the operating system should persist. If configuration settings aresubsequently changed, significant performance problems may occur. The customer can request avalidation of configuration changes for the operating system and for the installation of additional operatingsystem components by the hardware partner depending on the service contract between the hardwarepartner and the customer. The hardware partner then supports these changes and additional componentsin accordance with the existing service contract with the customer. No modified Linux version can beused.

The customer is generally responsible for implementing operating system patches. If the customer hasa special agreement with the hardware partner, support for operating system patching may be theresponsibility of the hardware partner.

OS security patches may be imported immediately after they are available; however, the originalpackages of the distributors must be used to which a customer is entitled within the framework of avalid support contract with the distributor or an authorized OEM.

For all other operating system patches, the customer should wait until they are officially released forSAP HANA via a corresponding SAP Note before the operating system is updated with the patches inquestion. In particular, any updates related to kernel or runtime libraries (glibc) need to be validated

2012-05-0820


http://help.sap.com/hana/hana1_imdb_studio_admin_en.pdf

https://service.sap.com/~sapidb/011000358700000604952011D


and approved by SAP beforehand. Support Package Stacks (SPSs) can be downloaded and appliedto 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 mustensure that the configuration settings of the operating system persist. Do not change configurationsettings when you patch the operating system unless explicitly stated in the corresponding SAP releasenote. SAP will state any dependencies in the relevant SAP Note published when a revision is releasedwhich 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 hardwaresupport provider. The customer is responsible for any complete upgrade of the operating system andthe 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 PrioritySupport for SAP'). This support offer facilitates communication and ensures high quality. OS securitypatches may be imported immediately after they are available; however, the original packages of thedistributors must be used to which a customer is entitled within the framework of a valid support contractwith the distributor or an authorized OEM.

For more information, see SAP Note 1056161 - SUSE Priority Support for SAP applications and SAPNote 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 packagestack at the time when the SAP HANA appliance is shipped. The customer is responsible for thesubsequent implementation of SAPHANA patches, revisions, or support packages and support packagestacks.

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 recommendapplying the latest SAP HANA support package stack after applying an update to the connectedsystem.

• The SAP HANA support packages stacks are cumulative. You can update directly from any olderSAP HANA support package stack to any newer SAP HANA support package stack.

• New SAP HANA support package mainly cover software improvements. SAP recommends that youdownload and install these new SAP HANA support packages if SAP support has to resolve issueswith SAP HANA versions previously installed in the customer landscape. However, customers donot necessarily need to update their SAP HANA landscape with the newest SAP HANA supportpackages if their SAP HANA landscape works correctly.

• NewSAPHANA support packages and patches will be produced and shipped at SAP’s sole discretion.There is no periodic cycle for releasing and patching the SAP HANA software. The new SAP HANAsupport package stacks will be communicated to customers and hardware partners by means ofSAP Notes.

2012-05-0821





For the most current information on SAPHANA support packages and patches, see SAPNote 1514967– SAPHANA 1.0: Central Note (SAP Service Marketplace user required). Up to now there are no knowndependencies between SAPHANA support package stacks and the SAPHANA hardware and installedfirmware. The process for implementing SAP HANA support packages is described on SAP ServiceMarketplace 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 aspatching.

2.5.3 Updating and Patching File System Components

The customer is responsible for implementing operating patches for the shared file system. If thecustomer has a special agreement with the hardware partner, the hardware partner is responsible forproviding support for file system patching.

2.5.4 Updating and Patching Storage Components

If the customer has a special agreement with the hardware partner, the hardware partner is responsiblefor patching storage components (such as software for the filer).

Note:Special support agreements may exist with the hardware partner, which include services such aspatching.

2.6 Administering the SAP HANA Database

You administer the SAP HANA database using the administration console perspective of the SAP HANAstudio. The administration console perspective of the SAP HANA studio allows technical users tomanage the SAP HANA database as well as to create and manage user authorizations.

For more details, seeSAP HANA Database – Administration Guide

For further reference information, see:• SAP HANA Database - System Tables and Monitoring Views• SAP HANA Database - SQL Reference Guide

2012-05-0822





http://help.sap.com/hana/hana_monitor_views_en.pdf

http://help.sap.com/hana/hana_sql_en.pdf

2.6.1 Initial Administrative Tasks

It is strongly recommended after the initial setup and after the initial load, that you perform a full dataand filesystem backup (including a configuration backup). For more information, see the SAP HANADatabase – Backup and Recovery Guide.

2.6.2 Regular Administrative Tasks

• Regularly check the system status on the Overview tab page of the administration editor in SAPHANA studio. This displays the most important system information:• Overall system state• General system information (software versions and so on).• The Current Alerts and Messages section shows the latest warnings generated by the statistics

server. Detailed information about these alerts and messages is available by clicking Showalerts. The alerts and messages are generated by the statistics server, which is a monitoringtool 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 availablememory, 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 isdisplayed.

• On the Services tab page (under the Landscape tab) of the administration screen in SAP HANAstudio, check that all services belonging to your system are running: preprocessor, name server andindex server for each host and one statistics server. A statistics server exists on each host of adistributed landscape; however, the service actually runs on the master host only. Running servicesare indicated by a green icon. Information about resource usage and possible bottlenecks is alsodisplayed.

• Regularly perform data backups (including configuration backups). There are no general guidelinesfor backup frequency (this depends on the usage scenario). For more information, see the SAPHANA Database – Backup and Recovery Guide.

2.6.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

2012-05-0823


http://help.sap.com/hana/hana1_imdb_backup_en.pdf




administration screen. To display a log file, choose Open in the context menu of the list, or simplydouble-click the entry for the respective log file.

• You can turn on and configure several traces from the Trace Configuration tab. For more detailssee Configuring Traces in the SAP HANA Database – Administration Guide.

• In certain situations, you have to restart the system (for example, after a power failure). In theNavigator of the SAPHANA studio, open the context menu on the system entry and chooseRestart.After confirming the restart, you need to enter the operating system user and password before thesystem is actually restarted.

• 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 releasedautomatically after a savepoint. After the log has released, the oldest unused log segment can beoverwritten 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. Whenthe log is full, no more logging is possible until the log backup has completed. Automatic log backupprevents log full situations from arising.

• 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 systembehavior) and can be viewed on the Diagnosis Files tab in SAP HANA studio. We recommendusing SAP HANA studio to delete diagnosis files that are no longer needed.

• Before the SAP HANA database or SAP HANA software is upgraded to a new version, perform adata backup (including a configuration backup). This allows for the recovery of the system in casethe software upgrade fails.

• After the initial load has finished successfully, a data backup is strongly recommended.• For more information, see the SAP HANA Database – Backup and Recovery Guide.

Note:

• For replication scenarios during the initial data load - from ERP into the SAP HANA database – logwriting should not be switched off.

• There is no system table or log file that records the information that log writing has been switchedoff. For this reason, SAP does not recommend switching off the log during initial load. It is not possibleto check when log writing has been switched OFF/ON on customer systems.

2.7 Backup and Recovery

The backup and recovery functionality in SAP HANA is quite simple. The relevant content of all datavolumes of all services (name server, index server, statistics server) that belong to a single host/nodeinstance are marked by an instance-wide save point. This content is written into service-specific backupfiles located in the file system. The system/tools will take care of the details of backup/recovery; theuser just has to call up the functions.

2012-05-0824




For more information, see the SAPHANADatabase – Backup and Recovery Guide. This Guide describesthe administration of the SAP HANA database in relation to backup and recovery. It deals with theimplementation of the backup and recovery features of the SAP HANA database.

2.7.1 In-Memory Data and Persistent Storage

The SAP HANA database holds the bulk of its data in memory for maximum performance, but still usespersistent storage to provide a fallback in case of failure.

During normal operation of the database, data is automatically saved from memory to disk at regularsavepoints.

Additionally, all data changes are captured in the log. The log is saved from memory to disk after eachcommitted database transaction.

After a power failure, the database can be restarted like any disk-based database and returned to itslast consistent state by replaying the log since the last savepoint.

For more information see the SAP HANA In-Memory Database Backup and Recovery Guide.

2.7.2 Backup

Why are backups necessary?

Backups are required to protect against data loss due to disk failures. While savepoints and log writingprotect your data against loss due to power failures, this does not help when the persistent storageitself is damaged.

Data backup• Data backups should be performed regularly. No general guidelines are available. The backup

frequency depends on the usage scenario.• During data backups, the system is available as usual.• Data backups save data to the file system (mounted network drives are supported).

2012-05-0825



• The backup target directory should not be located on a dedicated disk (not the same disk as thedata or log volumes).

• You can carry out backup using the SAP HANA studio, DBA Cockpit or SQL statements on thecommand line (scheduling using scripts is possible).

• Space requirements:• Memory -> disk: some additional space needed (+ 10-50% = for shadow pages).• Disk -> backup: no additional space needed (only net occupied space is backed up).

Log backup:• The SAP HANA database automatically carries out log backups:

• When a log segment is full.• After a specified time.

• You can configure the log backup settings.• During log backups, the system is available as usual.

Note:Log backups need to be archived manually. It is recommended to monitor the available space in thetarget directory.

Configuration backup

The database configuration files (ini files) need to be backed up manually (copied to different locationusing operation system commands).

2.7.3 Recovery

Using data and log backups (and if available log entries from the log volumes), the SAP HANA databasecan be recovered.

A recovery may be necessary in one of the following situations:• Disk crash of the data area• Disk crash of the log area• Logical error, need to reset the database to an earlier point in time• Software upgrade failed

2012-05-0826


Recovery types

DescriptionRecovery Type

This recovery option uses the following data:• The last data backup available before the specified point in time• The entries from the log backups (and if needed the log entries from

the log area) between the data backup and the specified point in time

To a specified point in time

Note:This recovery type is an advanced option that is needed in case a previousrecovery failed.

This recovery option uses the following data:• The most recent data backup available before the specified log position• The entries from the log backups between that data backup and the

specified log position

To a specified log position

This recovery option uses the following data:• The specified data backup

Note:All log entries that still exist in the log are deleted. No log will be replayed.

Using a specific data back-up

Note:The recovery process of the SAP HANA database causes the database to be shut down. Duringrecovery, the system is therefore not accessible for end-users or applications.

2012-05-0827


2.8 Security

The SAP HANA Security Guide (Including SAP HANA Database Security) provides an overview of thesecurity-relevant information that applies to the SAP HANA appliance software. For more information,see the SAP HANA Security Guide (Including SAP HANA Database Security).

2.8.1 Auditing and Regulatory Compliance

• Starting with SAP HANA 1.0 SPS02, auditing functions will be provided.• There is an extensible auditing infrastructure.• Audit trails are stored using syslog:

• Syslog is a standard mechanism for logging program messages on Unix/Linux.• This makes it possible to separate the system on which the audit trails are stored from the system

that generates the audit trail (this is important for preventing database power user access to theaudit trails).

• Audit trails can be written to a variety of targets, including remote systems (important to achievesecure storage of the audit trails such as on dedicated servers).

• Both successful and unsuccessful events are logged in the audit trails.• Audit login is available for the following authorization changes:

• Create/drop user• Create/drop role• Grant/revoke role• Grant/revoke SQL privilege• Grant/revoke system privilege• Grant/revoke analytical privilege

2.8.2 Authentication

All access to the SAP HANA database from client networks is secured by authentication andauthorization.

Options for authentication:• Direct logon to the database with user name and password• Kerberos (single sign-on)

2012-05-0828


http://help.sap.com/hana/hana1_sec_en.pdf

A password policy exists that enforces password quality, regular password changes, and so on.

2.8.3 Authorization

The SAPHANA database has its own user and role management which enables customers to implementtheir user and role concept. Roles are assigned to users, and roles can also be assigned to roles (rolehierarchy).

The role concept provides the building blocks for granular access control, based on the users' tasks:• Business end users (consume reports using client tools, e.g. Microsoft Excel)• Modelers (create models and reports using SAP HANA studio)• Database administrators (operate and maintain the database and users, using studio), SYSTEM

administrator created during installation.

Tool support:• SAP HANA studio, command line access using SQL commands.

Privileges:• Logged-on users can only access data and execute commands that they have been explicitly

authorized for using privileges (no privilege, no access). Users can have privileges directly assignedto them, and/or inherit privileges from the role.

Privilege types:• SQL privileges (access to database objects such as tables, SQL ownership concept)• System privileges (for administrative tasks such as user management)• Analytical privileges (filters on models for reporting purposes, for read operations only)• Repository privileges

Note:Activation of objects from the repository is executed using a technical user. This ensures that the peoplewho are doing the modeling (design time) will not have access right to activated objects (runtime).

2.9 High Availability

The SAP HANA appliance software in general supports high availability scenarios. This inclues scaleout with standby host for the SAP HANA database. Currently only in a distributed system, some of theSAP HANA database servers are designated as worker hosts, and other servers are designated asstandby hosts. Multiple servers can be grouped together to allow a dedicated standby host to be assignedto each group. You can assign multiple standby hosts to each group. SAP HANA database supportscold standby hosts, where a standby host is kept ready for the event that a failover situation occursduring production operation. A standby host is not used for database processing. All the database

2012-05-0829


processes run on the standby host, but they are idle and do not allow SQL connections. It is not possibleto configure individual services on a standby host; all the services are configured together.

High availability configurations can have a negative impact on change performance, in particular speedof log-writing. For this reason, SAP generally recommends following scale-up rather than scale-outsizing for SAP HANA. Contact your hardware partner of choice for a SAP-certified high availabilitysolution for SAP HANA.

Contact your hardware partner of choice for a SAP-certified high availability solution for SAP HANA.

For more information, see the SAP HANA Database - Scaleout with Standby Host.

For related information on partitioning and distributing see, SAP HANA Database - Partitioning andDistribution of Large Tables

2012-05-0830


http://help.sap.com/hana/hana1_imdb_scale_en.pdf

http://help.sap.com/hana/hana_db_part_en.pdf

http://help.sap.com/hana/hana_db_part_en.pdf

Administering and Operating SAP HANA ReplicationTechnologies

3.1 SAP HANA Replication Technologies

3.1.1 Introduction

In-memory reporting and analyzing of business data requires the replication of the data from a sourcesystem to the SAP HANA database. This section provides an overview of the possible replicationmethods that are available for the SAP HANA appliance. It also describes the application fields andlists the main components required for each method.

2012-05-0831

Administering and Operating SAP HANA Replication Technologies

The figure above focuses on the task of loading business data from an SAP ERP system to the SAPHANA database.

The methods for performing data replication are shown in the figure below. The main componentsinvolved 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 WebIntelligence, are not part of the appliance software.

• Source system, such as SAP ERP• Software components supporting the data replication

The software components that support different methods of data replication are described in the followingreplication scenarios.

The figure above gives an overview of the alternative methods for data replication from a source systemto the SAP HANA database. Each method handles the required data replication differently, andconsequently each method has different strengths. It depends on your specific application field and theexisting 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 isbased on capturing database changes at a high level of abstraction in the source ERP system. Thismethod of replication benefits from being database-independent, and can also parallelize databasechanges on multiple tables or by segmenting large table changes.

• ETL-Based Replication

2012-05-0832


Extraction-Transformation-Load (ETL) Based Data Replication uses SAP BusinessObjects DataServices to specify and load the relevant business data in defined periods of time from an ERPsystem into the SAPHANA database. You can reuse the ERP application logic by reading extractorsor utilizing SAP function modules. In addition, the ETL-based method offers options for the integrationof third-party data providers.

• Log-Based Replication

Transaction Log-Based Data Replication Using Sybase Replication is based on capturing tablechanges from low-level database log files. This method is database-dependent.

Database changes are propagated on a per database transaction basis, and they are then replayedon the SAP HANA database. This means consistency is maintained, but at the cost of not beingable to use parallelization to propagate changes.

For more information about supported databases, see the Product Availability Matrix (PAM) on SAPService Marketplace https://service.sap.com/pam and search for SAP HANA.

3.1.2 Trigger-Based Replication

The Trigger-Based Replication method uses the SAP Landscape Transformation (LT) Replication Servercomponent to pass data from the source system to the SAP HANA database target system.

Initial Load and Simultaneous Delta Replication

2012-05-0833



The initial load of business data is initiated using the SAP HANA studio. The initial load message issent from the SAP HANA system to the SLT system (based on SAP NetWeaver 7.02 with kernel 7.20EXT), which in turn passes the initialization message to the ERP system. The ERP system begins bysetting up database transaction log tables for each table to be replicated. After the transaction tablesare completed, the SLT system begins a multi-threaded replication of data to the target system, whichenables high speed data transfer.

The initial load of data can be executed while the source system is active. The system load that thisprocess causes can be controlled by adjusting the number of worker threads performing the initialreplication.

In parallel to the initial load, by means of database-specific triggers, the SLT system begins detectingany data changes that occur while the initial load process is running. These changes are logged to thetransaction tables, and are propagated to the target SAP HANA system. The multi-version concurrencycontrol (MVCC) of the SAP HANA database prevents issues that might be caused by the overlappingof 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 tablesin the ERP system, and replicates data changes in the source system to the SAP HANA system in nearreal 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 optionsdepending 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)

For more information on Trigger-Based Replication, see SAP HANA Installation Guide – Trigger-BasedReplication.

3.1.3 ETL-Based Replication

Extraction-Transformation-Load (ETL) based data replication uses SAP BusinessObjects 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 therequired business data on the level of the application layer. You deploy this method by defining dataflows in Data Services and scheduling the replication jobs.

2012-05-0834




Since this method uses batch processing, it also permits data checks, transformations, synchronizingwith additional data providers, and the merging of data streams.

The figure above gives an overview of the ETL-based replication method. Here, data replication isoperated by Data Services. Its main components are the Data Services Designer, where you modelthe data flow, and the Data Services Job Server for the execution of the replication jobs. An additionalrepository is used to store the metadata and the job definitions.

For information about installing ETL-based replication, see SAP HANA Installation Guide.

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 Designerto set up datastores.

Datastore Setup

Setting up a datastore for the source system SAP ERP, choose SAP Applications for the type ofdatastore, and specify the address of the system, the user name and password allowing Data Servicesto 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 separatedatastore 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 themetadata imported from the ABAP Data Dictionary to Data Services, you can determine the business

2012-05-0835



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 useextractors.

Note:

• You must apply SAP 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, whichis the extractor. For the target of the replication, choose a template table, which is then used in the SAPHANA 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 asupdating the replicated data (delta handling) is done using SAP BusinessObjects Data Services. Theinitial load can be set up modeling a simple data flow from source to target. For the update, in mostcases, the data flow is enhanced by a delta handling element, such as Map_CDC_Operation orTable_Comparison Transform. It depends on the environment and the requested setup of the targettables 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 wherethe 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 availablefor 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 canchoose from different tools and methods for the scheduling. You can also use the Management Consoleto monitor the replication process.


This replication method requires the following main components:• SAP HANA database• SAP BusinessObjects Enterprise• BusinessObjects Enterprise Central Management Server (CMS), which is a part of SAP

BusinessObjects Enterprise• SAP BusinessObjects Data Services XI 4.0

For more information on the components of the SAP HANA database, see the Product Availability Matrix(PAM) on SAP Service Marketplace https://service.sap.com/pam and search for “SAP HANA”.

2012-05-0836




3.1.4 Log-Based Replication

The figure above gives an overview of the Transaction Log-Based Data Replication Using Sybase.

This replication method is only recommended for customers that have been invited to use thistechnology during the RTC of the SAP HANA product delivery. If you are not part of this RTCgroup, SAP recommends using Trigger-Based Data Replication Using SAP LT (LandscapeTransformation) Relication Server because of the rich feature set offered by this replicationtechnology.

The main components of this replication method are the Sybase Replication Agent, which is part of thesource system, SAP ERP, and the Sybase Replication Server that is to be implemented in SAP HANA.

Replication Process in Detail

2012-05-0837


The figure above shows details of the data replication process and introduces the additional componentsof this replication method.

Initial Load and Simultaneous Delta Replication

The initial load of business data needs to be executed only once to replicate the entire existing datasetfrom the source system to the target, SAP HANA database.

The SAP HANA Load Controller, a component that resides in SAP HANA, coordinates the entirereplication process: it starts the initial load of source system data to the SAP HANA database in SAPHANA, and communicates with the Sybase Replication Server to coordinate the start of the deltareplication.

The initial load can be executed while the source system is active, as described briefly below:• The Load Controller initiates the initial load by calling the SAP R3load component in the source

system. This is a special version of R3load available as a patch from SAP Service Marketplace.• The R3load on the source system exports the data for selected tables in the source system database

and directly transfers this data via sockets to the R3load component in SAP HANA without anyintermediate files.

• The R3load on the target system imports the data into the SAP HANA database.• The login authentication between the source system and the target system is handled by the SAP

Host Agent, which is usually part of the source system.

In parallel to the initial load, the Sybase Replication Agent in the source system is started and detectsany data changes that occur while the initial load is already running to cover every single change. Thisdetection is performed by reading the logs for committed transactions of the source system database.

2012-05-0838


The Replication Agent uses the table metadata from the database to connect the raw log informationwith the existing table names. In addition, the Replication Agent transfers all relevant raw log informationvia TCP/IP connection to the Sybase Replication Server on the SAP HANA side. The Replication Servercreates SQL statements from the raw log information received and sends these statements to theSybase Enterprise Connect Data Access (ECDA).

The ECDA connects to the SAP HANA database via Open Database Connectivity (ODBC) driver andreplicates the data changes from the source database by executing the SQL statements in the SAPHANA database. The multi-version concurrency control (MVCC) of the SAP HANA database preventslocks.

Continuous Delta Replication After Initial Load

The continuous delta replication captures the ongoing data changes in the source system in real timeonce the initial load and the simultaneous delta replication have been completed. All further data changesare captured and continuously replicated from the source system to SAP HANA using the same processas the simultaneous delta replication described above.


This replication method requires the following components:• SAP HANA Load Controller: controls the entire replication process by triggering the initial load and

coordinating the delta replication• Sybase Replication Agent: performs the log mining on the source database and relays all relevant

information to the Replication Server• Sybase Enterprise Connect Data Access (ECDA): connects to the target SAP HANA database via

ODBC• Sybase Replication Server: main component to accept data from the Replication Agent, distribute

and apply this data to the target database using ECDA/ODBC for connectivity• SAP Host Agent: handles the login authentication between source system and target system

3.1.5 Comparison of Replication Methods

This table compares the key features of each replication method.

2012-05-0839


Log-Based Replica-tion

(Sybase Replication)

ETL-Based Replica-tion

(Data Services 4.0 –SP2)

Trigger-Based Repli-cation

(SLT Replication)Capability

SAP ERP 6.0 (only ifunicode)

ERP 4.6c - SAP ERP6.0

SAP R/3 4.6C - SAPERP 6.0 (EHP06)

All other ABAP-basedSAP Applications (Ba-sis 4.6C-NW7.02)

Release coverage

Unicode OnlyYesYesUnicode/Non-Unicode

NoPartial (1)

Partial (If table containsonly ASCII charactersor language key is in-cluded)

MDMP

YesYesYesTransparent Tables

NoYesYesCluster & Pool Tables

Yes, but not in scopeYes

Yes (for SAP supportedDBs only: Informix outof maintenance, there-fore not supported,DB4 and Sybase ASEnot yet covered,planned with SPS04)

Non-SAP Sources

DB2 (9.1, 9.5, 9.7)YesYesCompressed ValuesDB Table

DB2 9.7 only (no sup-port for 9.1 or 9.5)YesYesRow Compression DB

Table

2012-05-0840








DB2 LUW/UDB Only

All SAP supportedDBs, incl. ASE, andothers: see PAM for fulllist

(no MaxDB support)

All SAP supportedDBs, incl. ASE

DB Support (Sourceside)

AIX, HP-UNIX, SUSELINUX 10 & SUSE Lin-ux 11, SPARC/Solaris,(see PAM for versiondetails)

All OS supported underERP (NO impact ofsource OS on DataServices)

All SAP supported OSOS Support (Sourceside)

YesNoNot covered yet(planned with SPS04)Transactional Integrity

Single Source Systemto single SAP HANAinstance

Multiple source sys-tems

Multiple source sys-tems to multiple SAPHANA instances (onesource system can beconnected to one SAPHANA schema only)

Multi-System Support

NoYesYesWorkload balancing(parallelization of repli-cation)

Real-time (by logicalwork units)ScheduledReal-time and sched-

uled (on table level )Real-time and/orscheduled replication

Initial load + delta repli-cation (always incl.repository info for alltables!)

Initial load + delta repli-cation (for table basedneeds delta informationthrough timestamp col-umn or through deltaenabled extractors)

Initial load, initial load+ delta replication forrelevant tables

Initial Load & Deltareplication

2012-05-0841








1:1

Complete ETL enginefrom simple functionsto very complex trans-formations

Default 1:1; capabilitiesfor conditional filtering& transformationsavailable on project ba-sis

Transformation capabil-ities

Performance dash-board (load progressand throughput status)

Via Data Services ownManagement Consoleor through the integra-tion with SAP SolutionManager

Support dashboardAccess to performancestatistics

Via Data Services ownManagement Consoleor through the integra-tion with SAP SolutionManager

YesAccess to troubleshooting feature

(1) SAP BusinessObjects Data Services will need a fixed code page for each run. In order to processMDMP, the same job will need to get executed multiple times, each time with a different code page andwith a WHERE clause on the language key. This would only be manageable for a limited number ofcodepages.

3.2 ETL-based Data Acquisition by SAP HANA Direct Extractor Connection

The Extractor-based Data Acquisition by SAP HANA Direct Extractor Connection technique providesa simple and straightforward means to work with Business Content DataSources in SAP HANA, usinga special configuration which sends data from an SAP Business Suite system to SAP HANA. With SAPHANA Direct Extractor Connection (DXC), the Business Content DataSources data models for SAPentities are available for use in SAP HANA. The data flow from the extractors is redirected, and insteadof flowing into SAP Business Warehouse, extracted data flows into SAP HANA directly.

For more information see, SAP HANA Installation Guide - ETL-based Data Acquisition by SAP HANADirect Extractor Connection

2012-05-0842




3.3 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 ETL-based replication: SAP BusinessObjects Data Services

• Monitoring components for Log-Based Replication: Sybase Replication

3.3.1 Monitoring Components for Trigger-Based Replication (SAP LT ReplicationServer)

For information about monitoring the SAP LT (Landscape Transformation) Replication Server, see theTechnical Operations Manual Trigger-Based Data Replication (SAP LT).

3.3.2 Monitoring Components for ETL-Based Replication (SAP BusinessObjects DataServices)

For information about monitoring SAP BusinessObjects Data Services, see• SAP BusinessObjects Data Services Management Console Guide

Information about how to use SAP BusinessObjects Data Services Administrator and SAPBusinessObjects Data Services Metadata Reports

• SAP BusinessObjects Data Services Administrator's Guide

Information about administrative tasks such as monitoring, lifecycle management, security, and soon

• SAP BusinessObjects Data Services Performance Optimization Guide

Information about how to improve the performance of SAP BusinessObjects Data Services

2012-05-0843


http://help.sap.com/hana/hana_slt_tom_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/sbo401_ds_mgmt_cons_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/sbo401_ds_admin_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/sbo401_ds_perf_opt_en.pdf

3.3.3 Monitoring Components for Log-Based Replication (Sybase Replication)

For information about monitoring Sybase Replication components, see• Verifying and Monitoring Replication Server

Describes checking error logs, verifying that the components of a replication system are running,and monitoring the status of system components and processes

• Using Counters to Monitor Performance

Describes how to use Replication Server counters to monitor performance

• Handling Errors and Exceptions

Describes various error handing methods for Replication Server

• Replication Server System Functions

Contains reference pages for the Replication Server system functions

3.4 Starting and Stopping SAP HANA

Follow these steps to start SAP HANA. To stop SAP HANA, stop these components in the reverseorder to starting them.1. Start the SAP HANA database.2. Start the Sybase Replication Server.3. Start the Sybase ECDA.4. Start the Sybase Replication Agent.5. Start the BI client (for example, Microsoft Excel).

3.4.1 Starting and Stopping the SAP HANA Database

You start and stop the the SAP HANA database with the SAP HANA studio.

Launch the SAP HANA studio and open the administration console pespective. If the administrationconsole perspective does not open automatically, you can open it manually fromWindow > OpenPerspective > Administration Console. To start or stop the SAP HANA database select it in the

2012-05-0844


http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc32518.1550/html/rsadmin_vol_2/BGBDBIFB.htm

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc32518.1550/html/rsadmin_vol_2/CIHDCFCC.htm

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc32518.1550/html/rsadmin_vol_2/BGBDFAHF.htm

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc32410.1550/html/refman/X92370.htm

Navigator, open the context menu with the right mouse button and select Start... or Stop... respectively.Also see Starting Systems and Stopping Systems in the SAP HANA Database Administration Guide.

3.4.2 Starting and Stopping Sybase Components

3.4.2.1 Starting and Stopping the Sybase Replication Server

For information about starting and stopping the Sybase Replication Server, see SYBASE ReplicationServer Administration Guide: Volume 1 -> Managing Replication Server with Sybase Central -> UsingReplication Manager from Sybase Central -> Starting and stopping Sybase Central.

3.4.2.2 Starting and Stopping Sybase ECDA

For information about starting and stopping Sybase ECDA, see Sybase Enterprise Connect Data Accessand Mainframe Connect Server Administration Guide -> Starting and Stopping the Server and AccessServices.

3.4.2.3 Starting and Stopping the Sybase Replication Agent

For information starting and stopping the Sybase Replication Agent, see SYBASE Replication AgentAdministration Guide -> Administering Replication Agent -> Determining current Replication Agentstatus.

3.4.3 Starting the Software Update Manager (SUM) for SAP HANA

For information about starting the Software Update Manager (SUM) for SAP HANA see the SAP HANAAutomated Update Guide -> Automated Update -> Performing an Automated Update

2012-05-0845



http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc32511.1550/html/rsadmin_vol_1/title.htm


http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc35365.1500/html/dirconag/title.htm

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc35365.1500/html/dirconag/title.htm

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc38261.1550/html/raxag/title.htm

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc38261.1550/html/raxag/title.htm



3.5 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 BusinessObjects Data Services

• Administering components for Log-Based Replication: Sybase Replication

3.5.1 Administrating Components for Trigger-Based Replication (SAP LT ReplicationServer)

For information about administering the SAP LT (Landscape Transformation) Replication Server, seethe Technical Operations Manual Trigger-Based Data Replication (SAP LT).

3.5.2 Administrating Components for ETL-Based Replication (SAP BusinessObjectsData Services)

For information about administrating SAP Business Objects Data Services components, see the followingguides:• Management Console Guide SAP BusinessObjects Data Services XI 4.0 (14.0.0)

• Data Services Administration Guide

• Information platform services Administration Guide

• Data Services Upgrade Guide

3.5.3 Administrating Components for Log-Based Replication (Sybase Replication)

For more information about administrating Sybase Replication components, see the following guides:• Sybase Administration Guide: Volume 1

2012-05-0846


http://help.sap.com/hana/hana_slt_tom_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ds_mgmt_cons_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ds_admin_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ips_admin_en.pdf



Managing Replication Server with Sybase Central•

• Managing a Replication System

• Managing RepAgent and Supporting Adaptive Server

• Managing Routes

• Managing Database Connections

• Managing Replication Server Security

• Managing Replicated Tables

• Managing Replicated Functions

• Managing Subscriptions

• Managing Replicated Objects Using Multisite Availability

• Scheduling Replication Tasks

• Administering Replication Agent

• Replication Agent Reference Manual

3.6 Backup and Recovery of SAP HANA Replication Technologies

You backup and recover the SAP HANA system landscape by extending the backup and recoverystrategy 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 ETL-Based Replication components: Data Services

• Backup and Recovery for Log-Based Replication components: Sybase Replication

3.6.1 Backup and Recovery for the Trigger-Based Replication components (SAP LTReplication Server)

For information about backup and recovery for the SAP LT (Landscape Transformation) ReplicationServer, 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 storereplication status for example).

2012-05-0847


http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc38261.1550/html/raxag/CIHDEAIB.htm

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00268.1550/html/ra155ref/title.htm

• 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, thereplication 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 logoption), initial load and replication have to be started again.

3.6.2 Backup and Recovery for the ETL-Based Replication components (SAPBusinessObjects Data Services)

For information about backup and recovery for SAP BusinessObjects Data Services, observe thefollowing:• 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 andtransformations, the workflows with load order etc. backup this database regularly.

• If the SAP HANA database needs to be recovered, can replication resume without any further userinteraction? Data Services provides batch loading for SAP HANA database, so no further userinteraction would be needed. The next time a batch load is started, it will be loaded into the databaseagain.

3.6.3 Backup and Recovery for the Log-Based Replication components (SybaseReplication)

For information about backup and recovery for the Sybase Replication, observe the following:• Supported: Recovery to the last committed state

• Not supported: point-in-time recovery of either the ERP system or SAP HANA

• Sybase Administration Guide: Volume 2

• Replication System Recovery

3.7 Security for the SAP HANA System Landscape

2012-05-0848



http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc32518.1550/html/rsadmin_vol_2/BEHCIBDD.htm

You ensure security for your SAP HANA system landscape by ensuring security of the SAP HANAcomponents:

For more information, see:• SAP HANA Security Guide (Including SAP HANA Database Security)

• SAP HANA Security Guide - Trigger-Based Replication (SLT)

• SAP HANA Security Guides - ETL-Based Replication (Data Services)• SAP BusinessObjects Data Services Administrator’s Guide

-> Security• SAP BusinessObjects Data Services Administrator’s Guide

-> User Rights and management• SAP HANA Security Guide - Log-Based Replication (Sybase)

2012-05-0849


http://help.sap.com/hana/hana1_imdb_sec_en.pdf

http://help.sap.com/hana/hana1_slt_repli_sec_en.pdf



http://help.sap.com/hana/hana1_rs_repli_sec_en.pdf

2012-05-0850


SAP HANA Data Management

You use the SAP HANA modeler, which is accessible as a perspective of the SAP HANA studio, formodeling and managing SAP HANA data. It allows technical users to create new or modify existingmodels of data. In addition, the initial configuration of the data replication is done in the SAP HANAmodeler.

4.1 Configuring Data Replication

Configure data replication to provide the necessary metadata and data to the SAP HANA box. Youneed 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 SAPHANA database(target system) for a selection of tables

• Start continuous replication of data changes from the data provider systems (source systems) intothe SAP HANA database (target system) for a selected subset of tables

Once the metadata and data are loaded to the SAP HANA box, you can create views and reports basedon these metadata and data, as described in Modeling Data.

For more information, see the SAP HANA Modeling 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.

2012-05-0851


http://help.sap.com/hana/hana1_model_en.pdf

For more information, see the SAP HANA Modeling Guide.

4.3 Modeling and Data Provisioning for ETL-Based Replication (SAP BusinessObjectsData Services)

When using the ETL-Based Replication technology by SAP BusinessObjects Data Services, you canalso model ERP data by means of Data Services modeling tools. The following documents describethe modeling and data provisioning steps you have to do in SAP BusinessObjects Data services:• SAP BusinessObjects Data Services Administrator’s Guide -> Server Management -> To configure

SAP HANA ODBC

• SAP BusinessObjects Data Services Reference Guide -> SAP HANA target table options

• SAP BusinessObjects Data Services Reference Guide -> Database datastores -> SAP HANA

• Designer Guide SAP BusinessObjects Data Services XI 4.0 (14.0.0)

Describes how to set up a job in the Designer to connect to any database

• Reference Guide SAP BusinessObjects Data Services XI 4.0 (14.0.0)

Describes the options for setting up connections to the SAP HANA database

• Supplement for SAP BusinessObjects Data Services XI 4.0 (14.0.0)

Describes all interactions with other SAP applications

2012-05-0852


http://help.sap.com/hana/hana1_model_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/sbo401_ds_admin_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/sbo401_ds_reference_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/sbo401_ds_reference_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ds_designer_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ds_reference_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_ds_sap_en.pdf

hana1 tom en_mp

Software

sap products

sap company

sap hana landscape

sap hana database

sap netweaver

operating sap hana

sap hana guides

sap group products