1. Move to AWS
EDW Replatforming

2. Business Case Oracle Exadata X1 11g (est. 2008/2009)
Out of life, paying 3rd party for support
Hardware failure (Switches, disks, etc.)
Difficulty in meeting service level agreements
Reduction in data center foot print
Does not want to own IT assets
Technology refresh
On old HP hardware
3months after purchase Oracle acquired Sun and rolled out new appliance.
No discount was offered our customer to convert to new platform. (~$1 million)

3. Dirty Laundry EDW Appliance has never been patched nor upgraded
Back ups were stored locally on appliance storage array
EDW was not part of IT change management process
Could not track nor trend changes and or issues
22 Nodes to manage between the two X1 appliances across two data centers (AWS reduces to 5)

4. Scope Replace Oracle Exadata in both prod and non prod data centers
Evaluate and determine costs and risk with platform & software change
5 year total cost of ownership
Labor/Time
Risk of failure with code changes (Sysdate() vs. Getdate()
Licensing considerations
Company’s strategic direction
Upgrade to Oracle 12c

5. Goals Maintain >= performance
Assumption that our customer can $$$ for performance
Co-location of reporting and analytics software stack
Oracle EDW & Application Rep Databases
Business Objects 4.1 SP6
Informatica 9.6 (Upgrade to for 12c support)
Tableau (New purchase established in AWS)
No new net purchase of software licenses
Deliver within FY16 with $1.3 mil budget

6. Technical Solutions Moved to production back ups to AWS Provisioned:
1 x r3.8xlarge 35TB EBS Storage ($5,985/month)
Provisioned:
Oracle 12c on RHEL 6.7:
App Repo Dbase: 3 x R3.xlarge
EDW Prod: 1 x m4.4xlarge,
EDW Stage: 1 x r3.2xlarge
EDW Dev/Test: 2 x r3.4xlarge
Informatica (RHEL 6.7): 4 x r3.2xlarge
BOBJ 4.1 SP6 (Win 2012R2): 10 x r3.xlarge

7. Lesson’s Learned
Oracle RDS (PaaS) cost effective but 6TB limit, no control of outage/maintenance window, no RAC option.
Our customer uses AWS Direct connect 1GB pipe between VPCs. (10GB option at $60k-$50k/month)
Cost effective to over provision G-SSD to get IOPS.
Appliance based database appliance allows for inefficient database design and ETL design
Implement indexing, partition, tuning strategies.
Implement ASM and actively manage data, database volumes
4TB of data = 20TB of storage requirements. 2 Full back ups, 1 week archive logs, and 5 days of incremental
12c’s pluggable dbase and in-Memory require additional licenses ($23K per core similar to RAC pricing)