Compaq ProLiant 6400R Compaq Parallel Database Cluster Model PDC/O1000 for Ora - Page 123

Cluster Management 6-3 4. Determine how critical it is to repair the problem. G If the problem is not considered to be critical, wait until a non-peak time to service the problem. G If the problem is critical but does not affect all cluster nodes, shut down the Oracle instances on the affected nodes and wait until a non-peak time to service the problem. G If the problem is critical and affects all the cluster nodes, shut down the database instances on all cluster nodes and correct the problem. Managing Network Clients Connected to a Cluster An important aspect of managing network clients is informing users that their applications are now running on a cluster. As the cluster is initially brought into production, it can be helpful to describe in a memorandum the effects a cluster will have on user ability to access the database. Since users will experience some disruption of service and possibly a performance degradation during a node eviction, they might become concerned about the availability and stability of their applications. When a node eviction or node integration occurs, the users will notice that for a brief moment they cannot access their database. When users have been properly forewarned of the effects of operating in a clustered environment, they will more readily recognize when such an event is occurring. Most users will then know to wait several seconds before attempting to reaccess their database. Cluster Events The majority of cluster events can be viewed either within the System log or within specific error log files. The Oracle8i Server events are sent to the Application log and can be viewed from the Event Viewer. The lower-level software components, such as the cluster manager, send events to error log files. NOTE: If the OSDs are not installed in the default directory, the log files will be in the same directory as the OSDs.