Database Reference
In-Depth Information
CPU needs are also easily met. The original ODA has two Intel Xeon X5675 6-core CPUs and the X3-2 has two
Intel Xeon E5-2690 CPUs installed on each server node, which respectively provides 24 and 36 CPU cores per ODA.
In many cases, e-Business Suite databases have up to 8 CPU cores per database node, but this depends heavily on
the number of users and workload patterns of the environment. Make sure to estimate the required number of CPUs
based on the characteristics of your environment and use the flexible licensing to enable only the required number of
cores for the database.
Memory is potentially an issue, depending upon which ODA machine you are running, which version of
e-Business Suite you use, and your virtualization choices. The original ODA came with 96G of RAM installed on each
server node; the X3-2 was upgraded to 256G of RAM on each server. This is a sufficient amount of memory for the
e-Business Suite database in most cases. However, if the virtualized deployment option is chosen, the amount of
memory has to be split between the ODA Base (database), the management domain (Dom0), and the other virtual
machines. With the original ODA, the amount of available memory may become a problem.
As you might expect, Oracle certifies its own software on its own hardware. Oracle Database Appliance is an
Oracle Linux 5.6+ server cluster running Oracle grid infrastructure and database versions 11.2.0.2+. Both the OS
and the database versions are certified for running the Oracle e-Business Suite R12.1 database; however, 11.2.0.3 is
mandatory 2 for the R12.2 database version. Two deployment options for the application tier are possible:
Virtualized ODA that uses the ODA's integrated Oracle VM and Oracle Linux 6 virtual servers
for application tier hosts. This configuration is fully certified for e-Business Suite.
Use of an external application tier. This approach is certified if built according to the
requirements listed on My Oracle Support Certification Service.
e-Business Suite System Architecture on ODA
From a system architecture point, the ODA is nothing else than a “box” containing two servers, which can be configured
for a database workload only, or for other types of workloads if a virtualized configuration is used. With the virtualization
configuration, the ODA can also host multiple application servers; for a typical e-Business Suite configuration, two are
needed to ensure better availability figures. Additional VMs can be added for more advanced configurations, that is, if
external-facing modules (iSupplier, iRecruitment, iStore) are configured. Given the size and characteristics of the ODA
platform, there are a number of possible system architectures that fully or partially utilize the ODA. Following are a few of
the questions one has to answer to come up with the e-Business Suite architecture involving the use of an ODA:
Which ODA configuration to use—bare metal or virtualized? If bare metal is used, the
application tier servers will not reside on ODA.
What's the configuration of the database—RAC, RAC One Node,
3 or single node? This decision
affects the license costs and the availability characteristics of the database. For the best
availability, RAC is recommended.
Is an external load balancer available for use? (An ODA does not provide load balancer
functionality). If it's not available, you may need to implement a software load balancing or
failover functionality for the application tier on the ODA. Another option is to not use the load
balancing at all. Is that a suitable configuration?
What is the planned size of the application tier file system? Should it be shared between
nodes? One of the options for the shared file system is to use the Oracle Automatic Storage
Management Cluster File System (ACFS) on ODA; another option is to use an external NFS
share, which introduces an external dependency.)
2 Check the Certification Service on My Oracle Support for up-to-date requirements.
3 RAC One Node is supported without explicit certification ( https://blogs.oracle.com/stevenChan/entry/rac_one_node_ebs ).
 
Search WWH ::




Custom Search