Sunteți pe pagina 1din 5

Assumptions

Oracle Applications and Version


Operating System
Database Type
Database size
DR Offsite Hardware
Database redundancy requested
No of instances

Users Count

Data Archiving
Note:

Oracle E-Business Suite R12.2.x, OBIEE 11.1.8.1,


OID/OAM 11g, SOA 11g
64-bit Linux OEL 6.x
Oracle 11g 64-bit
500 GB
Proposed.
Proposed - RAC - Active/Active
Production
Development
Test
UAT
DR
Total 300 and 100 Concurrent Users (This include
assumed growth of users for next 2 years)

Considering the size of legacy data (700MB+2GB)


considering a data archiving solution would be
exaggerating. Archiving solution products are
designed for large volumes of data hence this
would not be the best time to propose a data
archiving solution. Existing database is capable of
containing all of customers legacy data. However,
if customer insists on a data archiving solution we
can provide solix as a roadmap.

1. The sizing is for 300 and 100 Concurrent Users for


all the modules. 5. Considering the size of legacy
data (700MB+2GB) considering a data archiving
solution would be exaggerating. Archiving solution
products are designed for large volumes of data
hence this would not be the best time to propose a
data archiving solution. Existing database is capable
of containing all of customers legacy data.
However, if customer
2. For Non Production, multiple instances can be
shared based on the load. Storage and configuration
will be changed based on the no. of instance in each
server that is going to share.
3. The storage configuration is based on the
assumptions and estimate of the total space
requirement. Therefore, the final proportions may
have to be adjusted to accommodate the sizes of
individual databases to contain all the data while
maintaining acceptable performance.
4. The hardware details need to be validated by the
hardware vendor based on the recommended
configuration for suitable model & make.

Component

No.of Servers

Operating System

CPUs
(Cores*3.0GHz)

Memory
(In GB)

SAN Storage - GB Remarks

Production E-Business Instance with High Availability Architecture with Active/Active Cluster

Oracle E-Business Suite R12.2.x

Application Node 1

Linux x86_64

24

Application Node 2

Linux x86_64

24

Database Node 1

Linux x86_64

32

Database Node 2

Linux x86_64

32

Application Node

Linux x86_64

16

150

Database Node

Linux x86_64

16

1 000

Application Node

Linux x86_64

16

300

Database Node

Linux x86_64

16

1200

Applications Tier

Linux x86_64

32GB

300

Database Server

Linux x86_64

32 GB

1000

300
1 000

Two Node Application Tier with the capability of load balancing and failover, this requires
HW Load balancer. Shared file system is proposed for application nodes
Database Cluster using the RAC solution with Active-Active Cluster with the capability of
Load balancing and failover.

Test (Demo, Training)


Non-Production instances for R12
Development / UAT
Non-Production instances for R12.2.x

Will share multiple non production instances.

DR

DR instances for R12.2.x

DR solution based on Oracle's Dataguard Solution with the capability of running


Applications and Database on respective servers in the event of production failover onto
DR Site. It is assumed that only key users will be on the system in case of disaster. This
sizing is arrived assuming expected load will be 50-60% in DR scenario without HA.
Performance may vary in case of DR scenario accordingly.
Disk replication is recommended for file level synchronization

Component

No.of Servers

Operating System

CPUs
(Cores*3.0GHz)

Memory
(In GB)

SAN Storage -GB Remarks

Production OBIEE
BI Server, Presentation Server

Application Node

Linux x86_64

24

150

Database Server

Database Node

Linux x86_64

24

500

BI Server, Presentation Server

Application Node1

Linux x86_64

16

150

Database Server

Database Node 1

Linux x86_64

16

500

BI Server, Presentation Server

Applications Tier

Linux x86_64

16

150

BI Server, Presentation Server

Database Server

Linux x86_64

16

500

Development

DR
DR solution based on Oracle's Dataguard Solution with the capability of running
Applications and Database on a single server in the event of production failover onto DR
Site. It is assumed that only key users will be on the system in case of disaster. This sizing
is arrived assuming expected load will be 60% in DR scenario without HA. Performance may
vary in case of DR scenario accordingly.
Disk replication is recommended for file level synchronization

Component

No.of
Servers

Operating System

CPUs
(Cores*3.0
GHz)

Memory
(In GB)

SAN Storage - GB Remarks

Production OID/OAM & SOA with High Availability Architecture with Active/Active Cluster

OID/OAM & SOA

Application Node 1

Linux x86_64

24

Application Node 2

Linux x86_64

24

Database Node 1

Linux x86_64

24

Database Node 2

Linux x86_64

24

Application Node

Linux x86_64

24

300

Database Node

Linux x86_64

24

500

Applications Tier

Linux x86_64

24GB

200

Database Server

Linux x86_64

24GB

300

200

Two Node Application Tier with the capability of load balancing and failover,
this requires HW Load balancer.

300

Database Cluster using the RAC solution with Active-Active Cluster with the
capability of Load balancing and failover.

Development & Test (Demo, Training)


Non-Production instances OID/OAM & SOA

Will share multiple non production instances

DR

DR for OID/OAM & SOA

DR solution based on Oracle's Dataguard Solution with the capability of


running Applications and Database on respective servers in the event of
production failover onto DR Site. It is assumed that only key users will be on
the system in case of disaster. This sizing is arrived assuming expected load
will be 50-60% in DR scenario without HA. Performance may vary in case of
DR scenario accordingly.
Disk replication is recommended for file level synchronization