2000003 – FAQ: SAP HANA

1. Where do I find central information about SAP HANA?

SAP Notes 1514967 and 1523337 contain central information and important links for SAP HANA.
Documentation for current and previous SAP HANA releases is available at http://service.sap.com/hana and  http://help.sap.com/hana. Particularly important for the technical SAP HANA administration is the SAP HANA Administration Guide.
SAP HANA software can be downloaded via the SAP Software Download Center (SWDC).
The SAP Community Network (SCN) covers SAP HANA topics at http://scn.sap.com/community/hana-in-memory.
Useful troubleshooting information can be found in the SAP HANA Troubleshooting and Performance Analysis Guide.
At SAP Press the book SAP HANA Administration is published, that provides a detailed overview about SAP HANA architecture and administration tasks with some complementary information to the SAP HANA Administration Guide.
The following FAQ Notes and SCN references for central SAP HANA topics exist:

SAP Note / SCN Link Title   SAP Note / SCN Link  Title 
1640741 FAQ: SAP HANA DB Users for the DBA Cockpit 2116157 FAQ: SAP HANA Consistency Checks and Corruptions
1642148 FAQ: SAP HANA Database Backup and Recovery 2124112 FAQ: SAP HANA Parsing
1999880 FAQ: SAP HANA System Replication 2127458 FAQ: SAP HANA Loads and Unloads
1999930 FAQ: SAP HANA I/O Analysis 2142945 FAQ: SAP HANA Hints
1999997 FAQ: SAP HANA Memory 2143736 FAQ: SAP HANA Table Distribution for BW
1999998 FAQ: SAP HANA Lock Analysis 2147247 FAQ: SAP HANA Statistics Server
2000000 FAQ: SAP HANA Performance Optimization 2159014 FAQ: SAP HANA Security
2000002 FAQ: SAP HANA SQL Optimization 2160391 FAQ: SAP HANA Indexes
2000003 FAQ: SAP HANA 2165547 FAQ: SAP HANA Database Backup & Recovery in a SAP HANA System Replication Landscape
2014562 FAQ: SAP HANA LT Replication Server (SLT) 2169283 FAQ: SAP HANA Garbage Collection
2039883 FAQ: SAP HANA Database and Storage Snapshots 2177064 FAQ: SAP HANA Service Restarts and Crashes
2044468 FAQ: SAP HANA Partitioning 2177604 FAQ: SAP HANA Technical Performance Optimization Service
2053330 FAQ: SAP HANA Operations Recommendation for Alerts 2180119 FAQ: SAP HANA Smart Data Access
2057046 FAQ: SAP HANA Delta Merges 2180165 FAQ: SAP HANA Expensive Statements Trace
2057595 FAQ: SAP HANA High Availability 2186744 FAQ: SAP HANA Parameters
2073112 FAQ: SAP HANA Studio 2200772 FAQ: SAP HANA Statement Routing and Client Distribution Mode
2081591 FAQ: SAP HANA Table Distribution
2082286 FAQ: SAP HANA Graph
2100009 FAQ: SAP HANA Savepoints
2101244 FAQ: SAP HANA Multitenant Database Containers DOC-35203 FAQ: SAP BW on SAP HANA
2112604 FAQ: SAP HANA Compression DOC-62942 FAQ: SAP HANA Tailored Data Center Integration
2114710 FAQ: SAP HANA Threads and Thread Samples DOC-64640 FAQ: SAP HANA Operations
2115815 FAQ: SAP HANA Database Patches and Upgrades DOC-66702 FAQ: High Availability for SAP HANA

2. How can I determine SAP HANA topology details?

Topology details like involved hosts, services and roles can be determined in different ways:

Tool Details
M_SERVICES This monitoring view contains information about the available SAP HANA services and their roles.
You can use SQL: “HANA_Services_Overview” (SAP Note 1969700) for displaying this information.
M_TOPOLOGY_TREE This monitoring view provides further topology details. It must be started with an equal predicate on the PATH column. You can start with PATH = ‘/’ and then dig deeper level by level (e.g. PATH = ‘/host’, PATH = ‘/host/<host_name>’).
landscapeHostConfiguration.py You can use the script landscapeHostConfiguration.py in the python_support folder in order to display topology information. Unlike the monitoring views, this approach can also be used when SAP HANA is down.

3. What do SAP HANA error codes mean?

SAP HANA server error codes are positive numbers. You can determine further details including a short description via SQL: “HANA_ErrorCodes” (SAP Note 1969700).
If client connections are done using SQLDBC, negative SQLDBC error codes can be thrown. SAP Note1929772 provides an overview.

4. What has to be considered for BW on SAP HANA?

General information for operating BW on SAP HANA is available in SAP Note 1600929. Sizing SAP HANA for BW is described in SAP Note 1637145.
SAP Note 1729988 provides checks that can be performed when migrating an existing NetWeaver BW installation to SAP HANA.
SAP HANA scale out scenarios with BW take advantage of special table distribution and partitioning features. SAP Notes 1908073, 1908075 and SCN document http://scn.sap.com/community/hana-in-memory/blog/2013/09/03/ contain more detailed information.
Large tables on BW side can be handled as described in SAP Note 2019973.
If you want to run BW on a scale-out solution, at least three SAP HANA nodes should be used (SAP Note1702409).

5. What has to be considered for Suite on HANA?

The minimum requirement for Suite on HANA is NetWeaver release 7.40.
SAP cluster and pool tables are changed to transparent tables on SAP HANA, so compared to other SAP databases you can see some new physical table names on SAP HANA, e.g.:

  • Transparent table KONV instead of cluster table KOCLU
  • Transparent table BSEG instead of cluster table RFBLG
  • Transparent table CDPOS instead of cluster table CDCLS
  • Transparent table EDID4 instead of cluster table EDI40

SAP Note 1950470 describes the hardware prerequisites for Suite on HANA.
SAP Notes 1793345 and 1872170 contain sizing information for Suite on HANA.
SAP pilot Note 1781986 describes the prerequisites for scale-out scenarios on Suite on HANA. Customers interested in piloting SoH scale-out can open a SAP incident with reference to SAP pilot Note1781986. SAP Note 1899817 describes table distribution in scale-out scenarios.

6. How can the configuration and performance of the SAP HANA hardware, firmware and operating system be checked?

Information about certified and supported hardware in SAP HANA environments can be found in the SAP hardware directory.
For optimal performance you should make sure that the /tmp directory resides on a local file system (see SAP Note 2100296).
SAP Note 1943937 describes a hardware configuration check tool that provides functionality to check if the hardware performance is sufficient for a production SAP HANA installation.
See SAP Note 1922310 related to firmware changes in SAP HANA environments.
The following SAP Notes provide information related to specific OS or hardware products:

SAP Note Product Area
1824819 SLES SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP2
1954788 SLES SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP3
2205917 SLES SAP HANA DB: Recommended OS settings for SLES 12 / SLES for SAP Applications 12
1944799 SLES SAP HANA Guidelines for SLES Operating System Installation
1944415 SLES Configuration Guide for Hardware Platforms of SuSE Linux Enterprise Server
2013638 RHEL SAP HANA DB: Recommended OS settings for RHEL 6.5
2136965 RHEL SAP HANA DB: Recommended OS settings for RHEL 6.6
1650046 Lenovo Lenovo Solution for SAP HANA – Operations Guide
1661146 Lenovo Lenovo/IBM Check Tool for SAP HANA appliances
1880960 Lenovo Lenovo Systems Solution for SAP HANA Platform Edition FW/OS/Driver Maintenance
1930395 Lenovo HANA Server Disk Quota Administration
2100566 Lenovo Frequently Asked Questions for Lenovo/IBM saphana support script
2055470 IBM HANA on POWER Planning and Installation Specifics – Central Note
2133369 IBM SAP HANA on IBM Power Systems: Central Release Note

7. What has to be considered when opening an SAP incident?

SAP Note 1976729 contains an overview of application components that can be used for SAP HANA incidents.
SAP Note 1758890 lists the information that is required by SAP support to analyze the problem efficiently.
See SAP Note 1747042 and make sure that a database user with sufficient privileges is provided in case the SAP support needs to connect to the database directly.
SAP support may require a data export in order to reproduce a problem. SAP Note 1785797 describes how to perform an export.

8. What are the requirements for SAP support service deliveries in SAP HANA environments?

SAP Note 1892593 describes the necessary preparations that are required for a successful SAP support service delivery in SAP HANA environments.

9. What has to be considered for sizing SAP HANA?

Detailed sizing information for different environments can be found in the following SAP Notes:

Sizing Area SAP Note
General information 1514966
BW 1637145
BW 3.5: 2021372
Suite on HANA 1793345
Dynamic tiering 2086829
Smart data streaming 2184297
Remote data sync 2210231

10. How can I check the technical consistency of the SAP HANA database?

SAP Note 1977584 provides an overview of tools that can be used to verify the technical consisteny of the SAP HANA database and of related areas like backups.

11. Where can I find information about backup, restore and recovery of SAP HANA?

See SAP Note 1642148 for popular questions and answers in the area of backup, restore and recovery of SAP HANA. SAP Note 2091951 provides a best practice document for backups, restore and recovery.
SAP Note 2031547 lists the available 3rd party software products for backup operations (backint).
SAP Note 2039883 answers questions around storage snapshots in SAP HANA environments.

12. Which trace options exist in the SAP HANA environment?

SAP HANA provides many trace options for various purposes. Several of them can be found in the “Administration” –> “Trace Configuration” section of SAP HANA Studio.
See SAP Note 2119087 for more information.

13. Which limitations exist for the SAP HANA database?

See SAP Note 2154870 for limitations in the SAP HANA environment.

14. What are rule of thumbs for the performance and throughput of SAP HANA operations?

The following table lists some typical performance values for SAP HANA operations. The actual performance depends on many factors including parallelism, available resources and I/O speed, so the values are only rough indications for well-configured constellations and can’t be taken for granted.

Activity Duration / Throughput Details
R3load export 100 – 500 GB / h Export from source database (different from SAP HANA)
R3load import 100 – 1000 GB / h Import into SAP HANA database (throughput based on source database size)
Row store load 10 GB / min Throughput of loading row store information into memory during SAP HANA startup
Quick selection (row store) 0.02 ms Time an optimal selection from a SAP HANA row store table takes (server side)
Measured values on client side much higher due to network / communication overhead
Quick selection (column store) 0.05 ms Time an optimal selection from a SAP HANA column store table takes (server side)
Measured values on client side much higher due to network / communication overhead
Data backup 100 – 1000 GB / h Backup of data to disk
Data recovery (restore) 100 – 1000 GB / h Restore of a data backup
Log recovery 80 – 800 GB / h Recovery of logs
Column store startup after log recovery 100 – 1000 GB / h A log recovery builds up potentially large delta storages (SPS <= 09). They are merged table by table when SAP HANA starts up next time. The column store startup time after a log recovery depends on the amount of recovered data which influences the sizes of the delta storages.

15. Is it possible to run multiple SAP applications on a single SAP HANA appliance?

See SAP Note 1681092 that describes under what circumstances you can implement multiple SAP HANA databases on a single SAP HANA appliance.
See SAP Notes 1661202 and 1826100 that describes under what circumstances you can implement multiple SAP applications in a single SAP HANA database. This scenario is also called MCOD (“multiple components in one database”).
SAP Note 1953429 describes in which situations it is possible to run SAP HANA and a SAP NetWeaver application server ABAP on one host.
SAP Note 2024433 describes the prerequisites to run more than one SAP HANA virtual machine (VM) on one host.
Further information on SAP landscape recommendations can be found in the SAP HANA System Landscape Guide (http://www.saphana.com/docs/DOC-4385) and athttp://wiki.scn.sap.com/wiki/display/SLGB/Landscape+Recommendations.

16. Which clients are supported for SAP HANA?

SAP Note 1577128 provides information related to clients supported in SAP HANA environments.

17. Which timeouts exist on SAP HANA side?

The most important timeouts on SAP HANA side are:

Parameter Default Unit SAP Note Description  Error message
global.ini -> [backup] -> data_backup_savepoint_lock_timeout
7200 (2 hours) s 2100009 Time after which a backup is terminated when its savepoint is not finished successfully
global.ini -> [persistence] -> log_backup_timeout_s
900 (15 minutes) s 1642148 Time after which a log backup is performed at latest
global.ini -> [system_replication] -> logshipping_timeout
30 s 1999880 Time after which a synchronous replication of a log buffer is terminated
sr_dataaccess DisasterRecoveryPrimaryImpl.cpp(00369) : Closing connection to siteID 2.

Leave a Reply