| The Oracle Recovery Kit does not include support for Connection Manager and Oracle Names features
The LifeKeeper Oracle Recovery Kit does not include support for the following Oracle Net features of Oracle: Oracle Connection Manager, a routing process that manages a large number of connections that need to access the same service; and Oracle Names, the Oracle-specific name service that maintains a central store of service addresses.
The LifeKeeper Oracle Recovery Kit does protect the Oracle Net Listener process that listens for incoming client connection requests and manages traffic to the server. Refer to the LifeKeeper for Linux Oracle Recovery Kit Administration Guide for LifeKeeper configuration specific information regarding the Oracle Listener.
| The Oracle Recovery Kit does not support the ASM or grid component features
The Oracle Automatic Storage Manager (ASM) feature provided in Oracle is not currently supported with LifeKeeper. In addition, the grid components are not protected by the LifeKeeper Oracle Recovery Kit. Support for raw devices, file systems, and logical volumes are included in the current LifeKeeper for Linux Oracle Recovery Kit. The support for the grid components can be added to LifeKeeper protection using the gen/app recovery kit.
| The Oracle Recovery Kit does not support NFS Version 4
The Oracle Recovery Kit supports NFS Version 3 for shared database storage. NFS Version 4 is not supported at this time due to NFSv4 file locking mechanisms.
| Oracle listener stays in service on primary server after failover
Network failures may result in the listener process remaining active on the primary server after an application failover to the backup server. Though connections to the correct database are unaffected, you may still want to kill that listener process.
| DataKeeper: Nested file system create will fail with DataKeeper
When creating a DataKeeper mirror for replicating an existing file system, if a file system is nested within this structure, you must unmount it first before creating the File System resource.
Proper Procedure: Create the /oracle/BPP file system before creating the sub-file systems under it, such as /oracle/BPP/mirrorlogA. (i.e. the /oracle/BPP file system should appear at the bottom of the GUI list)
Workaround: Manually unmount the nested file systems and remount / create each nested mount.
Thanks for your feedback.