-
Request for existing cases, user IDs, Portal navigation support and more
SAP HANA Database Scenarios
Managed System Setup for SAP HANA installations: If your SAP HANA database is installed with one or more nodes but without system replication or multi-tenancy. This guide will also apply to MCOD (Multiple Components One Database) databases which use different schemas for each SAP system.
Managed System Setup for SAP HANA with Multi-Tenant Database Container (MDC): If your SAP HANA system is installed as multi-tenant database container system some setup steps slightly differ from the standard SAP HANA installation. In an MDC system you have one system database and within this database you have several database containers which serve as isolated database for an SAP system.
Managed System Setup for SAP HANA with System Replication (SR): To support high-availability and disaster recovery you can install you SAP HANA system in a system replication scenario. In this case you continuously synchronize you SAP HANA system to a secondary location. This option is available for standard SAP HANA installations as well as for SAP HANA with MDC. If you SAP HANA system is using system replication for high-availability then some steps differ from the standard SAP HANA managed systems setup.
The picture below shows the different SAP HANA deployment options.
Check SAP HANA System in LMDB
Before running the managed system setup, you should check if the SAP HANA system was successfully reported from the SLD into LMDB of SAP Solution Manager. If you changed the SLDSYSTEMHOME for HANA to the SAPDBHOST in ABAP, the assignment between HANA and the ABAP system should happen automatically.
Even if the ABAP system already registered a HANA earlier via the RZ70 SLD data supplier, as long as HANA and the ABAP system register with the same SystemHome value, the assignment between HANA and ABAP system happen automatically. The formerly registered RZ70 HANA system will be enriched with the additional information from the HANA SLD data supplier.
Note: SAP HANA systems with MDC and/or System Replication will have to look differently in LMDB than a simple SAP HANA installation. Please refer to the respective wiki pages for more information.
- Call transaction LMDB and select your HANA system by switching the Type to SAP HANA Database and entering the relevant Extended System ID.
- Click on "Display" or "Edit". On the first page "System Overview" please verify that the product version is supplied automatically.
- Make sure all HANA nodes are reported under "Technical Instances". In our case it is just one node, for multi-node HANA databases you should see multiple lines under “SAP HANA Database Server”.
- In case your ABAP system is running on HANA, please check that the database is known to your ABAP system matches the HANA DB. To do this, open the ABAP system in LMDB and check the database information under System Database.
On the "Software" page, check the SAP HANA DATABASE software is marked as "Installed on Instance". This should at least be the case for the HANA master node.
Run Managed System Setup for HANA
The next step is to run the managed system configuration for SAP HANA. Unlike other database systems, SAP HANA has its own Technical System Type. Here we have to distinguish between a setup for a standalone HANA and an ABAP system having a HANA as a DB. For ABAP on HANA it is enough to execute the guided procedure for ABAP, which will include the HANA relevant steps as well.
Before you can run the managed system setup, make sure that the Diagnostics Agents for all HANA nodes are available. HANA nodes always register with their internal HANA hostname. So if you installed the agents manually without HLM but with the external HANA hostname you might have to create agents on-the-fly for the internal HANA hostnames. Or you just install the agents with the internal HANA hostname to begin with.
More information on agents on the fly can be found here.
To start the managed system setup for HANA, call transaction SOLMAN_SETUP → Managed System Configuration. Search for your HANA System. You'll find it on the tab “Technical Systems”.
In the first step Assign Product you have to assign product information to a technical system. To do so, click on Edit button at the top screen and click on Set Automatically to set a diagnostics-relevance flag.
In the second step Check Prerequisites you perform an automatic activity to verify if the prerequisites are met.
In the step Assign Diagnostics Agent an agent should be assigned to each server where a HANA node is installed. Furthermore, you can check the status of the corresponding SAP Host Agent.
In the next step you have to maintain the system parameters. To set up the DB Connection in this step you can use the same MONITOR user, created during HANA preparation steps for monitoring earlier.
If you have any problems creating the DB connection, check if there is a DB connection in table DBCON (transaction DBCO). If yes, test the connection using the report ADBC_TEST_CONNECTION. The output of this report will tell you what is wrong and also lead you to the trace file of the workprocess in which the error occurred. If the DB connection doesn't exist yet, please try to create it in DBCO and test it.
The most common reasons for failures here is a not correctly installed HANA client or missing HANA DB libraries. Please refer to the section about the HANA client installation from SAP HANA Managed System Setup section below.
In the Enter Landscape Parameters verify and add/change landscape parameters, if required.
The step Finalize Configuration consists mostly of automatic activities, which are relevant for data collection for scenarios like System Monitoring or Root Cause Analysis. Especially, ensure that the extractor relevant steps (Database Extractor and Extractor Setup) are finished successfully. The manual steps are relevant for a remote SAP support.
Check Configuration step performs a configuration check and updates a system status in the overview of the Managed System Configuration.
If you run a multi-node HANA DB, a manual step is required to make sure, that the HANA is still reachable, if the master node moves to another host.
To ensure that the HANA DB can be monitored and reached by DBACOCKPIT no matter who the master node is, you have to adjust the DB connection used by DBACOCKPIT. You have to add all possible HANA master node servers to the DB connection string.
Call transaction DBCO and open the DB connection for the HANA DB in change mode. Add the server names for all possible master nodes and ports separated by semicolon in the form:
<server1>:3<SysNo>15;<server2>:3<SysNo>15;<server3>:3<SysNo>15
Run Managed System Setup for ABAP on HANA System
Run the managed system setup for the ABAP on HANA system as usual. There will be some additional, ABAP relevant steps, like Maintain RFC's or Maintain Users, but in general the step sequence of the guided procedure is very similar to the one for HANA.