Abstract
RAC provides normal features such as recoverability, manageability, and maintainability found in a stand-alone (single instance) configuration of Oracle Relational Database Management System (RDBMS). Among the business requirements supported by Oracle RDBMS, availability and scalability are naturally derived from the architecture of the RAC configuration.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Oracle Clusterware is part of Oracle Grid Infrastructure starting with Oracle Database 11g Release 2.
- 2.
These values are controlled by underscore parameters _GC_POLICY_MINIMUM and _GC_POLICY_TIME.
- 3.
This is because the latency of retrieving data from an I/O subsystem is much higher compared to transferring data over the network. Basically, network latency is much lower compared to I/O latency.
- 4.
By enabling the gc_files_to_lock parameter, Oracle will disable the cache fusion functionality and instead would use the disks for the sharing of blocks. In other words, it would use the Oracle parallel server (OPS) behavior.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Murali Vallath
About this chapter
Cite this chapter
Vallath, M. (2014). Capacity Planning and Architecture. In: Expert Oracle RAC Performance Diagnostics and Tuning. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-6710-2_2
Download citation
DOI: https://doi.org/10.1007/978-1-4302-6710-2_2
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-6709-6
Online ISBN: 978-1-4302-6710-2
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books