Amazon Web Services (AWS) : Relational Database Services (RDS) for Oracle
In this blog we are going to install Oracle on Amazon Web Services(AWS).
Create a New Oracle Service
Select the RDS option from the service catalog.
Select the “Oracle EE” option by clicking the “Oracle” tab and clicking the “Select” button next to the “Oracle EE” option.
Select the high-availability state of the service. In this case I’m using the non-production option. When you’ve made your choice, click the “Next Step” button.
Enter the database details. If you are trialling the service, be careful about the options you pick. If you pick the on-demand license model your service costs will include the Oracle licensing, making the hourly cost significantly more expensive. Once you are happy with the settings click the “Next Step” button.
Enter the advanced settings, making sure the character set, backup and maintenance settings are correct for your service. Once you are happy with the settings click the “Launch DB Instance” button.
Click the “View Your DB Instances” button to see the status of your service.
The resulting page shows the status of your services. Once the status is “available”, you can connect to the service. If you want to see the monitoring information for the specific service, click the checkbox next to the service and click the “Show Monitoring” button.
The following picture shows the monitoring graphs.
Reservations of Oracle on usage :
- You do not get access to the SYS user. You only have access to a DBA user.
- Some of the operations you would typically expect to do as a DBA are restricted. Instead, you have to use the
RDSADMIN.RDSADMIN_UTILpackage, which provides an API to perform these tasks.
- With a few exceptions, you do not have direct access to the file system, so if you have processes that sFTP/SCP data to the server to be loaded, you may have to think again.