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?
Related
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.
I am exploring the shift of Oracle DB from on-prem to RDS in AWS. I have my own Oracle license, and I am running on a single server (no HA). I want to have Master-Slave in RDS on Multi-AZ (HA/FT). Now, I know I can bring my own license (BYOL) into RDS but what happen when I go from a sinlge license to a multi-AZ? I can't find anything online so far.
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
I was wondering whether MySQL commands like NOLOCK or creation of indexes is actually supported on Aurora AWS? Also, can I do performance issue investigation or is Aurora AWS a "black-box" to me?
The Aurora it is completely different database than MySQL, but when it comes to the compability with MySQL or PostgreSQL Amazon team did a lot so that there would not be a lot of differences. "The Amazon Aurora MySQL is designed to be wire-compatible with MySQL 5.6 and 5.7 using the InnoDB storage engine. Certain MySQL features like the MyISAM storage engine are not available with Amazon Aurora." Amazon Aurora MySQL 2.01 does not currently also support the following MySQL 5.7 features:
Global transaction identifiers (GTIDs)
Group replication plugin
Increased page size
InnoDB buffer pool loading at startup
InnoDB full-text parser plugin
Multisource replication
Online buffer pool resizing
Password validation plugin
Query rewrite plugins
Replication filtering
The CREATE TABLESPACE SQL statement
X Protocol
(source:https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.2022.html)
But it changes from release to release.
Answering to you question about a performance monitoring. You can monitor Aurora database from AWS Console or by using queries directly on Aurora database, the same as in case of MySQL. Staring from version 2.03 there is also available the performance schema.
UNLOCK command - I am not sure whether it also exists in native MySQL, but there is possiblity to set transaction isolation level.
Indexes - yes, you can also create indexes on Aurora.
I hope the information will be useful for you.
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.