The LifeKeeper Oracle Recovery Kit installation creates 3 registry entry variables stored in the following registry key:
MAXWAIT is a decimal integer that specifies the number of seconds that the recovery kit will wait for a single Oracle service to start or stop. If the service has not started within the specified time frame, LifeKeeper will mark the resource as failed. The default value for MAXWAIT is 300; however, it is possible that for extremely large databases, 300 seconds might not be enough time for the database services to reach the STARTED or STOPPED state. If this is the case, change this registry entry to a reasonable value.
RESTORE_DEEPCHK_MAX_RETRY is a decimal integer that allows multiple attempts to verify the Oracle service state during a restore or local recovery operation. On a server that is unexpectedly heavily loaded, the default service state check time may not always be sufficient to verify that protected Oracle services are in the RUNNING state. The default value for this variable is 0 and normally only 1 Oracle service state check attempt is performed for each service. This value can be changed if extra attempts may be needed to verify the Oracle service state.
RESTORE_DEEPCHK_SLEEP is a decimal integer, measured in seconds, to insert sleep intervals between each extra attempt to verify the Oracle service state during a restore or local recovery operation. This option is enabled if the RESTORE_DEEPCHK_MAX_RETRY option described above is used. The default value for this variable is 0 and normally no sleep times are inserted between extra Oracle service state check attempts. If the RESTORE_DEEPCHK_MAX_RETRY variable is set, it is highly recommended that the RESTORE_DEEPCHK_SLEEP variable be set as well to improve the reliability and performance of Oracle service state checks.
Post your comment on this topic.