Database Reference
In-Depth Information
Table 9-1.
Work That Doesn't Have to Be Done to Deploy an ODA
Task
Traditional
ODA
Spec equipment
Standards dependent.
Standardized hardware and software.
Cabling for external RAC network
On RAC systems.
Included in the hardware.
Provision SAN storage
In most cases.
Included in build.
IO virtualization
Standards dependent.
Included in build for virtualized systems.
Server partitioning
Standards dependent.
Not needed for databases, but can be done to
accommodate nondatabase virtual containers.
OS install
In most cases.
Included in build.
Grid Infrastructure install
In most cases.
Included in build.
Database software install
In most cases.
Included in build.
Project management to coordinate
team handoffs
Company dependent.
Included in build.
So what happened next? Today it isn't unusual to be approached by application teams or project managers
with the question, “Can we put this database on an ODA?”. You're in a good place when you are getting this type of
question.
The ODA install process eliminates unpredictable, time-wasting setup issues and handoffs that result in
additional coordination, dependencies, and delays. Deployment times are measured in days, not weeks or months.
The ODA provides a lot of flexibility in meeting project requirements challenges, which is something that a lot of
database and infrastructure departments have to deal with.
ODAs can be pre-deployed quickly to avoid the need to buy capacity before it is needed. They are the perfect
platform for the majority of your Oracle databases in support of Infrastructure as a Service (IaaS), Databases as a
Service (DBaaS), or cloud-based services in support of your company's IT strategy. When you get the question: “How
are you provisioning your databases so quickly and efficiently in your DBaaS offering?”—you are in an even better
place. ODAs won't meet every project requirement. There are limits to the number of IOPS, and the compute nodes
can't be scaled beyond two at this time. However, you may find that ODAs will meet the requirements for the majority
of your databases.
RAC Without Tears
Building RAC clusters that will be stable and meet high-availability requirements requires a great deal of up-front
planning and work, as well as pre- and post-install checks to validate the environments. Besides the RAC install
manuals, there are additional documents that have to be analyzed:
•
The RAC generic (MOS 810394.1) and any platform specific starter kits
•
The RAC FAQ (MOS 220970.1)
•
Oracle's support note (MOS 1344678.1) giving steps to stabilize a cluster, with platform-
specific extensions
•
The RAC Information Center note (MOS 1452965.2)
•
Your platform-specific RAC setup recommendations
•
RAC Known Issues support documents
