Contents
Now that you have installed the AWS Schema Conversion Tool, the next step is to create a Database Migration Project using the tool.
Parameter | Value |
---|---|
Project Name | AWS Schema Conversion Tool Oracle to Aurora PostgreSQL |
Location | C:\Users\Administrator\AWS Schema Conversion Tool\Projects |
Database Type | SQL database |
Source Database Engine | Oracle / I want to switch engines and optimize for the cloud |
Parameter | Value |
---|---|
Type | SID |
Server Name | < SourceOracleEndpoint > |
Server Port | 1521 |
Oracle SID | ORACLEDB |
User Name | dbmaster |
Password | dbmaster123 |
Use SSL | Unchecked |
Store Password | Checked |
Oracle Driver Path | C:\Users\Administrator\Desktop\DMS Workshop\JDBC\ojdbc8.jar |
You may see a security warning prompt to use SSL. Click on “Accept the risk and continue” button.
DMS_SAMPLE
database, then click Next.After hitting Next and loading metadata, you may get a warning message saying: Metadata loading was interrupted because of data fetching issues. You can ignore this message as it doesn’t affect us in this workshop.
SCT will examine in detail all of the objects in the schema of source database. It will convert as much as possible automatically and provides detailed information about items it could not convert.
Generally, packages, procedures, and functions are more likely to have some issues to resolve because they contain the most custom or proprietary SQL code. AWS SCT specifies how much manual change is needed to convert each object type. It also provides hints about how to adapt these objects to the target schema successfully.
Parameter | Value |
---|---|
Target Database Engine | Amazon Aurora (PostgreSQL compatible) |
Server Name | < TargetAuroraPostgreSQLEndpoint > |
Server Port | 5432 |
Database Name | AuroraDB |
User Name | dbmaster |
Password | dbmaster123 |
Use SSL | Unchecked |
Store Password | Checked |
Amazon Aurora Driver Path | C:\Users\Administrator\Desktop\DMS Workshop\JDBC\postgresql-42.2.9.jar |