Wednesday Jul 11, 2012

Migrating blog entries

Moving blog entries from Oracle blog to Blogger was easy as Oracle blog has an export facility. You can find out more here: Migrating blog entries

Friday Jul 06, 2012

Middleware and Cloud Computing Book

One of only a couple books that really discusses AWS and Oracle in depth. This books is focused on AWS and Oracle middleware/fusion/weblogic:
AWS Middleware cloud computing book
It also covers Rackspace but in not near as much depth.

Tuesday Jul 03, 2012

Oracle Enterprise Manager with AWS Database Instance

Oracle Enterprise Manager 11g Database Control support was just announced this May. It seems like it may be a long time in coming but Oracle Database support on the AWS cloud was first released just a few years ago in September 2008. Here is a great blog entry on using OEM with Oracle on AWS:

AWS OEM for Oracle DB

Monday Jul 02, 2012

AWS EC2 Overview book

A very good introduction book to AWS can be found here:
AWS Book

I would say the title is misleading as this book is more an introduction and overview book then a programming book. However, very good for those IT people new to AWS.

AWS EC2 Oracle RDB - Storing and managing my data

When create an Oracle Database on the Amazon cloud you will need to store you database files somewhere on the EC2 cloud. There are basically three places where database files can be stored:
1. Local drive - This is the local drive that is part of the virtual server EC2 instance.
2. Elastic Block Storage (EBS) - Network attached storage that appears as a local drive.
3. Simple Storage Server (S3) - 'Storage for the Internet'.

S3 is not high speed and intended for store static document type files. S3 can also be used for storing static web page files. Local drives are ephemeral so not appropriate to be used as a database storage device. The leaves EBS which is the best place to store database files. EBS volumes appear as local disk drives. They are actually network-attached to an Amazon EC2 instance. In addition, EBS persists independently from the running life of a single Amazon EC2 instance. If you use an EBS backed instance for your database data, it will remain available after reboot but not after terminate. In many cases you would not need to terminate your instance but only stop it, which is equivalent of shutdown. In order to save your database data before you terminate an instance, you can snapshot the EBS to S3.

Using EBS as a data store you can move your Oracle data files from one instance to another. This allows you to move your database from one region or or zone to another. Unfortunately, to scale out your Oracle RDS on AWS you can not have read only replicas. This is only possible with the other Oracle relational database - MySQL. The free micro instances use EBS as its storage.

This is a very good white paper that has more details:
AWS Storage Options
This white paper also discusses: SQS, SimpleDB, and Amazon RDS in the context of storage devices. However, these are not storage devices you would use to store an Oracle database. This slide deck discusses a lot of information that is in the white paper:
AWS Storage Options slideshow

Sunday Jul 01, 2012

AWS CloudFormations, Oracle Assembly Builder, Chef and Puppet

I blogged about the difference and similarities between AWS CloudFormations and Oracle Assembler builder to package your software stack for deployment/provisioning to the cloud. However, these tools do not deal with software stack versioning and configuration management. This is where tools like Chef and Puppet come into play.
Puppet and Chef points of interest:
1. Can be used in any cloud environment (rackspace, private cloud etc).
2. There is a debate between which is better. I am not going to get into this debate other then to say Puppet is more mature.
3. AWS CloudFormations can integration with both Chef and Puppet.

A good blog on AWS CloudFormations and the need for something more:
AWS CloudFormation

Migrating legacy client/server and mainframe technologies to the Oracle cloud.


« July 2012