Specifications
NFS Server Recovery Kit
Description
The Oracle Recovery Kit does not support the ASM or grid component features of Oracle
10g
The following information applies to Oracle 10g database instances only. The Oracle Automatic
Storage Manager (ASM) feature provided in Oracle 10g is not currently supported with LifeKeeper.
In addition, the grid components of 10g 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.
NFS Server Recovery Kit
Description
Top level NFS resource hierarchy uses the switchback type of the hanfs resource
The switchback type, which dictates whether the NFS resource hierarchy will automatically switch
back to the primary server when it comes back into service after a failure, is defined by the hanfs
resource.
Some clients are unable to reacquire nfs file locks
When acting as NFS clients, some Linux kernels do not respond correctly to notifications from an
NFS server that an NFS lock has been dropped and needs to be reacquired. As a result, when
these systems are the clients of an NFS file share that is protected by LifeKeeper, the NFS locks
held by these clients are lost during a failover or switchover.
When using storage applications with locking and following recommendations for the NFS mount
options, SPS requires the additional nolock option be set, e.g.
rw,nolock,bg,hard,nointr,tcp,nfsvers=3,timeo=600,rsize=32768,wsize=327
68,actimeo=0.
NFS v4 changes not compatible with SLES 11 nfs subsystem operation
The mounting of a non-NFS v4 remote export on SLES 11 startsrpc.statd. The start up
ofrpc.statdon the out of service node in a cluster protecting an NFS v4 root export will fail.
Solution: Do not mix NFS v2/v3 with a cluster protecting an NFS v4 root export.
238Troubleshooting