Where do we find central information about SAP HANA?

Below are the important details about SAP HANA?  

SAP Notes 1514967, 1523337 and 2536742 contain central information and important links for SAP HANA.

Documentation for SAP HANA is available at http://help.sap.com/hana. Particularly important for the technical SAP HANA administration is the SAP HANA Administration Guide.

SAP Note 2402628 describes how to find SAP HANA documentation for earlier Revisions.

SAP HANA software can be downloaded via the SAP Software Download Center (SWDC).

Useful troubleshooting information can be found in the SAP HANA Troubleshooting and Performance Analysis Guide.

At SAP Press the books SAP HANA Administration and SAP HANA 2.0 – An Introduction are published.

SAP Note / SCN Link Title

1642148 FAQ: SAP HANA Database Backup and Recovery

1999880 FAQ: SAP HANA System Replication

1999930 FAQ: SAP HANA I/O Analysis

1999997 FAQ: SAP HANA Memory

1999998 FAQ: SAP HANA Lock Analysis

2000000 FAQ: SAP HANA Performance Optimization

2000002 FAQ: SAP HANA SQL Optimization

2000003 FAQ: SAP HANA

2014562 FAQ: SAP HANA LT Replication Server (SLT)

2039883 FAQ: SAP HANA Database and Storage Snapshots

2044468 FAQ: SAP HANA Partitioning

2057046 FAQ: SAP HANA Delta Merges

2057595 FAQ: SAP HANA High Availability

2073112 FAQ: SAP HANA Studio

2081591 FAQ: SAP HANA Table Distribution

2082286 FAQ: SAP HANA Graph

2100009 FAQ: SAP HANA Savepoints

2100040 FAQ: SAP HANA CPU

2101244 FAQ: SAP HANA Multitenant Database Containers

2112604 FAQ: SAP HANA Compression

2114710 FAQ: SAP HANA Threads and Thread Samples

2115815 FAQ: SAP HANA Database Patches and Upgrades

2116157 FAQ: SAP HANA Consistency Checks and Corruptions

2124112 FAQ: SAP HANA Parsing

2127458 FAQ: SAP HANA Loads and Unloads

2142945 FAQ: SAP HANA Hints

2143736 FAQ: SAP HANA Table Distribution for BW

2147247 FAQ: SAP HANA Statistics Server

2159014 FAQ: SAP HANA Security

2160391 FAQ: SAP HANA Indexes

2165547 FAQ: SAP HANA Database Backup & Recovery in a SAP HANA System Replication Landscape

2169283 FAQ: SAP HANA Garbage Collection

2177064 FAQ: SAP HANA Service Restarts and Crashes

2180119 FAQ: SAP HANA Smart Data Access

2180165 FAQ: SAP HANA Expensive Statements Trace

2185556 FAQ: SAP HANA Cockpit (delivered with SAP HANA 1.0)

2186744 FAQ: SAP HANA Parameters

2200772 FAQ: SAP HANA Statement Routing and Client Distribution Mode

2220627 FAQ: SAP HANA LOBs

2222110 FAQ: SAP HANA Load History

2222200 FAQ: SAP HANA Network

2222218 FAQ: SAP HANA Database Server Management Console (hdbcons)

2222220 FAQ: SAP HANA DBACOCKPIT

2222250 FAQ: SAP HANA Workload Management

2222277 FAQ: SAP HANA Column Store and Row Store

2336344 FAQ: SAP HANA Static Result Cache

2340450 FAQ: SAP HANA Table Replication

2366291 FAQ: SAP HANA Executed Statements Trace

2380176 FAQ: SAP HANA Database Trace

2393013 FAQ: SAP HANA Clients

SAP Note / SCN Link Title 

2393464 FAQ: SAP HANA Live Content Installation

2399993 FAQ: SAP HANA Fast Data Access (FDA)

2400005 FAQ: SAP HANA Persistence

2400006 FAQ: SAP HANA Statement Hints

2400007 FAQ: SAP HANA Runtime Dumps

2400022 FAQ: SAP HANA Smart Data Integration (SDI)

2412519 FAQ: SAP HANA SQL Trace Analyzer

2416490 FAQ: SAP HANA Data Aging in SAP S/4HANA

2444090 FAQ: SAP HANA Backup Encryption

2470289 FAQ: SAP HANA Non-Uniform Memory Access (NUMA)

2477204 FAQ: SAP HANA Services and Ports

2502256 FAQ: SAP HANA Caches

2506811 FAQ: SAP HANA Dynamic Result Cache

2520774 FAQ: SAP HANA Performance Trace

2535951 FAQ: SAP HANA Users and Schemas

 2554012 FAQ: SAP HANA Big Endian to Little Endian Migration for IBM Power

2570371 FAQ: SAP HANA Execution Engine (HEX)

2573880 FAQ: SAP HANA Full System Info Dump

2593571 FAQ: SAP HANA integrated liveCache

2596466 FAQ: SAP HANA XS Advanced

2599949 FAQ: SAP HANA Extended SQL Executor (ESX)

2600076 FAQ: SAP HANA Inverted Individual Indexes

2600095 FAQ: SAP HANA Sequences

2669621 FAQ: SAP HANA Capture and Replay

2670064 FAQ: SAP HANA Multi-Dimensional Services (MDS)

2700084 FAQ: SAP HANA Persistent Memory

2729787 FAQ: SAP HANA Data Supplier for System Landscape Directory (SLD) and Focused Run (FRUN)

2799997 FAQ: SAP HANA Native Storage Extension (NSE)

2799998 FAQ: SAP HANA Plan Stability

2800006 FAQ: SAP HANA Cockpit

2800007 FAQ: SAP HANA Temporary Tables

2800008 FAQ: SAP HANA Fulltext Indexes

2800020 FAQ: SAP HANA Triggers

2800028 FAQ: SAP HANA Optimizer Statistics

2800030 FAQ: SAP HANA Kernel Profiler

2800048 FAQ: SAP HANA TREXviaDBSL

2800055 FAQ: SAP HANA Kernel Sentinel

2899330 FAQ: SAP HANA KPI Collector

2975780 FAQ: SAP HANA LDAP Based Authentication and Authorization

3007062 FAQ: SAP HANA Third Party Cluster Solutions

3048191 FAQ: SAP HANA Local Secure Store (LSS)

3049706 FAQ: SAP HANA Hardware and Cloud Measurement Tools (HCMT)

3133628 FAQ: SAP HANA Web Dispatcher

3158257 FAQ: SAP HANA User Store (hdbuserstore)

3266082 FAQ: SAP HANA Cloud

3288971 FAQ: Pacemaker Cluster Resource Manager in SAP HANA System Replication Environments

3300523 FAQ: SAP HANA in the Neo Environment

How to removing the SAP HANA Service from topology and deamon.ini ?

In a single database container environment, carry out the following steps to remove SAP HANA XS from the topology:

Stop all the applications that use the database. This is required because a new data backup has to be created after you remove SAP HANA XS. A log replay over the time of the service removal is not supported.

Determine all the hosts on which SAP HANA XS services are active:

 -- >  select host from m_services where service_name = 'xsengine'

Determine the volume ID of the SAP HANA XS services:

-->   select VOLUME_ID from m_volumes where service_name = 'xsengine'

Stop the SAP HANA XS services. To do this, carry out the following command for every <host name> with an SAP HANA XS service:

--   ALTER SYSTEM ALTER CONFIGURATION ('daemon.ini', 'host', '<host name>') UNSET ('xsengine','instances') WITH RECONFIGURE

Remove the SAP HANA XS service entry from the topology. To do this, carry out the following command for every <host name> with an SAP HANA XS service:

--  ALTER SYSTEM ALTER CONFIGURATION ('topology.ini', 'system') UNSET ('/host/<Hostname>', 'xsengine') WITH RECONFIGURE

Remove the volumes from the topology. To do this, carry out the following command for every <volume_id> of an SAP HANA XS service:

--   ALTER SYSTEM ALTER CONFIGURATION ('topology.ini', 'system') UNSET ('/volumes', '<volume_id>') WITH RECONFIGURE

           Caution: It can be a risk to make changes to the topology. Therefore, carefully check the host and the volume ID.

Create a new data backup.

Start the applications that use the database.

 If you want to restart SAP HANA XS, proceed as follows:

Stop all the applications that use the database.

Activate SAP HANA XS. When you do this, specify the host on which you want SAP HANA XS to run:

 --   ALTER SYSTEM ALTER CONFIGURATION ('daemon.ini', 'host', '<host name>') SET ('xsengine','instances') = '1' WITH RECONFIGURE

 SAP HANA XS is started automatically, and the volumes of the service are created automatically.

Create a new data backup and start the applications that use the database.

In case XS Engine is still active and running: Determine the port of SAP HANA XS for the relevant tenant:

SELECT HOST, PORT FROM "SYS_DATABASES"."M_SERVICES" where DATABASE_NAME = '<tenant>' and SERVICE_NAME = 'xsengine'

Remove SAP HANA XS.

ALTER DATABASE <tenant> REMOVE 'xsengine' AT '<host>:<port>';

In case XS Engine is inactive / cannot be started:

get database_id:

select * from M_TOPOLOGY_TREE where path = '/databases' 

By default the database_id is 3, but it can differ if multiple tenants are configured. So please verify by:

select * from M_TOPOLOGY_TREE where path = '/databases/3' and name = 'name' and value = '<tenantdb name>'

get hostname:

select host from sys_databases.m_services where service_name = 'xsengine'

verify host name in topology.ini:

select * from M_TOPOLOGY_TREE where path = '/host/<host name>' and name = 'xsengine'

get volume id

select VOLUME_ID from sys_databases.m_volumes where service_name = 'xsengine'

verify volume in topology.ini:

select * from M_TOPOLOGY_TREE where path = '/volumes' and name = '<database id from step 1>:<volume_id>'

remove xsenine from daemon.ini:

ALTER SYSTEM ALTER CONFIGURATION ('daemon.ini', 'host', '<host name>') UNSET ('xsengine','instances') WITH RECONFIGURE;

remove xsengine from topology:

ALTER SYSTEM ALTER CONFIGURATION ('topology.ini', 'system') UNSET ('/host/<host name>', 'xsengine') WITH RECONFIGURE;

ALTER SYSTEM ALTER CONFIGURATION ('topology.ini', 'system') UNSET ('/volumes', '<database id>:<volume id>') WITH RECONFIGURE;

Verify that xsengine is removed:

select * from sys_databases.m_services where service_name = 'xsengine'

Do you want to add the XSengine service again?

see also https://help.sap.com/docs/SAP_HANA_PLATFORM/4fe29514fd584807ac9f2a04f6754767/ee36e3441ae24a7883ab353631ecd4d6.html?locale=en-US

ALTER DATABASE JS2 ADD 'xsengine' AT '<host name>';

Verify that xsengine is back and active:

select * from sys_databases.m_services where service_name = 'xsengine'

Note

Need to run the command from SYSTEM Database if your database is a part of MDC

It can be a risk to make changes to the topology. Therefore, only use the above procedure carefully and carefully check the hostname, database, and volume id.

Make sure that you have a valid data backup and that you also backed up your topology.