{"id":13672,"date":"2020-03-17T15:24:01","date_gmt":"2020-03-17T14:24:01","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/migrating-an-oracle-instance-to-aws-aurora-1-setting-up-the-base-infrastructure\/"},"modified":"2020-03-17T15:24:01","modified_gmt":"2020-03-17T14:24:01","slug":"migrating-an-oracle-instance-to-aws-aurora-1-setting-up-the-base-infrastructure","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/migrating-an-oracle-instance-to-aws-aurora-1-setting-up-the-base-infrastructure\/","title":{"rendered":"Migrating an Oracle instance to AWS Aurora – 1 – Setting up the base infrastructure"},"content":{"rendered":"

Migrating database to the cloud is a hot topic since a few years. As more and more of our customers are in the cloud, and some of them in AWS<\/a>, migrating some of their Oracle databases to AWS Aurora becomes a topic from time to time. In this little blog series we’ll have a look at how you can use the AWS Database Migration Service (DMS)<\/a> and the AWS Schema Conversion Tool (SCT)<\/a> for simplifying such a task. In this very first post we’ll setup the basic infrastructure we need for the demo.<\/p>\n

<\/p>\n

I’ll be using Terraform<\/a> once again for bringing up all the basic stuff. For the purpose of VPCs<\/a>, Subnets<\/a>, route tables<\/a> and Security Groups<\/a> please check the AWS documentation, this is not in the scope of this post.<\/p>\n

The first thing to do in the Terraform script is to specify the AWS profile and region we want to use:<\/p>\n

\n\/\/ set the provider to AWS and the AWS region to eu-central-1\nprovider \"aws\" {\n  profile    = \"test\"\n  region     = \"eu-central-1\"\n}\n<\/pre>\n
After that there are two variables: the first one defines my local IP-address which is used in the security group definitions below, so connections via SSH and RDP will be possible from my current location. The second one defines the User data<\/a> that will be passed to the EC2 instance that will host the Oracle source database. Basically it installs the Oracle Database Express Edition (XE) Release 18.4.0.0.0 (18c) and the Oracle sample schemas:<\/p>\n
\nlocals {\n  my_ip        = [\"XXX.XXX.XXX.XXX\/32\"]\n  instance-userdata = <<EOF\n#!\/bin\/bash\nsudo yum update -y\nsudo yum install -y wget perl\nwget https:\/\/download.oracle.com\/otn-pub\/otn_software\/db-express\/oracle-database-xe-18c-1.0-1.x86_64.rpm -O \/home\/ec2-user\/oracle-database-xe-18c-1.0-1.x86_64.rpm\nwget https:\/\/yum.oracle.com\/repo\/OracleLinux\/OL7\/latest\/x86_64\/getPackage\/oracle-database-preinstall-18c-1.0-1.el7.x86_64.rpm -O \/home\/ec2-user\/oracle-database-preinstall-18c-1.0-1.el7.x86_64.rpm\nwget wget http:\/\/mirror.centos.org\/centos\/7\/os\/x86_64\/Packages\/compat-libstdc++-33-3.2.3-72.el7.i686.rpm -O \/home\/ec2-user\/compat-libstdc++-33-3.2.3-72.el7.i686.rpm\nsudo yum localinstall -y \/home\/ec2-user\/compat-libstdc++-33-3.2.3-72.el7.i686.rpm\nsudo yum localinstall -y \/home\/ec2-user\/oracle-database-preinstall-18c-1.0-1.el7.x86_64.rpm\nsudo yum localinstall -y \/home\/ec2-user\/oracle-database-xe-18c-1.0-1.x86_64.rpm\n(echo \"manager\"; echo \"manager\";) | \/etc\/init.d\/oracle-xe-18c configure\nsudo echo ORACLE_HOME=\/opt\/oracle\/product\/18c\/dbhomeXE\/ >> \/home\/oracle\/.bash_profile\nsudo echo PATH=$PATH:$ORACLE_HOME\/bin >> \/home\/oracle\/.bash_profile\nsudo echo ORACLE_SID=xe >> \/home\/oracle\/.bash_profile\nsudo echo export ORACLE_HOME PATH ORACLE_SID >> \/home\/oracle\/.bash_profile\nwget https:\/\/github.com\/oracle\/db-sample-schemas\/archive\/v19.2.tar.gz -O \/home\/oracle\/v19.2.tar.gz\nsudo su - oracle -c \"tar -axf v19.2.tar.gz\"\nsudo su - oracle -c \"cd db-sample-schemas-19.2; perl -p -i.bak -e 's#__SUB__CWD__#\/home\/oracle\/db-sample-schemas-19.2#g' *.sql *\/*.sql *\/*.dat\"\nsudo su - oracle -c \"cd db-sample-schemas-19.2; sqlplus system\/manager@localhost\/XEPDB1 @mksample manager manager manager manager manager manager manager manager users temp \/tmp\/ localhost\/XEPDB1\"\nchkconfig --add oracle-xe-18c\nEOF\n}\n<\/pre>\n
The next lines of the Terraform script will setup all the network related stuff which I am not going to explain here:<\/p>\n
\n\/\/ create the virtual private network\nresource \"aws_vpc\" \"dwe-vpc\" {\n  cidr_block = \"10.0.0.0\/16\"\n  enable_dns_hostnames = true\n  enable_dns_support = true\n  \n  tags = {\n    Name = \"dwe-vpc\"\n  }\n}\n\n\/\/ create the internet gateway\nresource \"aws_internet_gateway\" \"dwe-igw\" {\n  vpc_id = \"${aws_vpc.dwe-vpc.id}\"\n\n  tags = {\n    Name = \"dwe-igw\"\n  }\n}\n\n\/\/ create a dedicated subnet\nresource \"aws_subnet\" \"dwe-subnet\" {\n  vpc_id            = \"${aws_vpc.dwe-vpc.id}\"\n  cidr_block        = \"10.0.1.0\/24\"\n  availability_zone = \"eu-central-1a\"\n\n  tags = {\n    Name = \"dwe-subnet\"\n  }\n}\n\n\/\/ create a second dedicated subnet, this is required for RDS\nresource \"aws_subnet\" \"dwe-subnet-2\" {\n  vpc_id            = \"${aws_vpc.dwe-vpc.id}\"\n  cidr_block        = \"10.0.2.0\/24\"\n  availability_zone = \"eu-central-1b\"\n\n  tags = {\n    Name = \"dwe-subnet-2\"\n  }\n}\n\n\n\/\/ create routing table which points to the internet gateway\nresource \"aws_route_table\" \"dwe-route\" {\n  vpc_id = \"${aws_vpc.dwe-vpc.id}\"\n\n  route {\n    cidr_block = \"0.0.0.0\/0\"\n    gateway_id = \"${aws_internet_gateway.dwe-igw.id}\"\n  }\n\n  tags = {\n    Name = \"dwe-igw\"\n  }\n}\n\n\/\/ associate the routing table with the subnet\nresource \"aws_route_table_association\" \"subnet-association\" {\n  subnet_id      = \"${aws_subnet.dwe-subnet.id}\"\n  route_table_id = \"${aws_route_table.dwe-route.id}\"\n}\n\n\/\/ create a security group for ssh access to the linux systems\nresource \"aws_security_group\" \"dwe-sg-ssh\" {\n  name        = \"dwe-sg-ssh\"\n  description = \"Allow SSH inbound traffic\"\n  vpc_id      = \"${aws_vpc.dwe-vpc.id}\"\n\n  ingress {\n    from_port   = 22\n    to_port     = 22\n    protocol    = \"tcp\"\n    cidr_blocks = local.my_ip\n  }\n\n  \/\/ allow access to the internet\n  egress {\n    from_port   = 0\n    to_port     = 0\n    protocol    = \"-1\"\n    cidr_blocks = [\"0.0.0.0\/0\"]\n  }\n\n  tags = {\n    Name = \"dwe-sg-ssh\"\n  }\n}\n\n\/\/ create a security group for rdp access to the windows systems\nresource \"aws_security_group\" \"dwe-sg-rdp\" {\n  name        = \"dwe-sg-rdp\"\n  description = \"Allow RDP inbound traffic\"\n  vpc_id      = \"${aws_vpc.dwe-vpc.id}\"\n\n  ingress {\n    from_port   = 3389\n    to_port     = 3389\n    protocol    = \"tcp\"\n    cidr_blocks = local.my_ip\n  }\n\n  \/\/ allow access to the internet\n  egress {\n    from_port   = 0\n    to_port     = 0\n    protocol    = \"-1\"\n    cidr_blocks = [\"0.0.0.0\/0\"]\n  }\n\n  tags = {\n    Name = \"dwe-sg-rdp\"\n  }\n}\n<\/pre>\n
Once the network is ready we’ll deploy the EC2 instance that will run the Oracle database (Red Hat 7.7 in this case):<\/p>\n
\n\/\/ setup a red hat 7 system for the oracle source\nresource \"aws_instance\" \"dwe-oracle-source\" {\n  ami                         = \"ami-05798e9b15f285b27\"\n  instance_type               = \"t2.medium\"\n  key_name                    = \"dwe-key-pair\"\n  vpc_security_group_ids      = [\"${aws_security_group.dwe-sg-ssh.id}\"]\n  subnet_id                   = \"${aws_subnet.dwe-subnet.id}\"\n  associate_public_ip_address = \"true\"\n  user_data                   = \"${base64encode(local.instance-userdata)}\"\n\n  root_block_device {\n    volume_size           = \"30\"\n    volume_type           = \"standard\"\n    delete_on_termination = \"true\"\n  }\n\n  tags = {\n    Name = \"dwe-oracle-source\"\n  }\n}\n<\/pre>\n
As the target for the migration will be an Aurora cluster we will need that as well. This are basically three steps:<\/p>\n