Behavior on SAP HANA Studio Startup
2.3 Configuring SAP HANA System Properties .1 Changing System Properties.1 Changing System Properties
The properties of an SAP HANA system are defined in the parameters of its configuration files. Configuration files are separated into sections; sections bundle parameters of the same category.
Prerequisites
You have the system privilege INIFILE ADMIN.
Procedure
1. In the Administration editor, choose the Configuration tab.
A list of all configuration files appears.
2. Expand the configuration file that you want to change.
All the sections of the configuration file are listed.
3. Expand the required section.
All the parameters of the section are listed. For each parameter, you can see the default value.
4. In the context menu of the configuration parameter that you want to change, choose Change...
The Change Configuration Value dialog box appears.
5. Enter the new value.
If host-specific values are possible, you can expand the Hosts area of the Change Configuration Value dialog box, select the relevant host(s), and enter the host-specific value(s).
It is possible to enter both a value for the system as a whole and for individual hosts. In this case, the system-specific value only applies to those hosts that do not have a host-system-specific value.
If it is not possible to enter a different value for each host, the disabled icon ( ) is displayed in the Host column of the list view, and there is no Hosts area in the Change Configuration Value dialog box.
Results
After you have entered a new value for a parameter at system level, it is displayed in the System column with a green circle ( ). After you have entered a new value for a parameter at host level, a gray rhombus ( ) appears in the Host column. To show information on a specific host, select the host from the Host filter.
2.3.2 Resetting System Properties
You can restore changed parameters in the configuration files of an SAP HANA system back to their default values.
Prerequisites
You have the system privilege INIFILE ADMIN.
Procedure
1. In the Administration editor, choose the Configuration tab.
A list of all configuration files appears.
2. Expand the configuration file that you want to change.
All the sections of the configuration file are listed.
3. Expand the required section.
All the parameters in the section are listed. You can identify parameters that have user-defined values at system level and/or host level with a green circle ( ) and gray rhombus ( ) respectively.
4. To delete a user-defined value and restore the default value, you can choose one of the following methods:
Procedure Result
Delete with automatic reset:
1. In the context menu of the configuration parameter, choose Delete.
The Delete Configuration Value dialog box appears.
2. Choose the layer whose user-defined values you want to delete.
3. Choose Delete.
The user-defined value(s) are cleared and the default value(s) are re-applied.
Note
If you added a new parameter to a section, then choosing Delete from the context menu deletes the entire parameter.
Manually restore default:
1. In the context menu of the configuration parameter, choose Change...
The Change Configuration Value dialog box appears.
2. For the required layers, choose Restore Default, or if you want to reset all visible layers, choose Restore Default for All.
3. Choose Save.
The user-defined value(s) are cleared and the default value(s) are re-applied.
2.3.3 Setting the global_allocation_limit Parameter
The SAP HANA database preallocates a pool of memory from the operating system over time, up to a predefined global allocation limit. You can change the default global allocation limit in the global.ini configuration file.
Prerequisites
You have the system privilege INIFILE ADMIN.
Context
The global_allocation_limit parameter is used to limit the amount of memory that can be used by the database.
The value is the maximum allocation limit in MB. A missing entry or a value of 0 results in the system using the default settings. The global allocation limit is calculated by default as follows: 90% of the first 64 GB of available physical memory on the host plus 97% of each further GB. Or, in the case of small physical memory, physical memory minus 1 GB.
Procedure
1. In the Administration editor, choose the Configuration tab.
The configuration files that contain the configuration information for the system are displayed.
2. Expand the global.ini configuration file and then the memorymanager section.
3. In the context menu for the global_allocation_limitparameter, choose Change...
The Change Configuration Value dialog box appears.
4. Enter a value for the entire system and/or individual hosts.
If you enter only a value for the system, it is used for all hosts. For example, if you have 5 hosts and set the limit to 5 GB, the database can use up to 5 GB on each host (25 GB in total). If you enter a value for a specific host, then for that host, the specific value is used and the system value is only used for all other hosts. This is relevant only for distributed systems.
Related Information
Allocated Memory Pools and Allocation Limits [page 93]
The SAP HANA database, across its different processes, reserves a pool of memory before actual use. This pool of allocated memory is preallocated from the operating system over time, up to a predefined global allocation limit, and is then efficiently used as needed by the SAP HANA database code.
2.3.4 Configuring Trace File Rotation
Trace file rotation prevents trace files from growing indefinitely by limiting the size and number of trace files. You can configure trace file rotation globally for all services in the system and for individual services.
Prerequisites
You have the system privilege INIFILE ADMIN.
Procedure
1. In the Administration editor, choose the Configuration tab.
2. Depending on whether you are configuring trace file rotation for all system services or for an individual service, proceed as follows:
Option Description
All services 1. Navigate to the global.ini file and expand the section trace.
2. Configure the maxfiles parameter by specifying the maximum number of trace files that may exist.
3. Configure the maxfilesize parameter by specifying in bytes the maximum size an individual trace file may reach.
Note
The default configuration for trace file rotation in the global.ini file is maxfiles=10 and maxfilesize=10000000.
Individual
service 1. Navigate to the configuration file of the relevant service (for example, indexserver.ini) and expand the section trace.
If there is no trace section, create one by right-clicking the file and choosing Add Section.
2. Configure the maxfiles parameter by specifying the maximum number of trace files that may exist.
3. Configure the maxfilesize parameter specifying the maximum size an individual trace file may reach in bytes.
Note
If the two parameters do not exist in the trace section or if you created a new trace section, create the parameters by right-clicking the section and choosing Add Parameter.
Results
When a trace file reaches the specified maximum file size, it is closed, and a new file created. When the specified maximum number of files is reached, the next time a new file is created, the first file is deleted, and so on.
Note
The system checks the size and number of diagnosis files regularly. The threshold values for these checks (check 50 and 51) should be in line with the configured trace file rotation.
Related Information
Configuring Traces [page 171]
Various traces are available for obtaining detailed information about the actions of the database system. You can activate and configure traces on the Trace Configuration tab of the Administration editor.
Configuring Check Thresholds [page 70]
For some checks performed by the system, you can configure when an alert is issued, that is the alert condition. A check can have a low, medium, and high priority threshold.
2.3.5 Reserving Connections for Administrators
If the maximum number of connections has been reached in an SAP HANA system, it is not possible for anyone to log on, not even an administrator. For this reason, you can reserve a certain number of connections for
administrative access only.
Prerequisites
You have the system privilege INFILE ADMIN and SESSION ADMIN.
Procedure
1. In the Administration editor, choose the Configuration tab.
2. Navigate to the indexserver.ini file and expand the session section.
3. Configure the reserved_connections parameter by specifying the number of connections you want to reserve.
The default number of reserved connections is 10. The minimum number is 1.
4. Restart the system.
Results
When the maximum number of connections minus the number reserved connections is reached, only an administrator with the system privilege SESSION ADMIN can log on to the system, for example, to resolve blocking situations by canceling sessions.
2.3.6 Changing the Default SLD Data Supplier Configuration
The System Landscape Directory (SLD) is the central directory of system landscape information relevant for the management of your software lifecycle. Data suppliers collect and send system data to SLD on a regular basis.
The SLD data supplier for SAP HANA systems is implemented within the name server of the SAP HANA system.
Prerequisites
● The SLD is configured.
For more information, see SAP Note 1018839 and the section Configuring an SAP HANA System to Connect to the System Landscape Directory in the SAP HANA Update and Configuration Guide.
● You have the system privilege INIFILE ADMIN.
Context
For SAP HANA systems, the name server contains the SLD data supplier. It is configured by default to
automatically transfer data to the SLD in XML format using the sldreg executable on a regular basis. However, if it is necessary to change the default settings, you can do so in the SAP HANA studio by modifying the
nameserver.ini file. For example, it may not be necessary to send data to the SLD frequently if your landscape is stable, or you may need to change the default save locations of the configuration and log files.
Procedure
1. In the Administration editor, choose the Configuration tab.
2. Right-click the nameserver.ini file and choose Add Section.
3. Create a new section sld.
4. Add those parameters whose default value you want to change.
The following table lists the possible parameters and their default values.
Note
Under normal circumstances, you will not need to change the default values. It should only be necessary, for example, for testing purposes or if requested as part of a support inquiry.
Key Meaning Default Value Note enable Activates or deactivates the SLD
data supplier
true Allowed values are true, false
Interval Specifies the frequency (in seconds) with which the
sldreg.xml file is generated. If a newly-generated document is the same as the previous one, it is not sent to the SLD.
300 It does not make sense to enter small positive values or negative values.
If you enter 0 or a negative value, data is transferred to the SLD only once.
Enter a value without a “1000 separator” (for example, 1899, not 1,899 or 1.899), otherwise it will be interpreted as 0.
force_interval Specifies how often (in seconds) the sldreg.xml file must be sent to the SLD, even if the file has not changed.
43200
configpath Specifies the location of the folder that contains the configuration file slddest.cfg
This file is a parameter for the call to sldreg.
xmlpath Specifies where the file sldreg.xml is generated and where the sldreg.log log file is written
sldreg.log is the log file of sldreg, and both files are parameters for the call to sldreg.
/usr/sap/
If errors occur in the transfer of data to the SLD, you can check the log file smlreg.log and the database trace for the name server with trace components SLDCollect, SLDConfig, and SLDSend.
Related Information
Configuring, Working with and Administering System Landscape Directory Landscape Management Database (LMDB)
Database Trace [page 172]
The database trace records information about activity in the components of the SAP HANA database. You can use this information to analyze performance and to diagnose and debug errors.