Database Reference
In-Depth Information
Conclusion
Capacity planning is a very important step in a project life cycle to plan infrastructure and components required to
support the applications. We touched on normal issues faced in environments and how planning and conducting
proof of concepts to determine the throughput that can be obtained from each server and the n -nodes we add to the
configuration.
In this chapter, we explored the architecture of RAC as well as the new Oracle Clusterware architecture. Then
we looked at the clustered database by answering a few questions on cache fusion technology: how cache fusion
operates, how blocks are shared across the instances, and how they are managed in a way that only one instance
makes changes to the block at any moment. We also discussed the provision to cache memory between the various
instances by the GCS, how resources are mastered on an instance with a new concept of a the GRD, and how the GCS
and GES communicate with the GRD. We also investigated the additional background and foreground processes
available only in a RAC implementation.
We looked at the transaction management principles of cache fusion. We also looked at the various scenarios or
behavioral patterns that are encountered in a normal day-to-day operation in an enterprise with extensive details,
including process flows and a systematic description of each behavior.
In a RAC configuration, most of the activities are done within the SGA or across the cluster interconnect, and
a copy is maintained within an instance. We discussed when one instance required a block that is held by another
instance and how the holding instance would transfer the block to the requesting instance after making updates to the
required GRD on the resource master node.
 
Search WWH ::




Custom Search