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.
| MAXDB_START_TIMEOUT | Number of seconds to wait before aborting an in-service action that is hung. | Integers | 300 | As required (takes effect 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 | As required (takes effect immediately) | |
| MAXDB_STOP_COUNT | Number of times LifeKeeper will attempt to offline the database. | Integers | 5 | As required (takes effect immediately) | |
| MAXDB_WAIT | Number of seconds to wait between database offline attempts. | Integers | 5 | As required (takes effect immediately) | |
| MAXDB_DEBUG | Enables or disables debug logging. | 0: disabled 1: enabled |
0 | As required (takes effect 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. |
Post your comment on this topic.