The table below lists and explains names and meanings of the SAP MaxDB Recovery Kit parameters. These values are tuned by editing the /etc/default/LifeKeeper configuration file.
| Parameter Name | Meaning | Setting Value | Default Value | When parameter takes effect | Notes |
|---|---|---|---|---|---|
| MAXDB_START_TIMEOUT | Number of seconds to wait before aborting an in-service action that is hung. | Integers | 300 | Immediately | |
| MAXDB_PID_CLEANUP | Specifies whether child processes of a hung in-service action will be cleaned up (killed). | y: clean up n: no cleanup |
n | Immediately | |
| MAXDB_START_COUNT | Number of times LifeKeeper will attempt to online the database. | Integers | 3 | Immediately | |
| MAXDB_STOP_COUNT | Number of times LifeKeeper will attempt to offline the database. | Integers | 5 | Immediately | |
| MAXDB_WAIT | Number of seconds to wait between database offline attempts. | Integers | 5 | Immediately | |
| MAXDB_OFFLINE_ENABLED | Specifies whether the database will be taken offline when the LifeKeeper MaxDB resource is taken out of service. | 0: do not offline 1: do offline |
1 | Use with caution, if you need to temporarily stop LifeKeeper (e.g., to upgrade or perform maintenance) while not stopping the database. | Please ensure you re-enable database offlines after maintenance is complete. |
| MAXDB_EXPERT_MODE | Specifies whether dependencies are created for the MaxDB resource instance. | 0: create dependencies for MaxDB during instance creation 1: no dependencies created for MaxDB resource instance |
0 | Immediately | |
| MAXDB_RUN_REQUIRED | Specifies whether the MaxDB run directory is required to be on an LK protected filesystem | 0: optional 1: required |
1 | Immediately | |
| XSERVER_START_COUNT | Number of times LifeKeeper will attempt to start the x_server. | Integers | 3 | Immediately | |
| XSERVER_STOP_COUNT | Number of times LifeKeeper will attempt to stop the x_server. | Integers | 3 | Immediately |
Post your comment on this topic.