Information about HANA

Home


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


2. 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. 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 Note 1929772 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 Notes 1637145 and 2296290.

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 Note 1702409).


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 Note 1781986. SAP Note 1899817 describes table distribution in scale-out scenarios

6. How to 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


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



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

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

SAP Note 2248291 describes details for running multiple applications on the same machine of a S/4HANA on-premise system.

Further information on SAP landscape recommendations can be found in the SAP HANA System Landscape Guide (http://www.saphana.com/docs/DOC-4385) and at http://wiki.scn.sap.com/wiki/display/SLGB/Landscape+Recommendations.


10. Which clients are supported for SAP HANA?

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



11. Where do I find logs and traces of SAP HANA?

The log and trace files are written to directory /usr/sap/<HANA_SID>/HDB<inst_number>/<host>/trace.

Example:

/usr/sap/C11/HDB00/saphana01/trace


12. What has to be considered for SAP HANA sidecar scenarios?

SAP HANA can be used for specific functionalities in parallel to a classic SAP database. This scenario is called sidecar or side-by-side. SAP Note 1694697 provides further details.


13. Can a SAP HANA database be renamed?

You can use the SAP HANA tool hdbrename in order to change the SAP HANA database name or the involved host names.

14. Can a SAP HANA schema be renamed?

No, it is not possible to modify the name of a SAP HANA schema.

15. Where do I find more information related to SAP HANA extended storage?

Extended storage typically contains "warm" data that is accessed from time to time. So there is neither a need to treat it as "hot" data (processed in SAP HANA memory) nor as "cold" data (located on near-line storage). Instead it is a layer in between.

See SAP Note 1983178 and the documents attached to it for further information of using extended storage in BW environments.

16. Where to find information related to SAP HANA Live?

SAP HANA Live allows real-time operational reporting. See http://www.saphana.com/docs/DOC-2923 and SAP Note 1778607 for further details.

17. Is it possible to configure an e-mail notification in case of critical SAP HANA states?

It is possible to configure e-mail notifications for SAP HANA alerts. See the related information in the SAP HANA administration guide (http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf) for more information. If you require a quick notification in case of certain problems you should check if an alert can be used to identify these problem situations. If that is not possible, you have to use other tools (e.g. SAP Solution Manager, third party monitoring tools) for setting up notifications.

For the future it is planned to set up individual alerts with SAP HANA which can then be used as basis for e-mail notifications.

18. Standard recommendation for setting SAP HANA parameters?

In most cases the default SAP HANA parameters are working fine, but for some reasons (e.g. workaround for bugs, individual optimizations or administrative settings) it is useful to adjust parameters based on the needs. SQL: "HANA_Configuration_Parameters" (SAP Note 1969700) can be used to check for parameters which might have to be adjusted. See SAP Note 2186744 for more information regarding SAP HANA parameter settings.

19. HANA support timezones?

Yes, see SAP Note 1791342 for more details.

20.  Daylight saving time and leap seconds?

The document Preparing Your SAP Environment for Daylight Savings Time provides an overview of DST related recommendations in SAP environments including a reference to important SAP HANA Notes.

Leap seconds are small time adjustments which can have critical impact like high load on Linux boxes. See SAP Note 1738172 for more information