I'm creating AWS RDS instance to migrate existing on-prem oracle database to AWS Rds instance.
Existing On-prem oracle database is appox 700GB.
I've two queries
what allocate storage size should i use for RDS oracle database instance,
should it be equal or greater then on-prem oracle database?
which instance type should be suitable for size of database?
If you are using S3 import method with Data Pump, you would need sufficient space to download the backup file to RDS Oracle instance + restore the same, so a little more than double should be a good option to create with(~1.5TB). If you are using some other method where you don't need the backup file on RDS, you can try provisioning around 800 GB initially.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Oracle.Procedural.Importing.html#Oracle.Procedural.Importing.DataPump
It depends on your workload, and you might need to look at current Oracle AWR reports to analyze suitable CPU and RAM requirements. Nevertheless, you can start with something which you feel should suffice, and scale up or down as needed.
Related
We need to migrate an Oracle DB from Azure VM to AWS RDS Aurora. And we have a checklist that what are the things we have to take care while doing migration from Oracle to Aurora.
But, what would be the best approach to do the migration. i.e., Migrate Azure Oracle VM to AWS EC2 and then, migrate to RDS. Or Migrate directly from Azure VM to AWS RDS Aurora using any Azure service(s), DMS, Datapump, SCT, something like that.
(I am not familiar with Azure DMS / DB related services)
I would go direct from Azure Oracle RM to the AWS RDS.
For the tool take a look at using the AWS Database Migration Service (DMS). It lets you connect to your source database (Azure Oracle) to your target database (AWS RDS For Oracle). AWS DMS handles creating the schema and tables in the target database.
The DMS deploys on dedicated VMs for you migration and is priced based on the size of the EC2 instance you will need from a t2.micro ($0.43/day) to a r4.8xlarge ($80/day + storage cost) and everything in between Data transfer into DMS is free and transfer to an RDS in the same AZ (availability zone) as the DMS is free.
A few features that makes the DMS nice include:
Continuous Data Replication: Once your initial migration is completed it can continue to replicate the data until you are ready to make the switch. This is nice because you do your migration ahead of time and have plenty of time for verification before you switch the application over.
Schema Conversion Tool: Not useful in your case but if you where migrating from to a different database such as Oracle to Aurora it would handle the schema for you.
You can learn more and get start at AWS Database Migration Service
Do any one know how to see the total space used and available in aws aurora schema, also the memory of the cluster within DB itself using queries. We are using AWS aurora psql and we don't have console, hence we want to try the same from queries like we will do for oracle.
This is most likely not doable using a SQL query in aurora, specifically the volume size. As an alternative, if you do have AWS CLI access, you should be able to query Cloudwatch metrics under "AWS/RDS" namespace to get these metrics in a more reliable and accurate manner. The ones you are interested in are "VolumeBytesUsed" and "CPUUtilization" if I'm not mistaken.
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Aurora.Monitoring.html
We have a production Oracle 11g SE1 database in an AWS RDS instance. Seems like the Oracle statpack user is using huge storage space from the total storage. I want to purge some statpack snapshots to free some space. Has purging those snapshots an effect to the data of the database? Or is there any other side effects?
I have been assigned to move 10g database to AWS Oracle 12c. Size of data is around 20 GB of actual data but 900 GB has been allocated. So we will need to decrease that. Any suggestions on how to migrate and reduce the size of the database?
This is a good summary of several options:
Importing Data Into Oracle on Amazon RDS
Also here is the Oracle migration Whitepaper.
The solution depends on the size of your data and the accepted downtime.
Personally I used Data Dump in a project, it works well for the size of data you have. I'm not sure about the resizing.
How different is the Amazons RDS DB Instance different from The normal EC2 Instance other than the fact that RDS DB Instance has a Database server running on it?
When an EC2 Instance goes down all the data associated with it also vanishes(when you dont attach an EBS). Is this true for RDS DB Instance as well?
I have already set up my database server with the following: 1 small Instance?(m1.small) with Mysql and attached a 10GB EBS and routed the Mysql Data Directories to EBS.
Is the small Instance of EC2 RDS any Different from the above?
An RDS db instance can be configured to not lose any data during downtime, either planned or unplanned. For unplanned downtime, AWS keeps transaction logs which are replayed automatically on a failover instance. These logs can also be used to get an instance to a specific point in time.
For planned downtime, you create a DB snapshot prior to stopping the instance, and can later start a new instance with the saved snapshot.
RDS is a unmanaged MySQL service, means you only start and load data into it and your ready to go.
Is the small Instance of EC2 RDS any Different from the above?
The small instance of RDS is a 64bit, which support multi AZ failover and pricing obviously is a little expensive compared to EC2 MySQL.
EC2 Mysql needs more administration, but you can setup it up to do replication and you can customize it to have better performance compared to RDS.
See also http://www.dotdeb.org/2010/05/04/mysql-on-amazon-benchmarks-rds-vs-ec2/