Clients must always refer to the database by using the logical host name and not the physical host name.
For example, in the tnsnames.ora file for SQL*Net V2, you must specify the logical host as the host on which the database instance is running. See "5.2.5 How to Set Up Sun Cluster HA for Oracle".
Oracle client-server connections will not survive a Sun Cluster HA for Oracle switchover. The client application must be prepared to handle disconnection and reconnection or recovery as appropriate. A transaction monitor might simplify the application. Further, Sun Cluster HA for Oracle node recovery time is application-dependent.
If your application uses functions from RDBMS dynamic link libraries, you must ensure that these libraries are available in the event of failover. To do so:
Install the link libraries on the client, or
If Sun Cluster HA for NFS service is to be provided by the cluster, copy the libraries to the logical host and set the environment variables to the directory path of the link libraries, then NFS share those directories to clients.