Post on 06-Apr-2018
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 1/42
SAP HANA Technical Operations Manual
■ SAP In-Memory Appliance (SAP HANA) 1.0
2011-06-23
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 2/42
© 2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAPBusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as
Copyright
well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and
other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports,Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of BusinessObjects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere,Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase 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.
2011-06-23
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 3/42
Contents
Getting Started with SAP In-Memory Appliance (SAP HANA)................................................5Chapter 1
About this Document...............................................................................................................51.1
SAP HANA Guides .................................................................................................................51.2
Related Information..................................................................................................................51.3
Important SAP Notes...............................................................................................................71.4
Software Download..................................................................................................................81.5Software Components.............................................................................................................81.6
Hardware and Software Requirements.....................................................................................91.7
What is SAP HANA?..............................................................................................................101.8
Operational Concept .............................................................................................................101.9
SAP HANA Replication Technologies...................................................................................13Chapter 2
Introduction............................................................................................................................132.1
Trigger-Based Replication......................................................................................................152.2
ETL-Based Replication...........................................................................................................162.3
Log-Based Replication...........................................................................................................192.4
Replication Methods Comparison..........................................................................................212.5
Monitoring the SAP HANA System Landscape.....................................................................25Chapter 3
Monitoring the SAP In-Memory Database..............................................................................253.1
Monitoring Components for Trigger-Based Replication (SAP Landscape Transformation
Replicator).............................................................................................................................26
3.2
Monitoring Components for ETL-Based Replication (SAP BusinessObjects Data Services)....263.3
Monitoring Components for Log-Based Replication (Sybase Replication)..............................273.4
SAP HANA System Management..........................................................................................29Chapter 4
SAP HANA Administration Overview.....................................................................................294.1
Administrating the SAP In-Memory Database.........................................................................294.1.1
Administrating Components for Trigger-Based Replication (SAP Landscape Transformation
Replicator).............................................................................................................................29
4.1.2
Administrating Components for ETL-Based Replication (SAP BusinessObjects Data
Services)................................................................................................................................30
4.1.3
2011-06-233
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 4/42
Administrating Components for Log-Based Replication (Sybase Replication).........................304.1.4
Starting and Stopping SAP HANA..........................................................................................314.2
Starting and Stopping the SAP In-Memory Database.............................................................314.2.1
Starting and Stopping Sybase Components...........................................................................314.2.2
SAP HANA Backup and Recovery.........................................................................................324.3
Backup and Recovery for the SAP In-Memory Database........................................................324.3.1
Backup and Recovery for the Trigger-Based Replication components (SAP Landscape
Transformation Replicator).....................................................................................................33
4.3.2
Backup and Recovery for the ETL-Based Replication components (SAP BusinessObjects Data
Services)................................................................................................................................33
4.3.3
Backup and Recovery for the Log-Based Replication components (Sybase Replication)........344.3.4
SAP HANA Data Management..............................................................................................35Chapter 5
Configuring Data Replication..................................................................................................355.1
Modeling Data.......................................................................................................................355.2
Modeling and Data Provisioning for ETL-Based Replication (SAP BusinessObjects Data
Services)................................................................................................................................36
5.3
High Availability....................................................................................................................37Chapter 6
Security.................................................................................................................................39Chapter 7
Updates and Support Packages ...........................................................................................41Chapter 8
2011-06-234
Contents
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 5/42
Getting Started with SAP In-Memory Appliance (SAPHANA)
1.1 About this Document
This Techinical 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 relevantadministration documentation of each of the components included in the SAP HANA solution are
provided for details and step procedures.
1.2 SAP HANA Guides
For more information about SAP HANA landscape, security, installation, and administration, see the
resources listed in the table below.
Quick LinkGuide/ToolTopic
https://service.sap.com/hana
• SAP HANA 1.0 Master Guide
• SAP HANA 1.0 Installation Guide
SAP HANA Knowledge Center
on SAP Service Marketplace
SAP HANA Landscape De-
ployment & Installation
http://help.sap.com/hana
• SAP HANA 1.0 Technical Operations
Manual
• SAP HANA 1.0 Security Guide
SAP HANA Knowledge Center
on SAP Help Portal
SAP HANA Administration
& Security
1.3 Related Information
2011-06-235
Getting Started with SAP In-Memory Appliance (SAP HANA)
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 6/42
For additional information about planning your deployment, see the following content on SAP Service
Marketplace:
LocationContent
https://service.sap.com/hana*
http://help.sap.com/hana
Latest documentation for SAP In-Memory Appliance (SAP
HANA)
http://sybooks.sybase.com/nav/base.doSYBASE Product Documentation
http://service.sap.com/instguidesLatest versions of SAP installation and upgrade guides
http://service.sap.com/sizingSizing, calculation of hardware requirements, such as CPU,
disk, and memory resources
http://service.sap.com/bosap-instguidesSAP BusinessObjects installation and deployment guides
http://service.sap.com/bosap-supportSAP BusinessObjects Support
http://service.sap.com/quicksizer Sizing, calculation of hardware requirements - such as CPU,
disk and memory resource - with the QuickSizer tool
http://service.sap.com/pamReleased platforms and technology-related topics such asmaintenance strategies and language support (Platform
Availability Matrix (PAM) )
http://service.sap.com/securityguideNetwork security
http://service.sap.com/haHigh Availability
http://service.sap.com/performancePerformance
http://service.sap.com/securitySecurity
http://service.sap.com/unicodeUnicode SAP systems and their availability
http://service.sap.com/sp-stacksInformation about Support Package Stacks, latest software
versions and patch level requirements
2011-06-236
Getting Started with SAP In-Memory Appliance (SAP HANA)
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 7/42
(*) 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:
Location on SAP ServiceMarketplaceContent
http://service.sap.com/mes
sagesInformation about creating error messages
http://service.sap.com/notesSAP Notes search
http://service.sap.com/swdcSAP Software Distribution Center (software download and ordering
of software)
http://service.sap.com/rktSAP Online Knowledge Products (OKPs) – role-specific learning
maps
1.4 Important SAP Notes
You must 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.
TitleSAP Note Number
SAP HANA 1.0: Central Note1514967
SAP In-Memory Database 1.0: Central Note1523337
Check the current SAP notes for the various parts of SAP HANA by searching for any of the following
CSS/CSN components:
SAP HANA
• BC-HAN SAP High-Performance Analytic Appliance
• BC-HAN-LOA Load Controler
• BC-HAN-MOD SAP High-Performance Analytic Appliance Modeler
2011-06-237
Getting Started with SAP In-Memory Appliance (SAP HANA)
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 8/42
• BC-HAN-REP Replication Server
• BC-HAN-UPD HANA update tool
• BC-HAN-UPD-UI User interface for HANA update tool
SAP In-Memory Database • BC-DB-HDB HDB
• BC-DB-HDB-DBA Database Administration for HDB
• BC-DB-HDB-ENG SAP In-Memory Computing Engine
• BC-DB-HDB-INS Installation HDB
• BC-DB-HDB-MDX MDX Engine/Excel Client
• BC-DB-HDB-PER Database Persistence for HDB
• BC-DB-HDB-SYS Database Interface/DBMS for HDB
• BC-DB-HDB-UPG Upgrade HDB
CSS/CSN search also supports * (asterisk) search, so you can, for example, also search for BC-DB-HDB*
or similar and you will get results for all sub-components.
1.5 Software Download
The components of SAP HANA and of the SAP In-Memory Database 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 further information please refer to
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 Software Components
SAP HANA Enterprise 1.0 comprises the following components:
• SAP In-Memory Database
• SAP In-Memory Database 1.0 - Server
• SAP In-Memory Database 1.0 – Studio (incl. IMDB JDBC 1.0)
• SAP In-Memory Database 1.0 - Clients
• IMDB ODBO 1.0
• IMDB JDBC 1.0
• IMDB ODBC 1.0
• IMDB SQLDBC 1.0
• SAP Host Agent 7.20
2011-06-238
Getting Started with SAP In-Memory Appliance (SAP HANA)
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 9/42
• SAPCAR 7.10
• Replication Technologies
• Log-Based Replication
• Sybase Replication Server 15 (incl. ECDA)
• Sybase Replication Server Agent 15
• SAP HANA Load Controller 1.00
• Trigger-Based Replication
• SAP LT 1 - SHC for ABA 46C (DMIS 2010_1_46C)
• SAP LT 1 - SHC for ABA 620 (DMIS 2010_1_620)
• SAP LT 1 - SHC for ABA 640 (DMIS 2010_1_640)
• SAP LT 1 - SHC for ABA 700 (DMIS 2010_1_700)
• SAP LT 1 - SHC for ABA 710 (DMIS 2010_1_710)
For the ETL-Based Replication you need the following components:
• SAP In-Memory Appliance (SAP HANA) Enterprise 1.0 (see above)
• Sybase Adaptive Server Enterprise (ASE) 15
• SAP BusinessObjects Data Services XI 4.0 (limited use)
1.7 Hardware and Software Requirements
Note:You find the complete list of all SAP HANA components and the respective SAP HANA hardware and
software requirements in the Product Availability Matrix (PAM) on SAP Service Marketplace
https://service.sap.com/pam.
Software Requirements
Operating System for SAP HANA 1.0
SUSE Linux Enterprise Server (SLES) 11 SP1 (see SAP Note 1310037 for information about installingSLES 11 SP1 in an SAP environment)
SAPCAR 7.10
(see SAP Note 212876 - The new archiving tool SAPCAR)
2011-06-239
Getting Started with SAP In-Memory Appliance (SAP HANA)
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 10/42
1.8 What is SAP HANA?
• SAP In-Memory Appliance (SAP HANA)
• SAP HANA is a flexible, data-source-agnostic appliance that allows 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 components
including the SAP In-Memory Database, Sybase Replication technology and SAP LT (Landscape
Transformation) Replicator.
• SAP HANA is delivered as an optimized appliance in conjunction with leading SAP hardware
partners.
• SAP In-Memory Database
• The SAP In-Memory Database is a hybrid in-memory database that combines row-based,
column-based, and object-based database technology. It is optimized to exploit parallel processing
capabilities of modern multi core/CPU architectures. With this architecture, SAP applications can
benefit from current hardware technologies.
• The SAP In-Memory Database is at the heart of SAP offerings like SAP HANA that help customers
to improve their operational efficiency, agility, and flexibility.
1.9 Operational Concept
2011-06-2310
Getting Started with SAP In-Memory Appliance (SAP HANA)
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 11/42
The SAP HANA operational concept describes the tasks, concepts, responsibilities, and procedures
necessary for the ongoing operation of the SAP In-Memory Appliance (SAP HANA). It answers the
following questions:
• Tasks and concepts - What tasks are to be performed and what concepts are they based on?
• Responsibilities - Who is responsible for each task? What is SAP responsible for and what does
SAP support? What do the SAP hardware partners do? What is the customer allowed to do?
• 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
administrating and monitoring SAP HANA.
SAP HANA is following the appliance delivery model. Hence it can only be retrieved via one of the
following listed, 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)
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://ser
vice.sap.com/hana or respective components administration guides at https://help.sap.com/hana.
The SAP HANA Operational Concepts provides information about the following topics:
1. SAP HANA components and landscapes
2. Service and Support
3. Installation, Implementation, and Hardware
4. Change Management (Updating and Patching)
5. Administration and Monitoring
6. Backup and Recovery
7. Security
For more information about SAP HANA Operational Concept, see the SAP Note 1599888 SAP HANA
1.0: Operational Concept.
2011-06-2311
Getting Started with SAP In-Memory Appliance (SAP HANA)
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 12/42
2011-06-2312
Getting Started with SAP In-Memory Appliance (SAP HANA)
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 13/42
SAP HANA Replication Technologies
2.1 Introduction
SAP In-Memory reporting and analyzing of business data requires the replication of the data from a
source system to SAP In-Memory Database (IMDB). This section provides an overview of the possible
replication methods that are available for SAP In-Memory Appliance (SAP HANA 1.0), 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 an SAP ERP system to the IMDBin SAP HANA.
There are three methods available for performing the data replication. The main components involved
in all replication scenarios are:
• SAP HANA, consisting of the IMDB and SAP In-Memory Computing Studio, which is used to
administer the appliance. User interfaces, such as SAP BusinessObjects Dashboards or Web
Intelligence, are not part of the appliance.
2011-06-2313
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 14/42
• 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 following
three replication scenarios.
The figure above gives an overview of the three alternative methods for data replication from a sourcesystem to the IMDB. Each method handles the required data replication differently, and consequently
each method has varying strong points. 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
The Trigger-Based Data Replication Using SAP Landscape Transformation (SLT) Replicator 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 also can parallelize database
changes on multiple tables or by segmenting large table changes.
• ETL-Based Replication
The 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 ERP
system into the IMDB. 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 3rd
party data providers.
• Log-Based Replication
The Transaction Log Based Data Replication Using Sybase Replication is based on capturing table
changes from low level database log files. This method is database dependant.
2011-06-2314
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 15/42
Database changes are propagated on a per database transaction basis, which are then replayed
on the IMDB. This means consistency is maintained, but at the cost of not being able to use
parallelization for change propagation.
For details about supported databases, see the Product Availability Matrix (PAM) on SAP ServiceMarketplace https://service.sap.com/pam (search for SAP HANA).
2.2 Trigger-Based Replication
The Trigger-Based Replication method uses the SAP Landscape Transformation (SLT) component to
pass data from the source system to the SAP In-Memory Database (IMDB) target system.
Initial Load and Simultaneous Delta Replication
The initial load of business data is initiated using the SAP In-Memory Computing Studio. The initial load
message is sent from the SAP HANA system to the SLT system (based on SAP NetWeaver 7.02 withkernel 7.20) which in turn passes the initialization message to the ERP system. The ERP system begins
by setting up database transaction log tables 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
allows high speed of data transfer to be achieved.
The initial load of data can be executed whilst 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.
2011-06-2315
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 16/42
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 logged to the
transaction tables, and are propagated to the target SAP HANA system. The multi-version concurrency
control (MVCC) of the IMDB prevents issues that could be caused by the initial load process and new
database transactions overlapping.
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: Component that controls the entire replication process by triggering
the initial load and coordinating the delta replication.
Installation considerations
The SLT system can be installed in two ways. 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
For further details about this topic, see SAP HANA 1.0 Installation Guide – Trigger-based Replication.
2.3 ETL-Based Replication
The Extraction-Transformation-Load (ETL) based data replication uses SAP BusinessObjects Data
Services (hereafter referred to as Data Services) to load the relevant business data from the source
system, SAP ERP, and replicate it to the target, SAP In-Memory Database (IMDB). This method allows
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 allows also for data checks, transformations, synchronizing
with additional data providers, and the merging of data streams.
2011-06-2316
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 17/42
The figure above gives an overview of the ETL-based replication method. Here, the 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 meta data and the job definitions.
For information about installing the etl-based replication, see SAP HANA 1.0 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 Designer
to set up Datastores.
Datastore Setup
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 IMDB, 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 IMDB, we recommend to use extractors.
2011-06-2317
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 18/42
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, which
is the extractor. For the target of the replication, choose a template table, which is then used in the
IMDB to store the replaced data.
Data Flow for Initial Load and Update
Both the initial load of business data from the source system into IMDB as well as updating the replicated
data (delta handling) is done using SAP BusinessObjects 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
serves your requirements best.
Although we recommend 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 suited where the
source system must be saved from additional load during the main business hours. Thereby you can
shift the replication work load, for example, to night-time. 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 use the Management Console
also to monitor the replication process.
Required Software Components
This replication method requires the following main components:
• SAP In-Memory Database
• SAP BusinessObjects Enterprise
• BusinessObjects Enterprise Central Management Server (CMS), which is a part of SAP
BusinessObjects Enterprise
• SAP BusinessObjects Data Services XI 4.0For more information on components of SAP In-Memory Database, see the Product Availability Matrix
(PAM) on SAP Service Marketplace https://service.sap.com/pam (search for “SAP HANA”).
2011-06-2318
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 19/42
2.4 Log-Based Replication
The figure above gives an overview of the Transaction Log Based Data Replication Using Sybase
Replication.
This replication method is only recommended for customers that have been invited to use this
technology during the RTC of the SAP HANA 1.0 product delivery. If you are not part of this RTC
group, SAP recommends using Trigger-Based Data Replication Using SAP Landscape
Transformation (SLT) Replicator because of the rich feature set this replication technology
offers.
The main components of this replication method are the Sybase Replication Agent which is part of the
source system, SAP ERP, and the Sybase Replication Server which is to be implemented in SAP HANA.
Replication Process in Detail
2011-06-2319
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 20/42
The figure above details the data replication process and introduces the additional components of this
replication method.
Initial Load and Simultaneous Delta Replication
The initial load of business data needs to be executed only one time to replicate the entire existing
dataset from the source system to the target, SAP In-Memory Database (IMDB).
The SAP HANA Load Controller, a component that resides in SAP HANA, coordinates the entire
replication process: It starts the initial load of source system data to the IMDB in SAP HANA, and
communicates with the Sybase Replication Server to coordinate the start of the delta replication.
The initial load can be executed while the source system is active. The process is 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 patch from the SAP Service Marketplace.
• The R3load on the source system exports the data for selected tables in the source system’s database
and directly transfers this data via sockets to the R3load component in SAP HANA without any
intermediate files.• The R3load on the target system imports the data into the IMDB.
• 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 detects
any data changes that occur while the initial load is already running to cover every single change. This
detection is realized by reading the logs for committed transactions of the source system’s database.
2011-06-2320
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 21/42
The Replication Agent uses the table metadata from the database to connect the raw log information
with the existing table names. In addition, the Replication Agent transfers all relevant raw log information
via TCP/IP connection to the Sybase Replication Server on the SAP HANA side. The Replication Server
creates SQL statements from the raw log information received and sends these statements to the
Sybase Enterprise Connect Data Access (ECDA).
The ECDA connects to the IMDB via Open Database Connectivity (ODBC) driver and replicates the
data changes from the source database by executing the SQL statements in the IMDB. The multi-version
concurrency control (MVCC) of the IMDB prevents from any locks.
Continuous Delta Replication After Initial Load
The continuous delta replication covers the running data changes in the source system in real time
once the initial load and the simultaneous delta replication have been completed: All further data changes
will be captured and continuously replicated from the source system to SAP HANA using the same
process as the simultaneous delta replication described above.
Required Software Components
This replication method requires the following components:
• SAP HANA Load Controller: Component that controls the entire replication process by triggering
the initial load and coordinating the delta replication.
• Sybase Replication Agent: Component that does the log mining on the source database and relays
all relevant information to the Replication Server.
• Sybase Enterprise Connect Data Access (ECDA): Component that connects to the target database
(IMDB) via ODBC.
• Sybase Replication Server: Main component that accepts data from the Replication Agent, distributes
and applies this data to the target database using ECDA/ODBC for connectivity.
• SAP Host Agent: Component that handles the login authentication between source system and
target system.
2.5 Replication Methods Comparison
On the following page is a table comparing key features of each replication method.
2011-06-2321
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 22/42
Log-BasedReplica- tionETL-Based ReplicationTrigger-Based ReplicationFeature
No
Only 1:1
YesNo
Only n backends to 1 SAP
HANA
n:m replication
(many-to-many relationship sup-
port)
NoYesYes, but is to be defined
manually during project
setup
Table data transformation during
replication (add or remove fields,
conversions)
NoYesYesFree of restriction to database
version or manufacturer
No
No
NW720 required (Delta
queue patch)
Yes
(separate SLT system re-
quired if source system
kernel < 720)
Free of restriction to operating
system version
NoYesYesPool tables supported
NoYesYesCluster tables supported
NoYesYes, but is to be defined
manually during project
setup
Client dependent replication
(client ID considered during table
replication)
NoNoPartlyDDIC updates
NoYesYesMonitoring or error mechanism or
GUI
Real timeDelay more than 30 minutesReal timeReal time or latency (speed of
replication)
Yes (negli-
gible)
Implementation dependantMinor Load on source system (source
system noticeably affected during
replication)
2011-06-2322
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 23/42
Log-BasedReplica- tionETL-Based ReplicationTrigger-Based ReplicationFeature
YesNo (delta mechanism to be
established; delta-enabled
extractors can be reused)
YesBuilt in delta mechanism (replica-
tion mechanism natively supports
propagation of changes on the
source system)
No (short
interrup-
tions pos-
sible)
n/a - scheduledYesOn-the-fly starting and stopping
of replication
(support for scheduled stopping
and starting of replication)
NoYesNoReuse of ERP business logic
2011-06-2323
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 24/42
2011-06-2324
SAP HANA Replication Technologies
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 25/42
Monitoring the SAP HANA System Landscape
You monitor the SAP HANA system landscape by monitoring the SAP HANA components:
• Monitoring the SAP In-Memory Database
• Monitoring components for Trigger-Based Replication: SAP LT (Landscape Transformation) Replicator
• Monitoring components for Trigger-Based Replication: SAP LT (Landscape Transformation) Replicator
• Monitoring components for Log-Based Replication: Sybase Replication
3.1 Monitoring the SAP In-Memory Database
For more information, see the SAP In-Memory Database – Administration Guide, section Periodic
Administration Tasks -> Monitoring
For monitoring your SAP In-Memory Database use the following checklist about administrative tasks:
1. Initial Administrative Tasks
After the initial load of the EPR data into the SAP In-Memory Database, carry out a data backup(including configuration backup). For more information, see the SAP In-Memory Database – Backup
and Recovery Guide .
2. Regular Administrative Tasks
Regularly check the system status on the Overview tab page of the administration screen in SAP
In-Memory Computing studio. Here, the most important system information is displayed:
• Overall system state
• General system information (software versions etc.)
• The warning section shows the latest warnings generated by the statistics server. Detail information
about these warnings is available as a tooltip. The warnings are 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.
2011-06-2325
Monitoring the SAP HANA System Landscape
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 26/42
• On the Services tab page of the administration screen in SAP In-Memory Computing studio,
check that all services that belong 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 only on the master host the service is actually running.
• The Overview tab page contains information about the status of your system services. Running
services are indicated with a green icon. Additionally information about resource usage and
possible bottlenecks is displayed.
• Regularly carry out data backups (including configuration backups). There are no general
guidelines for backup frequency (depends on the usage scenario). For more information, see
the SAP In-Memory Database – Backup and Recovery Guide.
3. Regular Administrative Tasks
• In case of problems with the SAP In-Memory Database, log and trace files can be checked for
errors. These log files are available in the SAP In-Memory Computing studio on the tab page
"Diagnosis Files" of the administration screen. To display a log file, choose "Open" in the context
menu of the list or just double-click the entry of the respective log file.
• In certain situations, you have to restart the system (for example, after a power failure). In the
Navigator of the SAP In-Memory Computing studio, open the context menu on the system entry
and choose Restart. After confirming the restart, you need to enter the operating system user
and password, before the system is actually restarted.
• If the disk on which the log is located fills up, carry out a data backup. This ensures that the log
space can be reused by the system.
• Before the database software is upgraded to a new version, carry out a data backup (including
configuration backup). This allows for recovery of the system in case the software upgrade fails.
After a system failure, carry out a recovery. For more information, see the SAP In-Memory Database
– Backup and Recovery Guide.
3.2 Monitoring Components for Trigger-Based Replication (SAP LandscapeTransformation Replicator)
For information about monitoring the SAP Landscape Transformation Replicator (SLT Replicator), see
the Technical Operation Manual for SAP NetWeaver .
3.3 Monitoring Components for ETL-Based Replication (SAP BusinessObjects DataServices)
For information about monitoring SAP BusinessObjects Data Services, see
2011-06-2326
Monitoring the SAP HANA System Landscape
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 27/42
• SAP BusinessObjects Data Services Management Console Guide
Information about how to use SAP BusinessObjects Data Services Administrator and SAP
BusinessObjects Data Services Metadata Reports
• SAP BusinessObjects Data Services Administrator's Guide
Information about administrative tasks such as monitoring, lifecycle management, security, and so
on
• SAP BusinessObjects Data Services Performance Optimization Guide
Information about how to improve the performance of SAP BusinessObjects Data Services
3.4 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
2011-06-2327
Monitoring the SAP HANA System Landscape
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 28/42
2011-06-2328
Monitoring the SAP HANA System Landscape
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 29/42
SAP HANA System Management
4.1 SAP HANA Administration Overview
You administrate the SAP HANA system landscape by monitoring the SAP HANA components:
• Administrating the SAP In-Memory Database
• Administrating components for Trigger-Based Replication: SAP LT (Landscape Transformation)Replicator
• Administrating components for ETL-Based Replication: SAP BusinessObjects Data Services
• Administrating components for Log-Based Replication: Sybase Replication
4.1.1 Administrating the SAP In-Memory Database
You administrate the SAP In-Memory Database using the administration console of the SAP in-memorycomputing studio. The administration console of the SAP in-memory computing studio allows technical
users to manage the SAP In-Memory Database as well as to create and manage user authorizations.
For more details, see the SAP In-Memory Database – Administration Guide.
4.1.2 Administrating Components for Trigger-Based Replication (SAP LandscapeTransformation Replicator)
For information about administrating the SAP Landscape Transformation Replicator (SLT Replicator),see the Technical Operation Manual for SAP NetWeaver .
2011-06-2329
SAP HANA System Management
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 30/42
4.1.3 Administrating Components for ETL-Based Replication (SAP BusinessObjectsData Services)
For information about administrating SAP Business Objects Data Services components, see the following
guides:
• 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
4.1.4 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
• 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
2011-06-2330
SAP HANA System Management
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 31/42
4.2 Starting and Stopping SAP HANA
Follow these steps to start SAP HANA. To stop SAP HANA, stop these components in the reverse
order to starting them.
1. Start the SAP In-Memory 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).
4.2.1 Starting and Stopping the SAP In-Memory Database
You start and stop the SAP In-Memory Database with the SAP in-Memory Computing studio.
1. Locate and double-clickhdbstudio.exe in your file system to launch the SAP in-Memory Computing
studio and Administration Console.
If the Administration Console does not open automatically, you can open it manually from window
> Open Perspective > Administration. For further information, see the Starting Systems and
Stopping Systems chapters in the Administration Guide - SAP In-Memory Database .
2. Don't you need more steps here to say how to start/stop SAP In-Memory Database using the AdminConsole?
If you are starting SAP HANA, the next step is to start the Sybase Replication Server.
4.2.2 Starting and Stopping Sybase Components
4.2.2.1 Starting and Stopping the Sybase Replication Server
For information about starting and stopping the Sybase Replication Server, see SYBASE Replication
Server Administration Guide: Volume 1 -> Managing Replication Server with Sybase Central -> Using
Replication Manager from Sybase Central -> Starting and stopping Sybase Central .
2011-06-2331
SAP HANA System Management
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 32/42
4.2.2.2 Starting and Stopping Sybase ECDA
For information about starting and stopping Sybase ECDA, see Sybase Enterprise Connect Data Access
and Mainframe Connect Server Administration Guide -> Starting and Stopping the Server and Access
Services .
4.2.2.3 Starting and Stopping the Sybase Replication Agent
For information starting and stopping the Sybase Replication Agent, see SYBASE Replication Agent Administration Guide -> Administering Replication Agent -> Determining current Replication Agent
status .
4.3 SAP HANA Backup and Recovery
You backup and recover the SAP HANA system landscape by applying backup and recovery to the
SAP HANA components:
• Backup and Recovery for SAP In-Memory 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
4.3.1 Backup and Recovery for the SAP In-Memory Database
SAP HANA, with it's core component the SAP In-Memory 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. The
log is capturing all changes by database transactions. Data and log are automatically saved to disk at
regular savepoints, the log is also saved to disk after each COMMIT of a database transaction.
The backup and recovery functionality in HANA 1.0 is quite simple. The relevant content of all data
volumes of all services (name server, index server, statistics server) that belong to a single host/node
2011-06-2332
SAP HANA System Management
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 33/42
instance are marked by an instance-wide save point. This content is written into service-specific backup
files located in the file system. The system/tools will take care of the details of backup/recovery; the
user just has to call up the functions.
For more information, see the SAP In-Memory Database – Backup and Recovery Guide. This Guidedescribes the administration of the SAP In-Memory Database in relation to backup and recovery. It
deals with the implementation of the backup and recovery features of the SAP In-Memory Database.
4.3.2 Backup and Recovery for the Trigger-Based Replication components (SAPLandscape Transformation Replicator)
For information about backup and recovery for the SAP Landscape Transformation Replicator (SLT
Replicator), observe the following:
• The SAP Landscape Transformation Replicator (SLT Replicator) creates a schema in the SAP
In-Memory 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 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.
4.3.3 Backup and Recovery for the ETL-Based Replication components (SAPBusinessObjects Data Services)
For information about backup and recovery for SAP BusinessObjects Data Services, observe the
following:
• Data Services stores its own metadata in a relational database (currently not the SAP In-Memory
Database). This metadata is the definition of the source and target connections, the mappings and
transformations, the workflows with load order etc. backup this database regularly.
• If the SAP In-Memory Database needs to be recovered, can replication resume without any further
user interaction? Data Services provides batch loading for SAP in-memory 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.
2011-06-2333
SAP HANA System Management
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 34/42
4.3.4 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 HANA
• Sybase Administration Guide: Volume 2
• Replication System Recovery
2011-06-2334
SAP HANA System Management
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 35/42
SAP HANA Data Management
You use the information modeler, which is accessible as a perspective of the SAP In-Memory Computing
Studio, for modeling and managing SAP HANA data. It allows technical users to create new or modify
existing models of data. Also the initial configuration of the data replication will be done in the information
modeler.
5.1 Configuring Data Replication
Use the configuring data replication to provide the necessary metadata and data to the SAP HANA
box. The following steps need to be performed:
• Load table metadata from the data provider systems (source systems) into the SAP In-Memory
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 to SAP In-Memory
Database (target system) for a selection of tables
• Start continuous replication of data changes from the data provider systems (source systems) into
to SAP In-Memory Database (target system) for a selection subset of tables
Once the metadata and data are loaded to the SAP HANA box you can create views and reports based
on these metadata and data (see chapter Modeling Data).
For details, see the SAP HANA 1.0 Modeling Guide, chapters:
• Importing Metadata
• Mass Import of Metadata
• Selective Import of Metadata
• Provisioning Data
5.2 Modeling Data
You use the information modeler for modeling and managing SAP HANA data.
2011-06-2335
SAP HANA Data Management
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 36/42
For more information, see the SAP HANA 1.0 Modeling Guide.
5.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 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 BusinessObjects Data services:
• SAP BusinessObjects Data Services Administrator’s Guide -> Server Management -> To configure
HANA ODBC
• SAP BusinessObjects Data Services Reference Guide -> HANA target table options
• SAP BusinessObjects Data Services Reference Guide -> Database datastores -> 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 HANA DB
• Supplement for SAP BusinessObjects Data Services XI 4.0 (14.0.0)
Describes all interactions with other SAP applications
2011-06-2336
SAP HANA Data Management
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 37/42
High Availability
SAP HANA 1.0 provides a scale out with standby host for the SAP In-Memory Database. Currently only
in a distributed system, some of the SAP In-Memory Database servers are designated as worker hosts,
and other servers are designated as standby hosts. Multiple servers can be grouped together to allow
a dedicated standby host to be assigned to each group. You can assign multiple standby hosts to each
group. SAP In-Memory Database supports cold standby hosts, where a standby host is kept ready for
the event that a failover situation occurs during production operation. A standby host is not used for
database processing. All the database processes run on the standby host, but they are idle and do not
allow SQL connections. It is not possible to configure individual services on a standby host; all theservices are configured together.
For more information, see the SAP In-Memory Database 1.0 - Scaleout with Standby Host.
2011-06-2337
High Availability
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 38/42
2011-06-2338
High Availability
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 39/42
Security
The SAP HANA Security Guide provides an overview of the security-relevant information that applies
to the SAP In-Memory Appliance (SAP HANA). For more information, see the SAP HANA Security
Guide.
You ensure security for your SAP HANA system landscape by ensuring security of the SAP HANA
components:
• SAP In-Memory Database - Security Guide
• 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)
2011-06-2339
Security
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 40/42
2011-06-2340
Security
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 41/42
Updates and Support Packages
Use the following SAP HANA update guides to update SAP HANA and its components:
• SAP HANA 1.0 Manual Update Guide
How to manually update SAP HANA and its components
• SAP HANA 1.0 Automated Update Guide
How to update SAP HANA and its components with the Software Update Manager (SUM)
2011-06-2341
Updates and Support Packages
8/3/2019 Hana1 Tom En
http://slidepdf.com/reader/full/hana1-tom-en 42/42
Updates and Support Packages