Thursday, February 21, 2013

Cloud Migrations using Racmi

Here is company that can move 'as is' (lift and shift) from on premise to AWS :

Getting Started with WebLogic on AWS

Here are the links to get you started with Oracle WebLogic on AWS/EC2:
1. Oracle on AWS FAQ - 
2. Landing page on AWS - 
3. Oracle Amazon Machine Imagines - 
There are AMIs on the AWS web site but you are best to create your own AMI with the OS of your choice and install WebLogic on this base instance. . The AMIs Oracle has posted here are really just to get started.  They are really not even good for demo or POC usage. You can find the latest OEL AMIs, for OEL 5.9 and 6.4, at the bottom of this web page:  
4. EC2 Instances available - 
5. EC2
6. Pricing calculator - 

1. Oracle licensing : You bring your own license.  You can not buy a license from AWS. This can be an     Oracle ULA, ELA, or perpetual licenses. The only support AWS has for AWS compute with Oracle license included is for AWS RDS. For all other, you have to BYOL.  A partner can use OPN licenses for test and development.  OTN licenses are only for trials of 30 days or less.
Oracle on AWS licensing document is here:
2. The bulk of the AWS cost is composed of EC2 compute, storage (EBS and S3) and network (data transfer out). The pricing calculator above can give you an estimate of AWS cost.
3. Oracle support on AWS : 

Wednesday, February 20, 2013

Running Oracle EBusiness Suite on AWS

A common question for Oracle EBusiness Suite users or potential users is 'Where do I get started?'.  Here is some information to help with:
  1. Where not to start :
  2. It is best to create your own AMI or using an existing Linux AMI:
  3. Instructions for installing Oracle EBusiness Suite vision demo
  4. Creating you own AMI 'gold imagine' 
  5. CloudFormation : You will want to use CloudFormation templates to automate the process of configuring the security groups, VPC, and the EC2 instances required:
  6. Test drives : The Oracle EBusiness Suite test drive labs are a great place to start:

Tuesday, February 12, 2013

Oracle Secure Backup restore

A benchmark test using OSB, a DBA, was able to restore 3.8 terabytes in 2.5 hours over gigabit Ethernet. This amounts to 25 gigabytes per minute, or 422MB per second. This 2.5 hours using OSB and S3 compares to, conservatively, 10-15 hours that would be required to restore from tape.

Monday, February 11, 2013

Global data volumes

The global data volume at the end of 2009 has reached 800 EB according to The Internet video will generate over 18 EB/month in 2013; global mobile data traffic will reach 2 EB/month by 2013 according to a report from CISCO ( solutions sub solution.html).

Network speeds and Moore's Law

The speed of the Ethernet has increased from 1 Gbps in 1997 to 100 Gbps in 2010; this increase is slightly slower than the Moore law for traffic [251] which would require 1 Tbps Ethernet by 2013.

Oracle DB data transfer to AWS

A typical Oracle database is 1 TB or more in size. This will mean that a T3 line or higher speed line will be needed to move this much data. Otherwise, the AWS import export service can be used. The information below is from the web page but repeated here for easy of finding.

Connection           Theoretical 80% Utilization    AWS Imp/Exp
T1 (1.544Mb)        82 days                                    100GB or more
10Mbps                  13 days                                    600GB or more
T3 (44.736Mbps)    3 days                                      2TB or more
100Mbps               1 to 2 days                                 5TB or more
1000Mbps             Less than 1 day                         60TB or more

Elapsed time is going to depend on many factors: speed of connection, compression used (if any), can load be done in parallel etc. The fastest load times will happen using AWS import/export ( ). The next fastest will be using AWS Direct Connect ( 

Direct Connect provides speeds of 1 Gbps to 10 Gbps. Using a 1 Gbps line, it would take about 3-4 hours (here is a good site: 

Oracle licensing on AWS

I may have blogged about this already, but want to give more detail as this question keeps coming up. Customers and partners want to know specifically how licenses purchased from Oracle or used on AWS as part of their ULA and ELA agreements are converted to cores and sockets on AWS.  Here is an example that I believe will clear things up:
  1. Standard Edition - EC2 instances with 4 or less virtual cores are counted as 1 socket, which is considered equivalent to a processor license. For EC2 instances with more than 4 virtual cores, every 4 virtual cores used (rounded up to the closest multiple of 4) equate to a licensing requirement of 1 socket.  This means that running on m1.small, m1.medium, m1.large and m1.xlarge will all cost the same from an Oracle perspective. Details are: "When licensing Oracle programs with Standard Edition One or Standard Edition in the product name, the pricing is based on the size of the EC2 instances. Authorized Cloud Environment instances with 4 or fewer virtual cores are counted as 1 socket, which is considered equivalent to a processor license. For Authorized Cloud Environment instances with more than 4 virtual cores, every 4 virtual cores used (rounded up to the closest multiple of 4) equate to a licensing requirement of 1 socket."
  2. Enterprise Edition - .5 multiplier which means you need 1 Oracle license for every 2 virtual cores on EC2.  This means that  running on m1.small, m1.medium, and  m1.large will all cost the same from an Oracle perspective.  Running on m1.xlarge would cost double the price since it has 4 virtual cores.
A virtual core is not the same as a vCPU. More on virtual cores here:

All the details can be found on the Oracle web site here: 

Of course, you should check with Oracle to make sure that you are in compliance.

IT budget and energy

It was predicted that by 2012 up to 40% of the budget of IT enterprise infrastructure would be spent on energy.   
From: M. D. Dikaiakos, D. Katsaros, P. Mehra, G. Pallis, and A. Vakali. “Cloud computing: distributed internet computing for IT and scientific research.” IEEE Internet Computing, 13(5):10–13, 2009.
Not sure if this has come true but is a big number.