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 SID 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.
Restriction: If you are configuring multiple ORACLE instances, then you must configure each listener to listen on a unique virtual IP address.
LifeKeeper will not allow you to configure multiple listeners to listen on the same virtual IP address with different ports.