Scribd
Upload
279 views70 pages

S4 HANA Customer System Installation Guide

The document provides instructions for installing an S4 HANA Server 2020 Customer System. It outlines running prerequisite checks, installing HANA DB on the database node, and verifying system parameter settings with SAPTune to check compliance with SAP recommendations. Key steps include installing HANA DB, checking parameter settings with SAPTune, and ensuring several network and kernel parameters are configured as suggested in SAP notes to meet system requirements.

Uploaded by

sukumarreddyduvvuru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
279 views70 pages

S4 HANA Customer System Installation Guide

The document provides instructions for installing an S4 HANA Server 2020 Customer System. It outlines running prerequisite checks, installing HANA DB on the database node, and verifying system parameter settings with SAPTune to check compliance with SAP recommendations. Key steps include installing HANA DB, checking parameter settings with SAPTune, and ensuring several network and kernel parameters are configured as suggested in SAP notes to meet system requirements.

Uploaded by

sukumarreddyduvvuru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Installation guide S4 Customer System

______________________________
Rise With SAP
S4 HANA Server 2020 Customer System Installation
______________________________

1
Installation guide S4 Customer System

1. Prerequisite Checker

./sapinst SAPINST_REMOTE_ACCESS_USER=[Link]

2
Installation guide S4 Customer System

3
Installation guide S4 Customer System

4
Installation guide S4 Customer System

5
Installation guide S4 Customer System

2. HANA DB Installation

2.1 Install Hana DB on DBNode 2 ibmriss01db02

Check saptune

sudo saptune solution verify HANA

____________________________________________________________________________

SAPNote, Version | Parameter | Expected | Override | Actual |


Compliant

--------------------+------------------------------------+---------------------------+-----------+------------------------
+-----------

1771258, 5 | LIMIT_@dba_hard_nofile | @dba hard nofile 65536 | | @dba hard


nofile NA | no

1771258, 5 | LIMIT_@dba_soft_nofile | @dba soft nofile 65536 | | @dba soft


nofile NA | no

1771258, 5 | LIMIT_@sapsys_hard_nofile | @sapsys hard nofile 65536 | | @sapsys


hard nofile NA | no

1771258, 5 | LIMIT_@sapsys_soft_nofile | @sapsys soft nofile 65536 | | @sapsys


soft nofile NA | no

1771258, 5 | LIMIT_@sdba_hard_nofile | @sdba hard nofile 65536 | | @sdba


hard nofile NA | no

1771258, 5 | LIMIT_@sdba_soft_nofile | @sdba soft nofile 65536 | | @sdba soft


nofile NA | no

1980196, 7 | vm.max_map_count | 2147483647 | | 65530 |


no

2382421, 36 | [Link] | 4096 | | 128 | no

2382421, 36 | net.ipv4.tcp_max_syn_backlog | 8192 | | 2048 |


no

2382421, 36 | net.ipv4.tcp_slow_start_after_idle | 0 | |1 | no

6
Installation guide S4 Customer System

2382421, 36 | net.ipv4.tcp_syn_retries |8 | |6 | no

2382421, 36 | net.ipv4.tcp_timestamps |1 | |1 | yes

2382421, 36 | net.ipv4.tcp_window_scaling |1 | |1 | yes

2534844, 12 | [Link] | 32768 | | 4096 | no

2578899, 20 | IO_SCHEDULER_vda | none | | mq-deadline |


no

2578899, 20 | IO_SCHEDULER_vdb | none | | mq-deadline |


no

2578899, 20 | IO_SCHEDULER_vdc | none | | mq-deadline |


no

2578899, 20 | IO_SCHEDULER_vdd | none | | mq-deadline |


no

2578899, 20 | IO_SCHEDULER_vde | none | | mq-deadline |


no

2578899, 20 | rpm:tcsh | 6.20.00-4.9.1 | | 6.20.00-4.15.1 | yes


[3]

2578899, 20 | [Link] | start | | stop | no

2578899, 20 | [Link] | start | | start | yes

2578899, 20 | vm.dirty_background_bytes | 314572800 | |0 |


no

2578899, 20 | vm.dirty_bytes | 629145600 | |0 | no

2684254, 5 | KSM |0 | |0 | yes

2684254, 5 | THP | never | | always | no

2684254, 5 | energy_perf_bias | all:0 | | all:none | - [1]

2684254, 5 | force_latency | 70 | | all:none | - [1]

2684254, 5 | governor | all:performance | | all:none | - [1]

2684254, 5 | grub:intel_idle.max_cstate |1 | | NA | no [2]


[3] [6]

2684254, 5 | grub:numa_balancing | disable | | NA | no [2]


[3] [6]

2684254, 5 | grub:processor.max_cstate |1 | | NA | no [2]


[3] [6]

2684254, 5 | grub:transparent_hugepage | never | | NA | no


[2] [3] [6]

2684254, 5 | kernel.numa_balancing |0 | |1 | no

7
Installation guide S4 Customer System

941735, 11 | ShmFileSystemSizeMB | 413104 | | 193483 | no

941735, 11 | VSZ_TMPFS_PERCENT | 75 | | 35 | no

941735, 11 | [Link] | 1152921504606846720 | |


1152921504606846720 | yes

941735, 11 | [Link] | 18446744073709551615 | |


18446744073709551615 | yes

[1] setting is not supported by the system

[2] setting is not available on the system

[3] value is only checked, but NOT set

[6] grub settings are mostly covered by other settings. See man page saptune-note(5) for details

Attention for SAP Note 2684254:

Hints or values not yet handled by saptune. So please read carefully, check and set manually, if
needed:

# IBM EnergyScale for POWER8 Processor-Based Systems (applies to IBM Power systems only) - not
handled by saptune!

# Intel Cluster-On-Die (COD) / sub-NUMA clustering technology

# HANA is not supported neither on Intel Cluster-On-Die (COD) technology nor on sub-NUMA
clustering technology.

Attention for SAP Note 2382421:

Hints or values not yet handled by saptune. So please read carefully, check and set manually, if
needed:

# SAP HANA Parameters - all '.ini' file changes - not handled by saptune

# net.ipv4.ip_local_port_range

# As HANA uses a considerable number of connections for the internal

# communication, it makes sense to have as many client ports available as

# possible for this purpose.

# At the same time, you need to ensure that you explicitly exclude the ports

# used by processes and applications which bind to specific ports by adjusting

# parameter net.ipv4.ip_local_reserved_ports accordingly.

8
Installation guide S4 Customer System

# If configured correctly, the SAP Host Agent takes care of adjusting this

# parameter and setting it manually is neither recommended nor required.

# The SAP Host Agent typically increases the port range typically to 9000-65499.

# If your port range is significantly different, for example when your lower

# port range starts with port 40000, please check the SAP Host Agent section

# net.ipv4.ip_local_reserved_ports

# This parameter specifies the ports which are reserved for known applications.

# You especially also have to specify the standard ports that are used by the

# SAP HANA. To find out which standard ports are used by your SAP HANA please

# refer to SAP Note 2477204.

# Ports listed in this parameter will not be used by automatic port assignment,

# while explicit port allocation behavior is unchanged.

# If configured correctly, the SAP Host Agent takes care of the standard ports

# used by SAP HANA if the instance numbers are provided accordingly. Setting

# this configuration manually is neither recommended nor required.

# net.ipv4.tcp_wmem and net.ipv4.tcp_rmem

# These parameters specify the minimum, default and maximum size of the TCP

# send and receive buffer.

# They are mostly relevant for system replication scenarios with a latency

# higher than usual.

# The maximum value should be equal to at least the bandwidth delay product of

# the relevant connection.

# Both, tcp_wmem and tcp_rmem, are specified as three values separated by

# blanks: minimum, default and maximum buffer size.

# Preconditions for these settings to take effect are:

# * [Link].wmem_max and [Link].rmem_max must not be lower than the

# respective maximum value.

# * TCP window scaling has been enabled by setting net.ipv4.tcp_window_scaling=1

9
Installation guide S4 Customer System

# Example:

# net.ipv4.tcp_wmem = 4096 16384 4194304

# In this example, the current maximum is 4 MB. Given a 10 GBit/s connection

# with a latency of 1 ms, the required maximum would be

# 10 GBit/s * 1ms = 1.25 Mbytes, therefore the current setting is fine.

# If you want to saturate a 1 Gbit/s connection with a latency of 100 ms, the

# required maximum is 1 GBit/s * 100 ms = 12.5 Mbyte, so in this case the

# setting should be adjusted to at least 12.5 MByte.

# The minimum and the default buffer size do not need to be adjusted.

# [Link].wmem_max and [Link].rmem_max

# These settings define the maximum socket send and receive buffer size.

# To ensure complete functionality it must be ensured that the wmem_max and

# rmem_max values are at least the same as the respective maximum value of the

# parameters net.ipv4.tcp_wmem and net.ipv4.tcp_rmem.

# In landscapes where TCP timestamps are enabled please carefully evaluate if

# the following OS settings can be applied:

# net.ipv4.tcp_tw_reuse

# This setting allows HANA to reuse a client port immediately after the

# connection has been closed, even though the connection is still in TIME_WAIT

# state. A precondition for it to take effect is that TCP timestamps are

# enabled, i.e. net.ipv4.tcp_timestamps = 1, which is the default on most

# modern systems. Please note that this setting must not be applied if the HANA

# node needs to communicate with hosts behind a NAT firewall. Moreover, it must

# not be applied if not all hosts that use a TCP connection to communicate with

# the HANA node have TCP timestamps enabled. Otherwise you might encounter TCP

# connection issues after applying this configuration parameter.

10
Installation guide S4 Customer System

#net.ipv4.tcp_tw_reuse = 1

# net.ipv4.tcp_tw_recycle

# This setting reduces the time a connection spends in the TIME_WAIT state.

# One precondition for it to take effect is that TCP timestamps are enabled,

# i.e. net.ipv4.tcp_timestamps = 1, which is the default on most modern systems.

# Please note that this setting must not be applied if the HANA node has to

# communicate with hosts behind a NAT firewall. Moreover, it must not be

# applied if not all hosts that use a TCP connection to communicate with the

# HANA node have TCP timestamps enabled. Otherwise you might encounter TCP

# connection issues after applying this configuration parameter.

# In case you are running ABAP Application Server instances on Windows, please

# refer to SAP Note 2789262 for further details on possible connection issues.

# Starting from SUSE Linux Enterprise Server (SLES) 12 SP4 and SLES 15 GA this

# configuration is removed without substitution.

#net.ipv4.tcp_tw_recycle = 1

ERROR: The parameters listed above have deviated from the specified SAP solution
recommendations.

_____________________________________________________________________

Simulate the changes –

sudo saptune solution simulate HANA

11
Installation guide S4 Customer System

12
Installation guide S4 Customer System

sudo saptune solution apply HANA

13
Installation guide S4 Customer System

14
Installation guide S4 Customer System

Enter comma-separated list of the selected indices [3]: 2,3,4

Enter Installation Path [/hana/shared]:

Enter Local Host Name [ibmriss01db02]:

Do you want to add hosts to the system? (y/n) [n]: n

15
Installation guide S4 Customer System

Enter SAP HANA System ID: S00

Enter Instance Number [00]:

Enter Local Host Worker Group [default]:

Index | System Usage | Description

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

1 | production | System is used in a production environment

2 | test | System is used for testing, not production

3 | development | System is used for development, not production

4 | custom | System usage is neither production, test nor development

Select System Usage / Enter Index [4]: 1

Do you want to enable data and log volume encryption? [n]: y

Enter Location of Data Volumes [/hana/data/S00]:

Enter Location of Log Volumes [/hana/log/S00]:

Restrict maximum memory allocation? [n]:

Enter Certificate Host Name For Host 'ibmriss01db02' [ibmriss01db02]:

Enter SAP Host Agent User (sapadm) Password:

Confirm SAP Host Agent User (sapadm) Password:

Enter System Administrator (s00adm) Password:

Confirm System Administrator (s00adm) Password:

Enter System Administrator Home Directory [/usr/sap/S00/home]:

Enter System Administrator Login Shell [/bin/sh]:

Enter System Administrator User ID [1001]:

Enter ID of User Group (sapsys) [79]:

Enter System Database User (SYSTEM) Password:

Confirm System Database User (SYSTEM) Password:

Restart system after machine reboot? [n]:

Enter Installation Path for Local Secure Store [/lss/shared]:

Enter Local Secure Store User (s00crypt) Password:

Confirm Local Secure Store User (s00crypt) Password:

16
Installation guide S4 Customer System

Enter Local Secure Store User (s00crypt) ID [1002]:

Enter Local Secure Store User Group ID [80]:

Enter Local Secure Store User Home Directory [/usr/sap/S00/lss/home]:

Enter Local Secure Store User Login Shell [/bin/sh]:

Enter Local Secure Store Auto Backup Password:

Confirm Local Secure Store Auto Backup Password:

Summary before execution:

=========================

SAP HANA Database System Installation

Installation Parameters

Remote Execution: ssh

Database Isolation: low

Install Execution Mode: optimized

Installation Path: /hana/shared

Local Host Name: ibmriss01db02

SAP HANA System ID: S00

Instance Number: 00

Local Host Worker Group: default

System Usage: production

Do you want to enable data and log volume encryption?: Yes

Location of Data Volumes: /hana/data/S00

Location of Log Volumes: /hana/log/S00

SAP HANA Database secure store: ssfs

Certificate Host Names: ibmriss01db02 -> ibmriss01db02

System Administrator Home Directory: /usr/sap/S00/home

System Administrator Login Shell: /bin/sh

System Administrator User ID: 1001

ID of User Group (sapsys): 79

SAP HANA Database Client Installation Path: /hana/shared/S00/hdbclient

17
Installation guide S4 Customer System

Installation Path for Local Secure Store: /lss/shared

Local Secure Store User (s00crypt) ID: 1002

Local Secure Store User Group ID: 80

Local Secure Store User Home Directory: /usr/sap/S00/lss/home

Local Secure Store User Login Shell: /bin/sh

Software Components

SAP HANA Database

Install version [Link].1599235305

Location:
/sap-downloads/sap-downloads/SAP-Software-Download/HANA_Database_2_Installation_Revision_
52/HANA_Extracted/DATA_UNITS/HDB_SERVER_LINUX_X86_64/server

SAP HANA Local Secure Store

Install version [Link]

Location:
/sap-downloads/sap-downloads/SAP-Software-Download/HANA_Database_2_Installation_Revision_
52/HANA_Extracted/DATA_UNITS/HANA_LSS_24_LINUX_X86_64/packages

SAP HANA AFL ([Link],BFL,OFL)

Do not install

SAP HANA EML AFL

Do not install

SAP HANA EPM-MDS

Do not install

SAP HANA Database Client

Install version 2.5.109.1598303414

Location:
/sap-downloads/sap-downloads/SAP-Software-Download/HANA_Database_2_Installation_Revision_
52/HANA_Extracted/DATA_UNITS/HDB_CLIENT_LINUX_X86_64/client

SAP HANA Studio

Do not install

SAP HANA Smart Data Access

Do not install

SAP HANA XS Advanced Runtime

Do not install

18
Installation guide S4 Customer System

Log File Locations

Log directory: /var/tmp/hdb_S00_hdblcm_install_2021-05-10_11.25.34

Trace location: /var/tmp/hdblcm_2021-05-10_11.25.34_39728.trc

Note: Volume encryption will be enabled. You need to back up root keys after the installation.

Do you want to continue? (y/n):y

2.2 Install Hana DB on DBNode 1 ibmriss01db01

19
Installation guide S4 Customer System

SAPNote, Version | Parameter | Expected | Override | Actual |


Compliant

--------------------+------------------------------------+---------------------------+-----------+------------------------
+-----------

1771258, 5 | LIMIT_@dba_hard_nofile | @dba hard nofile 65536 | | @dba hard


nofile NA | no

1771258, 5 | LIMIT_@dba_soft_nofile | @dba soft nofile 65536 | | @dba soft


nofile NA | no

1771258, 5 | LIMIT_@sapsys_hard_nofile | @sapsys hard nofile 65536 | | @sapsys


hard nofile NA | no

1771258, 5 | LIMIT_@sapsys_soft_nofile | @sapsys soft nofile 65536 | | @sapsys


soft nofile NA | no

1771258, 5 | LIMIT_@sdba_hard_nofile | @sdba hard nofile 65536 | | @sdba


hard nofile NA | no

20
Installation guide S4 Customer System

1771258, 5 | LIMIT_@sdba_soft_nofile | @sdba soft nofile 65536 | | @sdba soft


nofile NA | no

1980196, 7 | vm.max_map_count | 2147483647 | | 65530 |


no

2382421, 36 | [Link] | 4096 | | 128 | no

2382421, 36 | net.ipv4.tcp_max_syn_backlog | 8192 | | 2048 |


no

2382421, 36 | net.ipv4.tcp_slow_start_after_idle | 0 | |1 | no

2382421, 36 | net.ipv4.tcp_syn_retries |8 | |6 | no

2382421, 36 | net.ipv4.tcp_timestamps |1 | |1 | yes

2382421, 36 | net.ipv4.tcp_window_scaling |1 | |1 | yes

2534844, 12 | [Link] | 32768 | | 4096 | no

2578899, 20 | IO_SCHEDULER_vda | none | | mq-deadline |


no

2578899, 20 | IO_SCHEDULER_vdb | none | | mq-deadline |


no

2578899, 20 | IO_SCHEDULER_vdc | none | | mq-deadline |


no

2578899, 20 | IO_SCHEDULER_vdd | none | | mq-deadline |


no

2578899, 20 | IO_SCHEDULER_vde | none | | mq-deadline |


no

2578899, 20 | rpm:tcsh | 6.20.00-4.9.1 | | 6.20.00-4.15.1 | yes


[3]

2578899, 20 | [Link] | start | | stop | no

2578899, 20 | [Link] | start | | start | yes

2578899, 20 | vm.dirty_background_bytes | 314572800 | |0 |


no

2578899, 20 | vm.dirty_bytes | 629145600 | |0 | no

2684254, 5 | KSM |0 | |0 | yes

2684254, 5 | THP | never | | always | no

2684254, 5 | energy_perf_bias | all:0 | | all:none | - [1]

2684254, 5 | force_latency | 70 | | all:none | - [1]

2684254, 5 | governor | all:performance | | all:none | - [1]

21
Installation guide S4 Customer System

2684254, 5 | grub:intel_idle.max_cstate |1 | | NA | no [2]


[3] [6]

2684254, 5 | grub:numa_balancing | disable | | NA | no [2]


[3] [6]

2684254, 5 | grub:processor.max_cstate |1 | | NA | no [2]


[3] [6]

2684254, 5 | grub:transparent_hugepage | never | | NA | no


[2] [3] [6]

2684254, 5 | kernel.numa_balancing |0 | |1 | no

941735, 11 | ShmFileSystemSizeMB | 413104 | | 193483 | no

941735, 11 | VSZ_TMPFS_PERCENT | 75 | | 35 | no

941735, 11 | [Link] | 1152921504606846720 | |


1152921504606846720 | yes

941735, 11 | [Link] | 18446744073709551615 | |


18446744073709551615 | yes

[1] setting is not supported by the system

[2] setting is not available on the system

[3] value is only checked, but NOT set

[6] grub settings are mostly covered by other settings. See man page saptune-note(5) for details

22
Installation guide S4 Customer System

23
Installation guide S4 Customer System

24
Installation guide S4 Customer System

25
Installation guide S4 Customer System

26
Installation guide S4 Customer System

2.3 Upgrade HANA DB to Rev 55

27
Installation guide S4 Customer System

3. Install ASCS

28
Installation guide S4 Customer System

29
Installation guide S4 Customer System

30
Installation guide S4 Customer System

31
Installation guide S4 Customer System

32
Installation guide S4 Customer System

33
Installation guide S4 Customer System

34
Installation guide S4 Customer System

4. Install ERS

35
Installation guide S4 Customer System

36
Installation guide S4 Customer System

37
Installation guide S4 Customer System

5. Install HANA DB instance

38
Installation guide S4 Customer System

Run DB installation from CS node

39
Installation guide S4 Customer System

Risewithsap00

40
Installation guide S4 Customer System

41
Installation guide S4 Customer System

42
Installation guide S4 Customer System

43
Installation guide S4 Customer System

44
Installation guide S4 Customer System

45
Installation guide S4 Customer System

46
Installation guide S4 Customer System

6. Install PAS

47
Installation guide S4 Customer System

48
Installation guide S4 Customer System

49
Installation guide S4 Customer System

50
Installation guide S4 Customer System

51
Installation guide S4 Customer System

52
Installation guide S4 Customer System

53
Installation guide S4 Customer System

54
Installation guide S4 Customer System

55
Installation guide S4 Customer System

7. Install Application Server

56
Installation guide S4 Customer System

Additional application server instance

57
Installation guide S4 Customer System

58
Installation guide S4 Customer System

59
Installation guide S4 Customer System

60
Installation guide S4 Customer System

61
Installation guide S4 Customer System

8. Post Installation Activities

Execute SGEN

Client Copy – 100

Disbale log_mode for HANA DB

62
Installation guide S4 Customer System

System DB

Tenant DB

Create client 100 in SCC4 and a logical System name for same in Bd54

63
Installation guide S4 Customer System

Login to source client 000 and start the transaction SCCLN

64
Installation guide S4 Customer System

As per the new client copy too we need to create foll three RFC Destinations:

MDGTR@S01CLNT000 and use DDIC user and pwd. Add the entry in /mdg_tr_dest transaction

FINBTR@S01CLNT000 and use DDIC user and pwd. Add the entry in /finb_tr_dest

S01CLNT100

65
Installation guide S4 Customer System

66
Installation guide S4 Customer System

/nMDG_TR_DEST

/nfinb_tr_dest

67
Installation guide S4 Customer System

Add logical client name for 000 also

Create foll rfc also and then start client copy again:

68
Installation guide S4 Customer System

69
Installation guide S4 Customer System

Enable log_mode again for System DB and Tenant DB

------------------------------------------------End of Document--------------------------------------------------------------

70

Common questions

Powered by AI

Setting 'transparent hugepage' to 'never' is crucial for ensuring SAP HANA's memory efficiency, as it prevents the kernel from automatically using huge pages, which can save memory when large contiguous memory blocks are required. The default setting 'always' can lead to increased memory fragmentation and performance degradation, impacting SAP HANA's real-time processing capabilities. Non-compliance poses risks such as unstable memory allocation and potential performance bottlenecks, highlighting the importance of manual configuration for optimal performance .

'IO_SCHEDULER' settings determine how input and output operations are managed on disk devices. In SAP HANA, these are critical for optimizing database performance and ensuring efficient disk usage. Non-compliance often occurs when the actual scheduler used, such as 'mq-deadline', does not match the recommended setting, which might be 'none'. This discrepancy can result from system upgrades or configuration mismatches, and rectifying it may involve aligning the scheduler settings with SAP's performance tuning guidelines .

The 'net.ipv4.tcp_tw_recycle' parameter reduces the time a connection spends in the TIME_WAIT state by allowing quicker reuse of TCP connections. However, this setting requires that TCP timestamps are enabled, i.e., net.ipv4.tcp_timestamps = 1, which might not be applied if the HANA node needs to communicate with hosts behind a NAT firewall. Additionally, if not all hosts that communicate with HANA have TCP timestamps enabled, enabling this setting may cause TCP connection issues. Therefore, it might not be advisable in configurations involving NAT firewalls or heterogeneous environments with varying TCP timestamp settings .

The setting 'limit_@dba_hard_nofile' is not compliant because the current value does not meet the expected standard. According to SAP Note 1771258, the expected value is '@dba hard nofile 65536'. However, the actual setting is '@dba hard nofile NA', indicating non-compliance with SAP's predefined limits for file descriptor counts, essential to handle the database operations efficiently under high load conditions .

Using 'uuidd.socket' as part of the SAP HANA installation ensures unique identifiers are generated, which is crucial for system processes to prevent conflicts or duplication of resources. Its compliance status indicates correct activation and functionality within the installation, contributing to the system's operational integrity and data consistency across distributed environments .

The 'net.ipv4.tcp_tw_reuse' parameter can be effective when TCP timestamps (net.ipv4.tcp_timestamps) are enabled. It allows HANA to reuse client ports immediately after closing, thus reducing waiting times in TIME_WAIT states and improving resource efficiency, especially in high-volume environments. However, it must not be enabled if the environment includes NAT firewalls or hosts without TCP timestamps, as this may lead to connection reliability issues .

The parameters 'net.ipv4.tcp_max_syn_backlog' and 'net.core.somaxconn' govern how incoming TCP connections are managed before a server accepts them. 'net.ipv4.tcp_max_syn_backlog' sets the maximum number of half-open connections. In SAP HANA, reducing its size can lead to dropped connections under high load. Similarly, 'net.core.somaxconn' configures the maximum number of queued connections when a socket is in a waiting state. Lower-than-recommended values, such as 128 in the typical configuration, could lead to connection losses during peak periods, suggesting a need for higher values to prevent backlog issues .

The 'net.ipv4.tcp_wmem' parameter specifies the minimum, default, and maximum size of the TCP send buffer, which is significant in system replication scenarios with higher than usual latency. Its maximum value should be at least equal to the bandwidth-delay product for the relevant connection. For instance, for a 10 GBit/s connection with 1 ms latency, the required maximum is 1.25 MB, which allows sufficient data flow within transmission windows without unnecessary delays .

Changing the SAP HANA installation path affects how the system is configured and operated as it determines where the data volumes, log volumes, and secure stores are located. An incorrect path could lead to configuration errors or startup issues, as the system expects to access specific directories for its operations. Careful planning is needed during installation to align system paths with the desired system architecture and storage policies .

'net.ipv4.ip_local_port_range' influences the number of client ports available for internal communication within SAP HANA. It should be configured to maximize the availability of client ports while reserving specific ports used by processes and applications. Typically, the SAP Host Agent sets this parameter to a range that ensures enough client ports are available, often between 9000 and 65499. Deviations from this configuration should be carefully managed to avoid conflicts with other applications .

You might also like