|A resource will not come in service on a secondary node if it is running LifeKeeper for Linux older than v9.7.0
ISSUE: When a secondary node is updated to v9.7.0 and a failover or switchover occurs making it the primary node in the cluster, it will update the configurations of all the other nodes. If another node is running a version of LifeKeeper for Linux previous to v9.7.0, it will fail to come in-service due to the new configuration format not being supported in previous versions.
WORKAROUND/SOLUTION: Upgrade the secondary node to v9.7.0 to allow for normal failover/switchover operations. To bring the resource in-service on an older release, restore the configuration from a backup, see lkbackup for more information.
|Local recovery may fail if the local database is stopped with a sapcontrol Stop/StopWait command, resulting in a failover of the SAP HANA resource hierarchy
ISSUE: When a user issues a Stop/StopWait request for the HDB instance using the sapcontrol utility (which is also what is used internally when a user issues an ‘HDB stop’ command), sapstartsrv begins an asynchronous process of gracefully stopping all of the HANA database processes, and does not stop this process until either the database is completely shut down or the process times out. Therefore any other action issued via sapcontrol while sapstartsrv is in the process of gracefully shutting down the database will compete with the already-in-progress stop action, and will ultimately fail and time out.
In particular, the following sequence of events may lead to a failover of the SAP HANA resource hierarchy, even when local recovery is enabled for the protected database:
Thanks for your feedback.