OUI makes its best
guess based on the existing cluster configuration, as you can see here.
6. In step 6, you will see the existing cluster services; update the services with the new node
name as appropriate.
7. On the last step, step 7, specify the tablespaces, datafiles, and redo log groups that
will be added for this instance; in this case, an undo tablespace, the datafile for the
tablespace, and two redo log groups, shown here.
Chapter 10: Real Application Clusters 389
8. A confirmation screen appears when the instance is up and running; the cluster once
again has three nodes:
SQL> select inst_id from gv$instance;
INST_ID
-------
1
2
3
Tuning a RAC Node
The first step in tuning a RAC is to tune the instance first. If an individual instance is not tuned
correctly, the performance of the entire RAC will not be optimal. You can use the Automatic
Workload Repository (AWR) to tune an instance as if it was not part of a cluster.
Using EM Database Control, you can further leverage the statistics from the AWR to produce
reports on a RAC-wide basis. In Figure 10-20, you can see how EM Database Control makes it
easy to analyze the performance of the shared global cache as well as the cache performance on
an instance-by-instance basis.
FIGURE 10-20 EM Database Control RAC cache statistics
390 Oracle Database 11g DBA Handbook
Tablespace Management
In a RAC environment, tablespace management is much the same as in a single-instance
environment.
Pages:
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609