The table below lists and explains names and meanings of SAP HANA parameters. These values are tuned by editing the /etc/default/LifeKeeper configuration file.
| Parameter Name | Meaning | Setting Value | Default Value | When to Apply | Notes |
|---|---|---|---|---|---|
| HANA_HANDSHAKE_TAKEOVER_FAILBACK | Whether to perform an automatic failback of the SAP HANA resource in the case of a failed Takeover with Handshake attempt. When set to ‘true’, LifeKeeper will automatically bring the SAP HANA resource back in-service on the previous host in the case of a failed Takeover with Handshake attempt. When set to ‘false’ (default), the SAP HANA resource remains in the Out-of-Service Failed (OSF) state after a failed Takeover with Handshake attempt and requires manual intervention to bring in-service. | True or False | False | As required (takes effect immediately) | |
| HANA_HSR_POLL_INTERVAL | Specifies how often (in seconds) LifeKeeper will poll the status of SAP HANA System Replication. | Positive integers | 10 | As required (takes effect immediately) | |
| HANA_QUICKCHECK_TIMEOUT | Specifies the timeout value (in seconds) for the SAP HANA quickCheck script. | Positive integers, Minimum value 30 | LKCHECKINTERVAL – 10 | As required (takes effect immediately) | If set to less than 30, it will automatically default to 30. |
| HANA_REGISTER_SECONDARY_DURING_RESTORE | Whether the SAP HANA Recovery Kit should register and restart the secondary database before completing the in-service operation for the primary database instance. When set to ‘true’, the SAP HANA resource is not marked in-service until the recovery kit has attempted to register and restart the secondary database. When set to ‘false’ (default), the SAP HANA resource is marked in-service as soon as the primary database instance is running, and a local recovery event is initiated immediately afterward to register and restart the secondary database. | True or False | False | As required (takes effect immediately) | |
| HANA_RECOVER_TIMEOUT | Specifies the timeout value (in seconds) for the SAP HANA recover script. | Positive integers | 1800 | As required (takes effect immediately) | |
| HANA_START_WAIT | Specifies the amount of time (in seconds) to wait when starting the SAP HANA database instance. | Positive integers | 2700 | As required (takes effect immediately) | |
| HANA_STOP_WAIT | Specifies the amount of time (in seconds) to wait when stopping the SAP HANA database instance. | Positive integers | 600 | As required (takes effect immediately) | |
| HANA_START_COUNT | Specifies the number of attempts to issue the sapcontrol Start command when starting the SAP HANA database instance. | Positive integers | 3 | As required (takes effect immediately) | |
| HANA_STOP_COUNT | Specifies the number of attempts to issue the sapcontrol StopWait command when stopping the SAP HANA database instance. | Positive integers | 3 | As required (takes effect immediately) | |
| HANA_STOP_FINAL_WAIT | After HANA_STOP_COUNT failed attempts to stop the SAP HANA database, this specifies the amount of additional time (in seconds) to wait to allow the database to fully stop. | Positive integers | 60 | As required (takes effect immediately) | |
| HANA_RECOVER_AUTORES_ISP | When LifeKeeper starts it will automatically in-service all hierarchies that have resources with AUTORES_ISP set. HANA can not automatically in-service a resource on startup if there are other systems down. This flag when set to TRUE will cause the hierarchy to in-service on the AUTORES_ISP system when the last system in the cluster starts. For example, in a 2 node cluster, when node1 starts the HANA resource will not in-service automatically even though AUTORES_ISP is set if node2 is down. When node2 starts, it will trigger the automatic restore on node1. | True or False | True | As required (takes effect immediately) | |
| HANA_STARTUP_TIMEOUT | This is the maximum time (in seconds) a restore will wait for LifeKeeper startup on a system to complete. | Positive Integers | 900 | As required (takes effect immediately) |
Post your comment on this topic.