How to Configure Replication between two SAP HANA Cockpit

Step-by-Step Guide

www.sap.com

How to Configure Replication between two SAP HANA Cockpit Step-by-Step Guide SAP HANA Platform Edition 2.0

Ali Chalhoub

2

Document History

Document Version Authored By Description Date Created

1.0 Ali Chalhoub

First release of this whitepaper April 06, 2020

Reviews Reviewer Description Review Date

Jose Ramos

First release of this whitepaper April 07, 2020

TABLE OF CONTENTS

Document History ...................................................................................................................................................... 2

Chapter 1 – Introduction ........................................................................................................................................... 4

Chapter 2 – Installations and Configuration .............................................................................................................. 4

Chapter 4 – Preparing the replication between two SAP HANA Cockpit .................................................................. 4

Chapter 5 – Configuring Replication .......................................................................................................................... 4

Chapter 6 – Testing replication .................................................................................................................................. 4

Chapter 7 – Troubleshooting ..................................................................................................................................... 4

CHAPTER 1 INTRODUCTION ...........................................................................................................................5

Overview of the Architecture .................................................................................................................................... 5

Prerequisites .............................................................................................................................................................. 6

Requirements ............................................................................................................................................................ 7

Architecture Requirement ......................................................................................................................................... 7

Assumption ................................................................................................................................................................ 8

CHAPTER 2 INSTALLATIONS AND CONFIGURATION ........................................................................................9

Configuring SAP Web Dispatcher............................................................................................................................... 9

Installing the SAP HANA Cockpit Primary .................................................................................................................. 9

Installing the SAP HANA Cockpit Secondary ............................................................................................................ 11

3

CHAPTER 3 PREPARING THE REPLICATION BETWEEN TWO SAP HANA COCKPIT ............................................ 12

Preparing the primary.............................................................................................................................................. 12

Preparing the secondary .......................................................................................................................................... 27

CHAPTER 3 CONFIGURING REPLICATION ....................................................................................................... 31

Copying SSFS and xscontroller.ini ............................................................................................................................ 31

Configuring the primary ........................................................................................................................................... 32

CHAPTER 6 TESTING REPLICATION ................................................................................................................ 45

Add a database ........................................................................................................................................................ 45

Secondary taking over ............................................................................................................................................. 45

CHAPTER 7 TROUBLESHOOTING .................................................................................................................. 50

Replication button is missing to configure replication ............................................................................................ 50

Tier 2 System register error: primary and secondary has different SystemKPI SSFS .............................................. 50

503 Service not available ......................................................................................................................................... 51

Changes in file auto_install.cfg are not being applied during installation .............................................................. 52

4

Abstract

Chapter 1 – Introduction 1.1. Architecture and Environment

1.2. Prerequisites

1.3. Requirements

1.4. Assumption

Chapter 2 – Installations and Configuration 2.1. Configuring SAP Web Dispatcher

2.2. Installing the SAP HANA Cockpit Primary

2.3. Installing the SAP HANA Cockpit Secondary

Chapter 4 – Preparing the replication between two SAP HANA Cockpit 2.4. Preparing the primary

2.5. Preparing the secondary

Chapter 5 – Configuring Replication

3.1. Copying SSFS and xscontroller.ini

3.2. Configuring the primary

Chapter 6 – Testing replication

5.1. Add a database

5.2. Secondary taking over

Chapter 7 – Troubleshooting 5.3. Replication button is missing to configure replication

5.4. Tier 2 System register error: primary and secondary has different SystemKPI SSFS

5

Chapter 1 Introduction

Welcome to “How to Configure Replication between two SAP HANA cockpit Step-by-Step Guide” for SAP HANA

Platform Edition 2.0 On-Premise. In this whitepaper we will introduce you to all the requirements that are

needed in order to configure replication between two SAP HANA cockpit.

In this whitepaper we will discuss and show the user how to create and configure the environment:

• Prepare the environments

• How to enable replication

Overview of the Architecture

Before we can start our configuration, we need to look at the Architecture that this whitepaper will address. This

whitepaper will cover the following scenario:

Figure 1 Replication Architect

6

1. In the figure above, it is the general architecture implementation to replicate two SAP HANA cockpit.

a) We have one node which we will call it the “Headquarter”. That node will be the primary node

b) Another node which we will call “Waterloo”. That node will be the secondary node

2. We have to enable replication on the primary and replicates everything to the secondary

Note

This whitepaper is meant to show the administrator the minimum

steps that are needed in order to enable replication between two

SAP HANA cockpit.

Prerequisites

There are few requirements that must be met:

• Make sure the machines or VMs are backed up before starting the configuration in case anything goes

wrong, the administrator should be able to restore it back

• The primary and secondary systems are both installed and configured successfully. You have verified

that both are independently up and running after restarting them successfully

• This replication is done between two nodes only. No third tier is involved

• The number of nodes in secondary system must be equaled to the number of active nodes in the

primary system

• All configuration steps have to be executed on the master name server node; for SAP HANA Multitenant

Database Containers this means on the system DB (and not on the tenant DBS)

• The SAP HANA software version of the secondary has to be equal to or newer than the one on the

primary

• The secondary system must have the same SAP System ID, <SID>, and instance number as the primary

system. The primary replicates all relevant license information to the secondary

• System replication between two systems on the same host is not supported

• Changes to the ini file configuration parameters made on one system should be duplicated on the other

system. Note: Enabled the ini parameter replication on the primary site with [inifile_checker]/replicate =

true (from the “How To Perform System Replication for SAP HANA, in the help:

https://help.sap.com/viewer/4e9b18c116aa42fc84c7dbfd02111aba/2.0.04/en-

US/f65a9c62f60f4d4bb91620dd959ee68d.html?q=ini%20file%20checker

• An initial data backup or snapshot must be performed on the primary before the system replication can

be activated

Note

For more details in depth about replications, please refer to this following

detailed whitepaper:

https://assets.cdn.sap.com/sapcom/docs/2016/06/0ec37684-7a7c-0010-

82c7-eda71af511fa.pdf

7

Requirements

This setup should be done in a testing/development environment before it can be used and implemented in

production.

The architecture above is implemented in the following environment

Primary Node Secondary Node

• Host: cocpithost1 • Host: cockpithost2

• OS: SUSE SP15 PL01 • OS: SUSE SP15 PL01

• Site Name: Headquarter • Site Name: Waterloo

• Instance: 96 (Default) • Instance: 96 (Default)

• SID: H4C (Default) • SID: H4C (Default)

• OS: SUE Linux 15 SP01 • OS: SUSE Linux 15 SP01

• Port to be opened:39633 • Port to be opened:39633

Wildcard DNS: *.<YOUR-FQDN>

Web Dispatcher

Architecture Requirement

In order to enable replication between the two nodes or SAP HANA cockpit servers and be able to failover to the

other node or the secondary and be able to use it, we need to update the architecture in order to support

wildecard DNS. So that you must have *.<FQDN> available. Please refer to the architect below

8

1. Wildcard FQDN

2. Firewall

3. SAP Web Dispatcher to route the request

4. SAP HANA Database Cockpit which will be our headquarter with a role “Primary”

5. Replication between the “Primary” and the secondary SAP HANA Database Cockpit

Assumption

This whitepaper assumes the followings:

1. A wildcard domain available. So for example, if I have this domain, mycompany.net, then when you

issue from the command line ping command as follow, ping anything.mycompany.net, you should get

back a successful response. You cannot continue with this whitepaper before making sure this is setup

successfully

2. An SAP Web Dispatcher must be available and configured successfully. This whitepaper will only provide

the section configuration that is needed to enable Web Dispatcher to reroute the requests to the

appropriate SAP HANA cockpit

3. Two machines where Cockpits are not installed

4. This whitepaper will not discuss the installation and configuration of the SAP Web Dispatcher. For more

details about XSA failover, refer to this blog https://blogs.sap.com/2017/11/13/sap-hana-2.0-xs-

advanced-a-host-auto-failover-installationconfiguration-example/

9

Chapter 2 Installations and Configuration

Configuring SAP Web Dispatcher

As we mentioned, we assume the SAP Web Dispatcher is working successfully. Therefore, we need to add the

following configuration to your web Dispatcher instance profile.

1. Shutdown your Web Dispatcher

2. Edit the profile file you are using

3. Add the following content:

a. icm/server_port_3 = PROT=ROUTER,PORT=39633,TIMEOUT=60

b. icmd/HTTP/max_request_size_KB=-1

c. icm/max_conn = 2000

d. wdisp/system_3 = NAME=H4C, SRCVHOST=*39633,

EXTSRV=https://<COCKPIT-PRIMARY-

HOST>:39633#MAIN_INSTANCE;https://<COCKPIT-SECONDARY-

HOST>:39633#FAILOVER_INSTANCE

e. wdisp/server_3 = NAME=MAIN_INSTANCE, LBJ=1, ACTIVE=1

f. wdisp/server_4 = NAME=FAILOVER_INSTANCE, LBJ=-2147483647,

ACTIVE=1

g. Save the changes

h. Restart the SAP Web Dispatcher

Installing the SAP HANA Cockpit Primary

Now that we have the Web Dispatcher configured. It is time to install our first SAP HANA Database Cockpit.

Before starting the installation of SAP HANA Database Cockpit primary node. There is one more thing we need to

be aware of.

Note

During the installation of the Cockpit, the installer will not give you the

options to change the routing mode nor the ability to specify the domain

name which is in our case is the wildcard domain.

10

In order to change the routing mode and provide the domain name of our FQDN, we need to do the following:

1. If the the media, SAR, file is not unzipped, issue the following command

./SAPCAR -manifest SIGNATURE.SMF -xvf <Cockpit-MEDIA>.SAR

2. Make a backup copy of the auto_install.cfg which is located under the following folder “/<MEDIA-

INSTALLATION-DIRECTORY>/HDB__LCM_LINUX_X86_64/configurations/auto_install.cfg

3. Using text editor, for example vi , open the file auto_install.cfg

4. Change xs_routing_mode=ports to xs_routing_mode=hostnames

5. Change xs_domain_name=USE_DEFAULT to xs_domain_name=<YOUR-DOMAIN-NAME>, for example

xs_domain_name=mydomain.net or whatever the name is

6. Save your changes

7. Now that that we changed the configuration file under the folder HDB__LCM_LINUX_X86_64, we need

to invoke the installer that is located in the root of the media installation. Invoke the installer as follow:

./hdblcm.sh

8. Accept the default installation assuming you made the changes to the auto_install.cfg

9. Once the installation is done at the end you will see something displayed like that

10. Open Chrome browser and enter the following URL:

https://hanacokpit-sap-cockpit-web-app.<YOUR-DOMAIN>:39633

Note

Assuming you accepted the default installation value and the instance is 96 did not

change and the SID is H4C

11

11. If Everything is going well, you will see something like that:

12. We are done with the Primary node installation

Installing the SAP HANA Cockpit Secondary

• Repeat the same installation steps we have done on the primary node or server

• Follow the same steps we have done to the primary, do them on the secondary

12

Chapter 3 Preparing the replication

between two SAP HANA Cockpit

Preparing the primary

In this section we will go through all the steps that are to prepare the primary server for the Cockpit in order to

enable replication.

Accessing the Cockpit on the Primary host/server

1. Login to your server

2. Open your Web browser, preferably Chrome

3. Type the cockpit URL address, in our case that would be the wildcard FQDN domain name

https://api.<FQDN>:39633

4. Click on hana-cockpit-admin as shown below:

Figure 2 HANA Cockpit Admin access

13

5. Enter COCKPIT_ADMIN user information and click Log On button

Figure 3 Logon XS Advanced screen

6. You will get the following Not Authorized warning screen

Figure 4 Not Authorized warning screen

14

7. Click on OK

Figure 5 Creation of Role

8. Role now is created, you will be redirected to login back into the Cockpit Manager

Figure 6 Log on XS Advanced screen

15

9. Once we are successfully logged in into the SAP HANA cockpit Manager, click on Registered Resources if

the HANA Express Cockpit DB is not added.

Figure 7 Registering the resource

10. Click on the Register Resource button on the bottom of the screen

Figure 8 Adding a resource

16

11. Enter the information for the primary host name. In our example it is cockpithost1, as well the instance

number which is 96

Figure 9 Adding the cockpit information to manage it

12. Since we are not using encryption, deselect all the options, it should look like this below:

Figure 9 Encryption section

17

13. Click on Step 3

14. Enter the technical user in order to add the resource. In my example I am using SYSTEM user. If you do

not have the SYSTEM user, click the “Create New Technical User” in order to create a user.

Figure 10 Using technical or SYSTEM user to add the resource

15. Accept the default and click on Step 5

Figure 10 Using technical or SYSTEM user to add the resource

18

16. Accept the default and click on Review

Figure 11 Contact information

19

17. Review your configuration and click on Register

Figure 12 Review system configuration before adding it

20

18. Once the system is added, you should see the something similar to the screen below:

Figure 13 Resource details

19. On the bottom of the screen, click on Go to SAP HANA cockpit as shown below:

Figure 14 Detail screen of the node that is added

21

20. Once you are in the Cockpit, click on Resource Directory as shown below:

Figure 15 SAP HANA cockpit Resource Directory tile

22

21. Click on the Resource SYSTEMDB@H4C or whatever the name you chose

Figure 16 Resource section

22. If this is the first time you accessed your node and never logged into it through the Cockpit, you will be

presented with a logon screen. This one requires a database user as shown below. In our example, I am

going to use SYSTEM user to login with

Figure 17 Logon dialog box to HANA Express Edition DB

23

23. Under the System Overview, if replication has not been setup before, go to the Database Administration

and click on “Manage System configuration”

Figure 18 Manage system configuration

24. Under the search field, type log_mod and hit search

Figure 19 Search for log_mode

24

25. Once it is found, click on delete to remove it as shown below

Figure 20 Removing the overwrite value of log_mode

The end result should have only the default value of log_mode which is normal as shown below:

26. Once the log_mode is normal, now go back to the SYSTEM Overview screen and go to the System

Replication card and click on “Create a data backup to enable system replication”

Figure 21 Creating a data backup to enable replication

25

27. Click on Create Backup button

Figure 21 Creating backup

28. Accept the default and click Back Up

Figure 22 Performing backup of SAP HANA cockpit DB

26

29. Once backup is done, we should have something like that

Figure 23 Backup result

30. Go back to the home page of the Cockpit and click on

Figure 24 SAP HANA cockpit Home page

31. Next step we have to provide the credential for the <SID>adm in order for us to enable replication. Click

on the “Enter Credentials” link under SAP Control Credentials as shown below:

Figure 25 Host credential

27

32. Enter the user ID <SID>adm. For example in our case it is h4cadm and password, assuming this was not

changed and click on OK

Figure 26 Host OS credential

33. The end result, should look like the screen below:

Figure 27 Host OS credential information entered

Preparing the secondary

In this section we will go through all the steps that are required in order to prepare the secondary server for the

Cockpit.

Note

Note: All the resources will be replicated to the secondary via system

replication, you only have to register the secondary in the primary HANA

Cockpit. You can omit any configuration to the secondary. But it is good

practice to access the secondary and do the configuration to make sure it

is working properly.

28

1. Login to SAP HANA cockpit on the secondary

a. Before doing that we need to shutdown the primary node so the Web Dispatcher does not send

any requests to it

2. For example in our case that would be the URL: https://api.<FQDN>:39633 as shown below:

Figure 28 hana-cockpit-admin

3. Then follow all the same steps from step 1 until step 25 of the section “Preparing the Primary” above

on the secondary node. Once this is done, please continue the below steps

29

4. On the secondary node, click on the Resource Directory tile

Figure 29 SAP HANA Database Cockpit Home page

5. Add the Host control credential as shown below

Figure 30 Host control credential

30

6. Enter the <SID>adm use id and password and click on OK

Figure 31 Host OS Credentials for SAP Control

31

Chapter 3 Configuring Replication

In this chapter we will focus on how to configure replication between two SAP HANA Database Cockpits.

Copying SSFS and xscontroller.ini

Now that we have prepared both systems. Now we are ready to start configuring replication.

There are few requirements that must be done at this stage. The following files below MUST BE COPIED FROM

the primary node to the secondary node and replace the existing ones in the secondary node with the ones from

the primary. Make sure you have a backup copy of the VMS or systems before moving forward.

These files are listed below:

• In HANA 2.0 the System PKI SSFS key and data files must be copied from the primary to the secondary

site according to this SAP Note 2369981. These files are

1. /hana/shared/H4C/global/security/rsecssfs/data/SSFS_H4C.DAT

2. /hana/shared/H4C/global/security/rsecssfs/key/SSFS_H4C.KEY

• As well we need to copy the XSA Keys as well. For more information please refer to this SAP Note:

2300936

1. /hana/shared/H4C/global/xsa/security/ssfs/data/SSFS_H4C.DAT

2. /hana/shared/H4C/global/xsa/security/ssfs/key/SSFS_H4C.KEY

• Lastly we need to copy the /hana/shared/H4C/global/hdb/custom/config/xscontroller.ini

Note

At this stage, we need to make sure that secondary should not be

tried to be restarted. If it is running, keep it running.

32

Configuring the primary

Now that we are ready to configure the primary node, restart SAP HANA Database cockpit on the primary using

the command line and follow these steps on the primary server

1. From a Linux terminal and issue this command su - h4cadm ( assuming default SID is used)

2. HDB start

3. Once the database is up and running, login to SAP HANA cockpit Manager as shown below

Figure 32 hana-cockpit-admin

Note

• Make sure you start a fresh instance of Chrome and type the URL

of the SAP HANA Database Cockpit

• The hana-cockpit-admin will take between 3 to 7 minutes before

it can be accessed. So if you get the error 503 service not

available, just give it at least 5 to 7 minutes before it can be

ready. To check the status, check the Troubleshooting section

which explains how to monitor the starting process

33

4. Click on Registered Resources

Figure 33 Registered resources

5. Register the secondary Cockpit and follow the steps on how to register a node that we have done in the

section “Preparing the Primary”

34

6. Once these steps are done, we should have the primary and secondary added to the Cockpit as shown

below:

Figure 34 Systems managed by SAP HANA Database Cockpit on primary node

35

7. Go back to the primary SAP HANA Database Cockpit and click on “Resource Directory” tile

Figure 35 Accessing Resource Directory

Note

a. to access the Cockpit, click on this URL:

https://api.<FQDN>:39633

b. Select from the XSA bottom right screen “hana-cockpit”

36

8. Click on the Enter Credentials for the secondary node as shown below:

Figure 36 Secondary host OS credentials

9. Enter the credential which is <SID>adm of the secondary node and password

Figure 37 Host OS Credentials for SAP Control

10. Now click on the secondary Cockpit database as shown below

Figure 38 SAP HANA Database Cockpit Resources

37

11. Enter database user of the secondary node, in our example I am going to use SYSTEM as shown below

Figure 39 SAP HANA Database Cockpit user ID and password of the DB

12. Our setup now should look like this on the primary

Figure 40 Cockpit resources configuration

38

13. Click on SYSTEMDB@H4C for the primary node. Make sure it is the one for the primary

14. Click on System Replication card

Figure 41 System Replication

15. Click on Enable This System as Primary

Figure 42 Enabling the primary node to be a primary

39

16. Enter a name of your choice for your site. In my case I called it headquarter.

Note: Do not use names such as, PRIMARY, REMOTE or SECONDARY

Figure 43 System Details for replication site

17. Once it is done, click on Configure on the bottom right of the screen

18. Once the configuration is successful, we should have the following screen

Figure 44 Configure replication

19. Click on “Configure System Replication” Button

20. Fill the Tier 2 System Details as follow:

a. Site Name of the second tier, can be anything, in our case, it is called Waterloo

b. The secondary System Host, it is called cockpithost2. In your setup maybe it is called something

else. If you are not sure, click on the double squares on the right of the text field. It is called the

value help

c. Make sure you select the checkbox that says “The system has to be offline to register it as a

secondary…”

d. Replication Mode: You can select whatever is required for your application. In our test, we

chose Asynchronous

e. Operation Mode: We chose Log Replay

f. Initiate Data Shipping is set to No

g. Start the secondary system after registration is checked

40

h. Final result should look like the screen below

Figure 45 Replication configuration values

Note

Select the replication mode that satisfy your requirement. This paper

covers only a proof of concept of the replication. To learn more about

replication and the replication and operation mode. Please refer to the

following whitepaper https://archive.sap.com/kmuuid2/9049e009-

b717-3110-ccbd-

e14c277d84a3/How%20to%20Perform%20System%20Replication%20fo

r%20SAP%20HANA.pdf

41

21. Once you are done, click on Configure

Figure 46 Configuration of replication in progress...

42

22. Once it is done, it will look like this

Figure 47 Initial result of System Replication Overview

Note

The figure color is yellow and not green because the system

replication is in state “initializing”.

23. Give it few minutes and go back to the SAP HANA cockpit Home page still on the primary and click on

“Resource Directory” tile

Figure 48 Resource Directory

43

24. Click on SYSTEMDB@H4C that belongs to the primary as shown below

Figure 49 Listening of resources

25. Click on “System Replication” Card

Figure 50 System Replication card

44

26. We should see the following result. Which indicates replication is configured successfully

Figure 51 System Replication Overview summary

45

Chapter 6 Testing replication

Add a database

This is just a test use case, on the primary node add an instance of a database to be managed by the cockpit. Just

pick any instance of an existing database. Use the method that was described in this whitepaper.

Secondary taking over

To test now the replication, we need to do the following:

1. Login to the primary SAP HANA Database Cockpit using the following URL: https://api.<FQDN>:39633

2. Click on the Resource Directory tile

3. Click on the secondary database instance as shown below:

46

4. Click on System Replication card

47

5. Click on Take Over as shown below

6. Click on Start Takeover

48

7. You should see the following process is happening

8. If everything goes well, you should see the following

9. Click the Home button in Fiori launchpad

10. Now click back on the Resource Directory tile

11. You should see the following

12. Now the secondary took over and the replication is done

13. Assume the primary has a problem, shut it down by issuing HDB stop

49

14. Now open a new instance of Chrome and enter the URL https://api.<FQDN>:39633

15. Click on the bottom right on HANA Cockpit

16. If you get the error 503 Server not available, you need to wait at least 5 to 10 minutes before it can be

available.

17. Once XS engine is ready, you should see the following

18. Logon and you should see Fiori launchpad tiles listed

50

Chapter 7 Troubleshooting

Replication button is missing to configure replication

Issue:

When the user is trying to configure replication for the Cockpit, the user notices the button of replication

configuration is missing.

Resolution:

This issue is resolved in this

KBA: 2910382 - When using SAP HANA cockpit the replication buttons are missing

Tier 2 System register error: primary and secondary has different SystemKPI SSFS

Issue:

When trying to configure replication, the following error occurs.

Resolution:

The issue is the user forgot to copy the two SSFS files from these locations on the primary to the secondary

1. /hana/shared/H4C/global/security/rsecssfs/data/SSFS_H4C.DAT

2. /hana/shared/H4C/global/security/rsecssfs/key/SSFS_H4C.KEY

3. /hana/shared/H4C/global/xsa/security/ssfs/data/SSFS_H4C.DAT

4. /hana/shared/H4C/global/xsa/security/ssfs/key/SSFS_H4C.KEY

51

503 Service not available

Issue:

When starting SAP HANA Database Cockpit, the user is able to access the main XSA home page as follow

https://api.<FQDN>:39633, but when the user clicks on HANA-Cockpit link on the bottom right of the page, the

error 503 Service not available is displayed.

Resolution:

This is expected behavior because the Cockpit applications takes sometimes up to 10 minutes or more in order

to load. To monitor the load time and make sure everything is loading do the following:

1. On the machine that the Cockpit is restarted on open a Linux terminal

2. Issue su - h4cadm

3. Issue xs login

4. You should see something like this after login with the user COCKPIT_ADMIN

5. Now issue this command xs a

a. Check under the instances column, if the value is 0/1, that means the application still did not

load. In order to access the Admin Cockpit, cockpit-admin-web-app, the value of the instances

must be 1/1

b. Same things for the HANA Cockpit, check cockpit-web-app, 0/1

52

6. Wait sometimes and issue xs a again until you see this

7. Now open a new instance of Chrome assuming no web caching in place, issue this

URL: https://api.<FQDN>:39633

8. Access either one of the HANA-cockpit or HANA-cockpit-admin

9. You will be asked to login

10. Finally you should logged in successfully to the cockpit

Changes in file auto_install.cfg are not being applied during installation

Issue:

All the changes that are done in the file auto_install.cfg are not being taking into effect during the installation

Resolution:

If the changes are made to the following file, /<MEDIA-INSTALLATION-

DIRECTORY>/HDB__LCM_LINUX_X86_64/configurations/auto_install.cfg, and then you run the installer from

this directory, /<MEDIA-INSTALLATION-

DIRECTORY>/HDB_SERVER_LINUX_X86_64/configurations/auto_install.cfg , then any changes that are made to

the file, /<MEDIA-INSTALLATION-DIRECTORY>/HDB__LCM_LINUX_X86_64/configurations/auto_install.cfg, will

not be used during the installation. Therefore; If changes are made to the file located under

HDB_SERVER_LINUX_X86_64, then the user need to run the installer hdbinst under this folder. If the changes are

made to the file located under HDB__LCM_LINUX_X86_64, then hdbinst.sh needs to be ran.