How to get hardware key of the ABAP system at OS LEVEL

 Login with <sid>adm

Cmd:

Saplikey -get

Output:

HARDWARE KEY = **************

Enqueue work process utilized percentage monitoring

 in this post, how much enqueue WP is filled info will be shown.

Practical steps:

1. Access the T-code SM12.

2.Resultant screen will looks like below:

     

3. Perform the below highlighted navigation.

    More --> Extra --> Statistics.

4. Maximum no of lock entries supported by the server is 441075

   Current filled level is 334519

Conclusion:

Almost 75%+ portion is filled.

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:

how to take snapshot for the EBS Volumes

Intro:

• Practical steps:

1. Login to AWS console.
2. Navigate to Services --> Compute --> EC2 --> Running instances--> select the EC2 instance.
3. Navigate to Volumes.

4. Select the check box for the volume and Navigate to Actions menu --> Create snapshot. For which snapshot is required. here i am considering root volumes.

5. Then the below screen will appears,Provide description & click on Crete snapshot.                                                                          

6.Conformation screen.Click on close.                                                                                                      

                                                                                         

7. Then from Volumes page. Navigate to snapshots screen.                                                                          

8. Snapshot created,can check the complete status here.                                                                               

How to change the EBS disk type

This post will answer the below question:

1.How to change the EBS disk type.

Practical steps:

Step1: 

          login aws console.

Step 2:

            Navigate to services -->compute -->EC2-->Running EC2 instance -->select the correct EC2 instance.  where the modification of EC2 instance is required.

Step 3:

 Under Elastic Block Store  --> click on volumes.

     Here in the availability zone column, each EBS disk can be found here.

              in the Volume Type column -->EBS type info is available.

To change the EBS drive type of one particular EBS drive to another type -->select the correct EBS drive -->Actions dropdown --> Modify volume(as highlighted below).

Note:

Here in the snapshot column, the snapshot value of represents the root drive.

Step4:                                                                                                                                                              

                                                                                                                                                   

Result for the Step 3 will be as below screen. Here in Volume type drop down select the target type of EBS drive. 

in this scenario, im changing from General purpose SSD(gc2)  type to provisioned iops SSD(io1). 

Step 5:                                                                                                                                                            

                                                                                                                                                           

Selected Provisioned IOPS SSD(io1) as my target type. Along with Volume type, we can change SIZE and IOPS range also in the same screen.

Step 6:                                                                                                                                                     

if any action required at OS level. the list of steps for the activity is available in the links highlighted below. Here the links are available for both Windows and Linux based systems.

Click on Yes. To proceed to next step.

Step 7:                                                                                                                                                      

Conform screen. Just click on Close here.                                                                      

---------------------------------------------------------------------------------------------------------------------------

Before performing the above activity, the Volume type is gc2.

Now it is io1. Hurrah!!! we have succeeded in change the EBS type.                                                         

How to extend the EBS volume size of EC2 instance.

This post will answer the below question:

1.How to extended the EBS volume size of EC2 instance.

Thumb rule:

• Whatever the availability zone the EC2 instance is running, in the same region the EBS volumes are available. the reason behind this rule is hard disk also should be near to mother board.
•  if in case the EC2 instance and EBS volume are in 2 different availability zones then manually need to make that available in single availability zone.

Advantage with EBS:

• can increase the EBS volume size and type on fly. No need to stop or shutdown the system.

Practical steps:

1. login aws console.

2.Navigate to services -->compute -->EC2-->Running EC2 instance -->select the correct EC2 instance.  where the modification of EC2 instance is required.

3. Under Elastic Block Store  --> click on volumes.

     Here in the availability zone column, each EBS disk can be found here.

              in the Volume Type column -->EBS type info is available.

   To extended the size of one particular EBS drive -->select the correct EBS drive -->Actions dropdown --> Modify volume.

4. Here in the below highlighted field the default size of EBS drive is 500GiB and can change the size here. just by enter the required size here in the highlighted field.

5.with in short time the additional storage will add in to the EC2 instance. & To adopt this additional storage few steps need to perform at OS level. This detail steps will be available in the below highlighted links(window or Linux) and finally click on YES to conform adding additional storage.

6.Then the below conform & succeeded screen will appears as shown below.                                           

7. if you click on refresh button as shown below the additional storage will update (services -->compute-->EC2 --> Running instance -->select the correct EC2 instance )

Now in the 3rd EBS disk size increase to 1000GB,can observe in the screenshot below

Pre-requisites for the SAP HANA instance before installation

Please log in as root user and create the following directories:

mkdir /hana

mkdir /hana/shared

mkdir /usr/sap

mkdir /hana/data

mkdir /hana/data/HDB

mkdir /hana/log

mkdir /hana/log/HDB

With the following command, we will format our 4 volumes with the ext3 file system (proceed with “y”):

mkfs -t ext3/dev/sdb

Proceed this way to format the remaining volumes:

mkfs -t ext3/dev/sdc

mkfs -t ext3/dev/sdd

mkfs -t ext3/dev/sde

Next, we will edit the file  vi/etc/fstab and add the following values, so our volumes will be automatically mounted every time we restart our system. With this, we will achieve that they always will be available as soon as we log in.

/dev/sdb             /usr/sap             ext3       defaults              0 0

/dev/sdc             /hana/data           ext3       defaults              0 0

/dev/sdd             /hana/log            ext3       defaults              0 0

/dev/sde             /hana/shared         ext3       defaults              0 0

With the command mount -a, all volumes displayed within fstab will automatically be mounted. Should you need to know and/or check, which volumes you have created and where they have been mounted to, you can use the df -h command for that:

For the rest of the process, a Java package will be required. You can easily install it on your Linux machine using the following commands:

wget http://javadl.sun.com/webapps/download/AutoDL?BundleId=83375

mv “FILE_NAME” java-linux-x64.rpm

Next, type in the following command in order to start unpacking your Java package:

rpm -ivh java-linux-x64.rpm

It is up to you whether you would like to download and decompress the data on a Windows machine or a Linux machine. Keep in mind, though, that the decompressed data must be readily available on your Suse Linux machine.

Within the Marketplace, we download the 10 RAR files – for instance on a Windows machine – and decompress these. For this, you will need a decompression tool such as WinRAR or 7-Zip.

The decompressed files can now be transferred to our SUSE server e.g. via SFTP:

Switch to the directory *DATA_UNITS/HDB_SERVER_LINUX_X86_64 and make the data executable with the following commands:

find -name  hdbinst   -exec chmod 744 {} +
find -name  hdbsetup  -exec chmod 744 {} +

find -name  hdbuninst -exec chmod 744 {} +
find -name  sdbrun    -exec chmod 744 {} +

In order to prevent the installation from aborting due to a hardware check, we must deactivate this functionality. Please note that the code below can only be deployed if you have the scripting language Python on your machine. I will just “guess” that you already have Python on your machine:

export IDSPISPOPD=”1″

python

>>> import os

>>> ‘IDSPISPOPD’ in os.environ.keys()

True

>>> quit()

 

Please make the file hdblcm within the subdirectory /HDB_LCM_LINUX_X86_64 executable:

chmod 744 hdblcm

Begin installation. Type in:

./hdblcm

Reference:                                                    

https://blogs.sap.com/2014/04/08/installing-sap-hana-sps-7-on-aws/