The LifeKeeper Oracle Recovery Kit provides the ability to concurrently run Oracle database instances on other servers, and to optionally place these instances under LifeKeeper protection. Such a configuration is known as Active/Active and allows LifeKeeper servers to be fully utilized under normal operating conditions.
The LifeKeeper Oracle Recovery Kit includes the ability to recover the database instance locally (local recovery) before trying to fail over the database instance to a standby server.
The LifeKeeper Oracle Recovery Kit protects the following Core/Standard Oracle services:
- Oracle Service
- Oracle TNS Listener
The LifeKeeper Oracle Recovery Kit protects the following Optional Services for each release:
|Optional 11g Services||Optional 12c Services||Optional 18c Services||Optional 19c Services|
|Oracle DB Console||-||-||-|
|Oracle Job Scheduler||Oracle Job Scheduler||Oracle Job Scheduler||Oracle Job Scheduler|
The typical Oracle resource hierarchy consists of the following resources:
- Shared communication resource (IP or LAN Manager alias name)
All Oracle data, log, and trace (core database) files for the protected Oracle Database are stored on shared or replicated volumes. Upon detecting a failure, LifeKeeper switches the core database files, along with its associated data volumes and communication resources, to a backup server. The recovery can be completely transparent to database users. Once LifeKeeper switches all dependent resources to the backup server, it starts the Oracle service on that server.
The LifeKeeper GUI display shown below depicts a typical resource hierarchy. The Oracle resource is the topmost resource in the hierarchy tree. It is responsible for starting and stopping the dependent resources (communication and volume resources) in the correct order.
This particular Oracle hierarchy uses only IP for its communication/Listener resource.
Post your comment on this topic.