If your result set is quite large and
you already retrieved most of the result set, the pause will be slightly longer since the first part of
the result set must be re-queried and discarded.
RAC Node Failure Scenario
One of the benefits of a RAC environment is your ability to add or remove nodes to meet changing
resource demands. One server that is underutilized in one business unit may be needed in another
business unit that is entering its peak processing period. Adding or removing a node in a RAC
environment may also be driven by a failure of a node; while the remaining nodes in the cluster
service ongoing requests, you will have to repair or replace the missing node and add it back to
the cluster without bringing down the rest of the cluster.
In this section, we??™ll show you the steps required to remove a node??™s metadata from the
cluster registry and then rebuild a node and add it back to the cluster. The assumption in this
scenario is that the local hard disk of the third cluster node is damaged beyond repair; therefore,
you will rebuild the node from scratch and add it to the cluster registry. After this step, you will
reinstall the Oracle software and create the instance as part of the database cluster.
Remove the Instance
Even if the instance on the failed server is not available, you still want to remove any traces of the
instance from the remaining nodes in the cluster. You can use the srvctl command to remove
the instance from the cluster, as in this example:
[oracle@oc1 ~]$ srvctl remove instance -d rac -i rac3
Remove instance rac3 for the database rac? (y/[n]) y
[oracle@oc1 ~]$
The parameter -d rac specifies the database to be modified, and -i rac3 specifies the instance
to be removed from the RAC.
Pages:
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605