## 8.2.3  Monitoring and Replicating INI File Parameter Changes
INI file parameters should be the same on each site of a system replication landscape and are checked automatically.
The configuration parameter checker reports any differences between primary, secondary, and further secondary systems.
Some parameters may have different settings on the primary and the secondary system on purpose. One example is the global\_allocation\_limit parameter where the secondary is used for other systems. By adding those parameters to the exclusion list below, they are excluded from checking and replication.
Activate ini parameter replication so that changes made on the primary are automatically replicated to the secondary systems. Otherwise, changes should be manually duplicated on the other systems.
The checks of the configuration parameter checker:
- Are done every hour by default.
● Generate alerts. The alerts are visible in the SAP HANA cockpit, SAP HANA studio, and the M\_EVENTS system view. To view the alerts in the SAP HANA cockpit, look for the alerts tile on the system overview page of the SAP HANA cockpit and choose Show All . Y ou can see all alerts including the ones created because of parameter mismatch.
- Are optimized for the most recently changed parameters.
Enable and disable the parameter check on the primary site with [inifile\_checker]/enable = true | false . The parameter checker is on by default.
Enable and disable the parameter replication on the primary site with [inifile\_checker]/replicate = true | false . The parameter replication is off by default.
The ini file parameter replication follows these rules:
| Parameter set on   |                |                                           |
|--------------------|----------------|-------------------------------------------|
| yes                | no             | Copy parameter to the secondary system.   |
| no                 | yes            | Delete parameter on the secondary system. |
| set to value x     | set to value y | Copy value x to the secondary system.     |
The parameter changes on the secondary system are applied differently for each parameter:
- Online changeable parameters become active after the ALTER SYSTEM command or by editing the .ini file followed by the automatically triggered hdbnsutil -reconfig command.
- Offline changeable parameters become active after a restart. When changing such a parameter, it is necessary to restart the primary and secondary systems before a takeover. For more information about configuration parameters, see Configuration Parameter Reference .
To prevent parameters from generating alerts and eventually getting replicated, it is possible to create exclusions. In the following example, different global allocation limits (GAL) on primary and secondary systems can be set without being overwritten by the parameter replication.
##  Example
If for example you intend to use your secondary system for DEV/QA systems and set the global allocation limit to its minimal value (as described above), you may exclude this global\_allocation\_limit parameter from these checks as follows:
```
[inifile_checker] enable = true|false interval = 3600 exclusion_global.ini/SYSTEM = memorymanager/global_allocation_limit
```
The exclusion rules are written in the following syntax (comma separated list) and take effect immediately:
```
exclusion_[inifile name|*][/<LAYER>] = [section with wildcards|*][/parameter with wildcards|*], ... <LAYER> := SYSTEM\|HOST\|DATABASE\|\*
```
## Related Information
Configuring SAP HANA System Properties (INI Files) SAP HANA Configuration Parameter Reference