Oracle Fail Safe provides resource dynamic-link library (DLL) files for the Oracle Database and Oracle TNS Listener. The DLL files enable the Cluster Service to communicate and manage the Oracle Database and listener resources. Other Oracle resources that do not require specialized DLL files are managed as Generic Services.
The following topics are discussed in this appendix:
Oracle Services for MSCS includes the resource DLL files shown in Table C-1. These files enable MSCS to communicate with and manage the Oracle resource types.
Table C-1 Oracle Resource DLL Files
As with other cluster resources, you can apply all advanced properties of controlling the failover parameters to these Oracle resources. You can control:
How often MSCS should poll the Oracle resource health (Looks Alive, Is Alive polling intervals)
Whether a database resource should be restarted when it fails, and, if so, how many times MSCS should attempt to restart it before failing over to the other node
How long MSCS should wait before declaring failure of the resource (pending timeout) during the startup and shutdown of the resource
If the resource takes longer than the time you specified with the pending timeout parameter to come online or go offline and the resource DLL did not detect any problems in the online or offline process, then the resource DLL asks MSCS to give it more time to complete the process. Thus, you do not have to be concerned if a resource occasionally takes longer to come online or go offline.
Typically, the Oracle Fail Safe Verify Cluster
operation automatically verifies the Oracle Database and listener resource DLL files and their registration with the MSCS software. If the Verify Cluster
operation finds that the DLL files are not registered, it registers them with the MSCS software. Using the Verify Cluster
operation is the preferred method for registering DLL files.
However, if you find that the Oracle resource DLL files are not registered properly, then you can use the commands in Section C.2.1 and Section C.2.2 to manually register or unregister them.
To register the Oracle Database resource DLL files, use the following commands:
fssvr /register "Oracle Database" FsResOdbs.dll fssvr /register "Oracle TNS Listener" FsResOdbs.dll
To unregister the Oracle Database resource DLL files, use the following commands:
fssvr /unregister "Oracle Database" fssvr /unregister "Oracle TNS Listener"
To register the Oracle Database resource administrator extension DLL files on the cluster nodes, use the following commands:
fsregadm /r FsResOdbsEx.dll fsregadm /r FsResTnsLsnrEx.dll
To unregister the Oracle Database resource administrator extension DLL files on the cluster nodes, use the following commands:
fsregadm /u FsResOdbsEx.dll fsregadm /u FsResTnsLsnrEx.dll
If MSCS Cluster Administrator is installed on a node that is not a member of a cluster, you need to register the Oracle Database resource administrator extension DLL with the cluster so that you can view Oracle Database resource parameters from the MSCS Cluster Administrator. To register, use the fsregadm
command. You must issue the command from the bin directory where Oracle Fail Safe Manager is installed (because Oracle Fail Safe Manager is not in the path environment variable).
For example:
fsregadm /r /c Cluster1 FsResOdbsEx.dll fsregadm /r /c Cluster1 FsResTnsLsnrEx.dll
You must specify the cluster name with the /c
option; otherwise the command will fail.