Bobcares

AWS DMS Oracle To Aurora PostgreSQL | Migration Guide

by | Sep 24, 2023

Let’s see how we can migrate data from Oracle to Aurora PostgreSQL using AWS DMS. As part of our AWS Support Services, Bobcares provides answers to all of your AWS questions.

How to Migrate Data from Oracle to Aurora PostgreSQL using AWS DMS?

There are various processes involved in moving data from Oracle to Amazon Aurora PostgreSQL using the AWS DMS. Oracle to Aurora PostgreSQL migrations are made easier by AWS DMS.

Steps to Migrate Data from Oracle to Aurora PostgreSQL using AWS DMS

1. Firstly, make sure that the AWS account is configured and that we have the rights to use AWS DMS, create Amazon Aurora PostgreSQL instances, and alter network settings.

2. Then, create a PostgreSQL instance on Amazon Aurora if we haven’t previously done so via the AWS Management Console. So, set the instance size, security group, and subnet group according to the needs.

3. Also, make sure that the migration settings on the Oracle database are correct. Make a user account with read-only access and the proper permissions for the migration procedure. Using this account, AWS DMS will read data from the Oracle source.

4. Now, make a new replication instance in the AWS DMS console. The endpoint for data migration from Oracle to Aurora PostgreSQL is this instance.

5. Create an Oracle database source endpoint. Also, specify the host, port, username, and password for the connection.

6. For the Aurora PostgreSQL instance, specify a target endpoint. Then, give the security group settings and endpoint information.

7. Then, create a replication instance and set the source and target endpoints for it to use.

8. Create a migration task in the AWS DMS console by entering the source and target endpoints, the migration type, as well as the migration options. A full migration or continual replication (CDC – Change Data Capture) are also options.

9. Start the migration task in the AWS DMS console once it has been configured. The data from the Oracle source will start to replicate to the Aurora PostgreSQL destination using AWS DMS.

10. Follow the development of the data migration and keep a check on the AWS DMS work status. In order to keep track of the task’s progress and spot any problems, use the metrics and logs provided by AWS CloudWatch.

11. Verify the data consistency and integrity between the Oracle source and Aurora PostgreSQL target after the completion of the migration. If there are any discrepancies, we also need to resolve them.

12. Then, use the new Aurora PostgreSQL database endpoint and credentials in the apps and services.

13. We can complete the move by decommissioning the Oracle database and clearing off any resources we no longer require once we’ve verified that the migration was successful as well as the app is operating as intended.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To conclude, we’ve provided a 13-step method from our Tech team to migrate data from Oracle to Aurora PostgreSQL using AWS DMS.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF