Search This Blog

Wednesday 30 December 2020

Install a Multiple-Host SAP HANA System Using the Command-Line Interface

 Pre - requisites and check:

  • minimum 2 HANA Appliance systems required.
  • Putty access for the both systems with root or any other using with read and execute permissions for the directory that contains .
  • Ensure NFS file system for /hana  mount point on both systems, using command df -h. 

  • The operating system administrator (<sid>adm) user and other operating system users may exist prior to installation. Make sure that you have the password of the existing users, and that the user attributes and group assignments are correct.
  • The SAP HANA system must be installed with its server software on a shared file system.                                            Create an installation directory. i.e /hana/shared.
  •       Set the export options rw,no_root_squash for the installation directory. for more info click here

  • Mount the installation directory on all hosts.                                 

    •     Depending on the desired storage solution. shared storage devices or separate storage devices with failover reassignment,

    different configurations apply:

     

    o     In a shared file system, the data files and log files are configured so that they are present and mounted on all hosts, including the primary host.

    o     In a system that uses separate storage devices, each host only has access to its own data files and log files.

     

    The suggested locations for the file systems are as follows:

     

    o   /hana/data/<SID›

     

    o   /hana/log/<SID>

     

    •     (Optional) Additional storage is configured.

     

    •     Root user name must be the same for all hosts in a multiple-host system.

     

    •     If the root user name is not root, it must be specified as a parameter during installation using the parameter root_user.

     



Context:                                                                                                                                                  

The following procedure describes the installation of an SAP HANA system in interactive mode and entering parameters interactively. This procedure may also be performed in advanced interactive mode or batch mode, with parameters entered as call options or from a configuration file. For more information about interaction modes and parameter entry methods, see Using the SAP HANA Platform LCM Tools in Related Information.

 

As of SAP HANA 2.0 SPS 01, the multi-container database mode is the only database mode. By default, a single tenant database is created during installation. You can add additional tenant databases later using the SAP HANA cockpit. SAP HANA options hosts or host roles can be automatically provisioned to a system that is installed with a single tenant. If the SAP HANA system contains multiple tenant databases, the SAP HANA options host or host role must be manually provisioned to the tenant.



Note

Not all parameters are requested interactively. Some parameters have default values that do not require confirmation in 


interactive mode. Those parameters must be specified as call options or from a configuration file. For more information 


about changeable default values, see Related Information.




Procedure:













Posted by at 1 comment:
Labels: , , , , , , , , , , ,

Saturday 19 December 2020

NFS - No Root Squash

 There are many options for NFS and I want to keep this article short but effective so I am leaving out many of the various configuration items that you could do. However there is one option that is worth mentioning, no_root_squash. By default NFS will downgrade any files created with the root permissions to the nobody user. This is a security feature that prevents privileges from being shared unless specifically requested.

If I create a file as the root user on the client on the NFS share, by default that file is owned by the nobody user.




Sometimes it is important to share files that are owned as root with the proper permissions, in these cases this can be done by simply adding the no_root_squash attribute to the /etc/exports configuration.



Adding no_root_squash

Edit the /etc/exports file:



Modify the /nfs line to:





Re-Export the exported file systems:

 root@server:/nfs# exportfs -a
Re-Mount the file system on the client:
root@client:~/# umount /shared/nfs1
 root@client:~/# mount -a

Now any file created by root should have root permissions.


Reference link:


https://bencane.com/2012/11/23/nfs-setting-up-a-basic-nfs-file-system-share/
Posted by at No comments:
Labels: , , ,

Sunday 6 December 2020

Different sync methods in SAP HANA HADR

 



Reference link:

https://blogs.sap.com/2019/10/18/sap-hana-high-availability/

Posted by at 2 comments:
Labels: , , , , , , , ,

SAP HANA database sizing with quick sizer


What is Sizing?                                                                                                                                      


  • For sizing we have identified three different and independent sizing models that have different advantages and disadvantages. The first two, user-based sizing and throughput-based sizing, have been implemented in the Quick Sizer.

Steps involved in Sizing:


  1. Access the web link for SAP sizing benchmark site: http://www.sap.com/sizing
  2. Navigate Quick Sizing section.



Based on the Business requirements,Select the required option.

    3. List of options available are almost same in all the 3 options.

         

4. Enter the details Customer no.  & Project Name. click on create project.
    Then the screen looks likes the below.
if you want to limit the user, you can here as highlighted below.

5. Shall limit the user access by the above highlighted option.

6. As a Next step, select the exact required Application in the left bottom side section.

7. input for sizing can be based on user based or throughput based or both.



 8. provide the remaining inputs also & click on calculate result.
9. The result with supportive hardware vendor will appears in the next screen.











Important links:

Posted by at No comments:
Labels: , , , , , ,

Saturday 5 December 2020

What is the major difference between single-container mode and multi-container mode?

 What is the major difference between single-container mode and multi-container mode?

An MDC system consists of a system database for overall system administration tasks and one or more tenant databases. Tenant databases are completely isolated in terms of persistence, database catalog, users, traces, etc.

Posted by at No comments:
Labels: , , , , , ,

Tuesday 1 December 2020

Determine Ports for SAP HANA Cockpit and Cockpit Manager

 The ports for SAP HANA cockpit and the cockpit manager can be determined in the XS console after the cockpit installation.

Prerequisites

  • You are logged in as <sid>adm user.
  • You know the XS organization manager user password. The password matches the master password, which is set during installation.

Context

Ports, through which the SAP HANA cockpit and the cockpit manager can be accessed, are assigned automatically by the installer. Once the cockpit installation is successfully completed, information about host and ports is displayed. If this information is no longer available, you can execute the following commands in the XS console to determine ports.

You can also assign free ports to SAP HANA cockpit during installation. For more information, see SAP Note 2389709 in Related Information.

Procedure

  1. Change to the directory that contains the XS Advanced installation:
    cd <sapmnt>/<SID>/xs/bin
    By default, <sapmnt> is /hana/shared.
  2. Log on to the SAP HANA XS advanced runtime. To do this, use the following command:
    ./xs-admin-login
  3. Enter the XS organization manager user password.
  4. Display a list of the applications running in the current space. In the command shell, run the following command:
    xs apps

    A list of all running apps is displayed. Information on host and ports are displayed in the urls column. The SAP HANA cockpit is listed as cockpit-web-app. The cockpit manager is listed as cockpit-admin-web-app.

Posted by at No comments:
Labels: , , , , , , ,
Subscribe to: Posts (Atom)