Thanks for the nice comments. Yes DMS service can be used fro synchronizing different databases. For this you need AWS SCT or any other tool for the conversion. For more details on the availability zones query, you can refer to docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html
@@InfraXpertzz thanq, I have a scenario where I have my Oracle db in AZ1 and other Oracle db in AZ2. My requirement is to keep both databases alive and sync with each other. So using DMS replication instance I will create source endpoint (from AZ 1) and target endpoint(from AZ 2) and will keep both in sync. However when db in AZ 1 is down db in AZ2 has to become primary and what ever data coming to db in AZ 2 has to be in sync with db in AZ 1. So here if I create another replication instance with source (DB in AZ 2) and target (DB in AZ 1) endpoints, using both the replication instances will there be any chance of going duplication of data in the tables?
Thanks a lot for the nice comments. Are you asking "Using SSL with AWS Database Migration Service". If yes, you can have a look at the below link from AWS : docs.aws.amazon.com/dms/latest/userguide/CHAP_Security.html#CHAP_Security.SSL
Hi, thank you so much for your video. It was very informative. I am currently doing the same migration but it failed. It failed to migrate schema- SYSTEM , on table SCHEDULER_PROGRAM_ARGS_TBL with this error "Table has LOBS but no primary key". Do you have any idea how I can resolve this ?
Hi. Thanks a lot for the valuable comments :) You can browse the below link from AWS for your error : docs.aws.amazon.com/dms/latest/userguide/CHAP_Troubleshooting.html Pasting a solution from the link for your reference : LOB changes aren't being captured Currently, a table must have a primary key for AWS DMS to capture LOB changes. If a table that contains LOBs doesn't have a primary key, there are several actions you can take to capture LOB changes: 1. Add a primary key to the table. This can be as simple as adding an ID column and populating it with a sequence using a trigger. 2. Create a materialized view of the table that includes a system-generated ID as the primary key and migrate the materialized view rather than the table. 3. Create a logical standby, add a primary key to the table, and migrate from the logical standby.
Keeping an eye on the downtime part, dms can be suggested, since there would be a replication setup which would minimise the whole downtime. However, plz test it in a lower environment for the practical errors you may face with regards to indexes, triggers and constraints. Testing can be done anytime, since it doesn't require any downtime
I'm currently trying to this from our On-premise database using DMS but while testing the endpoint I'm getting "Test Endpoint failed: Application-Status: 1020912, Application-Message: OCI connection failure". I'm trying to do from on-premise oracle and not from EC2. I'm new to this can you please help me ?
Please check whether all connections are open or not. This is a connection issue. Check ur security group to see whether the port for your respective rds is open or not
@@InfraXpertzz I added inbound rule in SG for port 1521 but I'm still getting the same error. can you please tell me what'll details should I have handy ? Currently I have below details of on premise oracle database: 1) IP Address 2)Service Name 3) username and password 4) Port 5) database name I have created Replication instances and while creating endpoint, I did below configurations-- 1) Source engine- Oracle 2) Access to endpoint database (Provide access information manually ) i) Server name - Added above IP address ii) Port - 1521 iii) user and password- the above username and password. iv) SID/Service name - the above database name while testing I'm getting that error. Thank you in advance :)
Thanks a lot for the nice comments. The document isn't well maintained and the steps aren't in an organized manner. Hence it is problematic to share the steps. Also, no screenshots are present in the document
Hi Raj, You can now find the detailed steps in our blog. Please visit our blog to find out more infraxpertzz.com/migration-and-replication-full-load-cdc-of-on-premise-oracle-11g-database-to-aws-rds-oracle-19c/
Dear Dinesh. This was already mentioned in our videos that we are using ec2, since dns setup using home laptop isn't an easy task. Also a database hosted in ec2, is similar to an on premise database, as u get control over the host too. So the steps are same as an on premise database
do we need to enable archive log mode for source oracle database to follow this DMS migration method ?
Good Explanation. Shall we use this DMS service for synchronising different databases (Oracle to Oracle only) exists in different Availability Zones ?
Thanks for the nice comments. Yes DMS service can be used fro synchronizing different databases. For this you need AWS SCT or any other tool for the conversion. For more details on the availability zones query, you can refer to docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html
@@InfraXpertzz thanq, I have a scenario where I have my Oracle db in AZ1 and other Oracle db in AZ2. My requirement is to keep both databases alive and sync with each other. So using DMS replication instance I will create source endpoint (from AZ 1) and target endpoint(from AZ 2) and will keep both in sync. However when db in AZ 1 is down db in AZ2 has to become primary and what ever data coming to db in AZ 2 has to be in sync with db in AZ 1. So here if I create another replication instance with source (DB in AZ 2) and target (DB in AZ 1) endpoints, using both the replication instances will there be any chance of going duplication of data in the tables?
Please read replica. In this scenario, dms won't serve the purpose. Read replica with multi az is recommended
@@InfraXpertzz will read replica and multi AZ supports EC2?
Is ur database hosted on ec2? Read replica is solely for rds
Thanks you for detailed explanation.can you please share or create any doc for replication using ssl.
Thanks a lot for the nice comments. Are you asking "Using SSL with AWS Database Migration Service". If yes, you can have a look at the below link from AWS :
docs.aws.amazon.com/dms/latest/userguide/CHAP_Security.html#CHAP_Security.SSL
Thank you
My pleasure
We are trying full load + cdc but after one day our source database shut down because of migration task. Any idea?
We didn't find a related error in cloudwatch.
Hi, thank you so much for your video. It was very informative. I am currently doing the same migration but it failed. It failed to migrate schema- SYSTEM , on table SCHEDULER_PROGRAM_ARGS_TBL with this error "Table has LOBS but no primary key". Do you have any idea how I can resolve this ?
Hi. Thanks a lot for the valuable comments :)
You can browse the below link from AWS for your error :
docs.aws.amazon.com/dms/latest/userguide/CHAP_Troubleshooting.html
Pasting a solution from the link for your reference :
LOB changes aren't being captured
Currently, a table must have a primary key for AWS DMS to capture LOB changes. If a table that contains LOBs doesn't have a primary key, there are several actions you can take to capture LOB changes:
1. Add a primary key to the table. This can be as simple as adding an ID column and populating it with a sequence using a trigger.
2. Create a materialized view of the table that includes a system-generated ID as the primary key and migrate the materialized view rather than the table.
3. Create a logical standby, add a primary key to the table, and migrate from the logical standby.
To migrate on-premise Oracle database of size 1.5TB to AWS EC2, is DMS feasible or can be suggested?
Keeping an eye on the downtime part, dms can be suggested, since there would be a replication setup which would minimise the whole downtime. However, plz test it in a lower environment for the practical errors you may face with regards to indexes, triggers and constraints. Testing can be done anytime, since it doesn't require any downtime
I'm currently trying to this from our On-premise database using DMS but while testing the endpoint I'm getting "Test Endpoint failed: Application-Status: 1020912, Application-Message: OCI connection failure". I'm trying to do from on-premise oracle and not from EC2. I'm new to this can you please help me ?
Please check whether all connections are open or not. This is a connection issue. Check ur security group to see whether the port for your respective rds is open or not
@@InfraXpertzz I added inbound rule in SG for port 1521 but I'm still getting the same error. can you please tell me what'll details should I have handy ?
Currently I have below details of on premise oracle database:
1) IP Address
2)Service Name
3) username and password
4) Port
5) database name
I have created Replication instances and while creating endpoint, I did below configurations--
1) Source engine- Oracle
2) Access to endpoint database (Provide access information manually
)
i) Server name - Added above IP address
ii) Port - 1521
iii) user and password- the above username and password.
iv) SID/Service name - the above database name
while testing I'm getting that error.
Thank you in advance :)
Is this u r trying from ur own virtual box or its related to ur clients environment where the DNS of the on premise is properly set up
@@InfraXpertzz I'm trying to migrate oracle database located on remote server to Amazon RDS. Can please help me in this ?
Good Explanation. Could you please share me the your document for reference and will help me to do it
Thanks a lot for the nice comments. The document isn't well maintained and the steps aren't in an organized manner. Hence it is problematic to share the steps. Also, no screenshots are present in the document
Hi Raj,
You can now find the detailed steps in our blog. Please visit our blog to find out more
infraxpertzz.com/migration-and-replication-full-load-cdc-of-on-premise-oracle-11g-database-to-aws-rds-oracle-19c/
it is not on prem to cloud as on prem db is in ec2
Dear Dinesh. This was already mentioned in our videos that we are using ec2, since dns setup using home laptop isn't an easy task. Also a database hosted in ec2, is similar to an on premise database, as u get control over the host too. So the steps are same as an on premise database
EWE ASMELASH KEMEY