SAP HANA is a high-performance in-memory database that speeds data-driven, real-time decisions and actions. After the activation the metrics will be collected and the DB replication group will be visible in System Monitoring. This path doesn't exist and you need to adjust this value.
Dear SAPLearners, in this cloud platform blog post we will learn on how to create HANA Databases and Schemas in SAP Cloud Platform. Username: SYSTEM and Password: password provided during database creation, Click on OK to assign the necessary HANA roles to the user “SYSTEM”, HANA roles have successfully assigned. Now you can press the highlighted green arrow to create user. As of SAP Solution Manager 7.2 SP05 new templates 'Tenant Database Instance' and 'Tenant Database Instance (instance level separated)' were introduced to support the System Monitoring of MDC.
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. In addition, it performs advanced analytics (predictive analytics, spatial data processing, text analytics, text search, streaming analytics, graph data processing) and includes extract, transform, load (ETL) capabilities as well as an application server.
Unlike other database systems, SAP HANA has its own Technical System Type.
Go to the new primary SAP HANA database in SLD and look for the relation SAP_DatabaseReplicationDependency with the role Dependent. If yes, test the connection using the report ADBC_TEST_CONNECTION. ( using SYSTEMDB) Step 2 – Execute query ” select * from m_databases “. Now HANA Database is successfully created in SAP Cloud Platform. Open the Administration Console and select the HANA system. SAP HANA … the one which is used for a virtual DB) can be reached from SAP Solution Manager point of view. The most common reasons for failures here is a not correctly installed HANA client or missing HANA DB libraries. This guide will also apply to MCOD (Multiple Components One Database) databases which use different schemas for each SAP system. If you want to use only the database level template, you can do this by activating the SR specific metrics. This should at least be the case for the HANA master node.
HANA nodes always register with their internal HANA hostname. This tenants will not have a DB_
Note: If you have coincidentally set the parameter sql_connect_hosts to the correct logical host in SITEA and SITEB as described earlier, in SAP HANA rev. Now you can rerun the System Monitoring activation.
The DB Connection should show green now. For the SYSTEMDB it will first show the global SID and then after the connection is made it will change to SYSTEMDB. To do this, open the ABAP system in LMDB and check the database information under System Database. If yes, close and reopen the managed system setup. These metrics were moved in a template "SAP HANA DB Instance (instance level separated)" on instance-level.
For the primary database you will see the role Primary Database. Click on Continue.
You have to add all possible HANA master node servers to the DB connection string. Login into SAP Cloud Platform cockpit. Further details about a version can be found in the release notes. Make sure you have performed the OS and DB level preparations for the Managed System Configuration as described in the SAP HANA Managed System Setup section below. Please refer to the respective wiki pages for more information. Once database is created successfully, choose Overview and see the overview of the database like below. GRANT REPO.READ ON “xyz-package” TO PRAM; //This will give read access to package name ‘xyz-package ‘ to user. The manual steps are relevant for a remote SAP support. You should only do this if the system is not used in any logical components or monitoring yet. Also because it is an actual database it is maintained as Physical Database. To avoid a warning when saving the parameter you should uncheck the "Check existence of paths when saving" checkbox when you save this parameter. SITEA and SITEB are representing the corresponding sites of the replication scenario. In the Enter Landscape Parameters verify and add/change landscape parameters, if required. In this case, assign additionally to "SAP HANA DB (NEW)" template, a "SAP HANA DB Instance" template on an instance level. You just need to register SITEA for system replication with SITEB. If you want to use this template please make sure that you use the template "SAP HANA DB (instance level separated)" on database system level. If you never re-establish system replication the new relationships will not be reported into SLD/LMDB and you will not be able to activate the monitoring for the secondary database. In this case a manual adjustment will be obsolete, but it needs to be ensured that host name (e.g. Custom Code Management during S/4 HANA Conversion, Activating the Emergency User in SAP Java only system. The LMDB will be updated automatically within 10-15 minutes after deleting the relationship in SLD.
They are easily identified by the prefix 'SR:'. 6. Provide the login credentials. 2. This relation is created by the SLD association SAP_IdenticalDatabaseSystem. In the next step "Enter Landscape Parameters" you have to make sure you put in the correct path for installation path and log path for SYSTEMDB and each tenant. As the data foundation of SAP’s Business Technology Platform, it provides advanced analytics on multimodel data, on premise and in the cloud.
The Database + XS Advanced Applications install, includes the SAP HANA Cockpit, the SAP Database Explorer and the SAP HANA Web IDE. The two physical databases will be recognized automatically. 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.
For ABAP on HANA it is enough to execute the guided procedure for ABAP, which will include the HANA relevant steps as well.
To be able to set up your SAP HANA with System Replication (SR) in the way described below please note that your SAP Solution Manager system needs to run on SAP Solution Manager 7.2 SP3 or higher. This Website is not affiliated to SAP. Congrats!! SAP HANA is an in-memory, column-oriented, relational database management system developed and marketed by SAP SE.
Note: SAP HANA systems with MDC and/or System Replication will have to look differently in LMDB than a simple SAP HANA installation.
It will be deleted automatically in the secondary database as well. To overcome this situation, you have either to adjust this parameter manually (every time a take-over is performed) or follow a recommended approach by using a virtual hostname instead of dedicated IP in field "Used DB-Connect String", which is then valid for both sites. The relations are modelled like this: SAP HANA Database reported by the SAP ABAP System.
SOLMAN_SETUP will automatically recognize which databases belong to the scenario and select them accordingly. In case your ABAP system is running on HANA, please check that the database is known to your ABAP system matches the HANA DB. //This wll create user PRAM with password : XYZPassword, //This will grant read access to SAPXYZ schema to user, //This will assign ABAP_ADMIN role to user. Note: during DB Connection Setup: If you get the warning "DBA cockpit connection
Once database is created successfully, choose Overview and see the overview of the database like below.
Check Configuration step performs a configuration check and updates a system status in the overview of the Managed System Configuration.
On the view "Related Databases" the Primary Database is displayed under "Replication Relations". Note: that expert knowledge in SAP Solution Manager and SLD is required to successfully perform this setup. Its primary function as a database server is to store and retrieve data as requested by the applications. Before the take-over the virtual database points to SITEA as identical database. Add the server names for all possible master nodes and ports separated by semicolon in the form:
5. To start the managed system setup for HANA, call transaction SOLMAN_SETUP â Managed System Configuration. Now the new relationships are reported to SLD and you can begin the reconfiguration. Request non-product support or provide feedback on SAP Support Portal site. This would lead to problems in the monitoring and also the reporting. If the information supplied from SLD, correctly displayed in the LMDB, you can perform the Managed System Configuration. No.>.
In the step "Define Scope" select the virtual database (the one for which you also ran the managed system configuration). The best way to avoid this, is to enter the DB_
The template "SAP HANA DB (NEW)" also contains these SR specific metrics but they are shipped as inactive by default.
Instance-specific metrics are basically metrics that can be specified "by host". Click on SAP HANA Web-based Development Workbench link, this will open web-based development workbench like below. Search for your HANA System. 100 to 110 this association will be corrected automatically. Especially, ensure that the extractor relevant steps (Database Extractor and Extractor Setup) are finished successfully. After a take-over this value is not automatically adjusted in the step "Enter System Parameters" of Managed System Configuration for HANA.
No.>/ The step Finalize Configuration consists mostly of automatic activities, which are relevant for data collection for scenarios like System Monitoring or Root Cause Analysis. To set up the DB Connection in this step you can use the same MONITOR user, created during HANA preparation steps for monitoring earlier. The formerly registered RZ70 HANA system will be enriched with the additional information from the HANA SLD data supplier. Note: This section is mainly then relevant for you if you don't plan to fail back immediately but have to run the database on SITEB (the new primary site) for some time. The last step is the activation of the System Monitoring. Please refer to the section about the HANA client installation from SAP HANA Managed System Setup section below. Now HANA Database is successfully created in SAP Cloud Platform. If you changed the SLDSYSTEMHOME for HANA to the SAPDBHOST in ABAP, the assignment between HANA and the ABAP system should happen automatically. In the step Assign Diagnostics Agent an agent should be assigned to each server where a HANA node is installed. Your SAP HANA SR system must be set up following the recommendations in the SAP HANA installation guide and the primary system and the secondary system must be on two different hosts. Click on SAP HANA Cockpit link in database overview section. In our case it is just one node, for multi-node HANA databases you should see multiple lines under “SAP HANA Database Server”. This will lead to grey metrics, but at least not to double monitoring and wrong reporting. you have successfully created HANA Databases in SAP Cloud Platform. 4.