I have always been fascinated with new support for Oracle technologies on other cloud platforms. This enables all the Oracle users to spread their wings across cloud providers like AWS, Azure and Google. I was very excited with the news about Oracle support on Google cloud.
In this article, we will look at the support for Oracle Standard Edition 2 on AWS RDS Custom. But first, what is RDS Custom?
RDS Custom is a managed database service provided by AWS, but as an added advantage, you also get access to the underlying operating system. This would ensure that some legacy applications can still use the managed services from AWS for Oracle, not only for the enterprise edition but also for thestandard edition.
Navigate to RDS on the AWS console and then click on Create Database. The options below are shown. We use the standard create option for our purpose as we want to configure each step in this process. Choose Oracle
After choosing Oracle, this will navigate you to options of choosing Amazon RDS or Amazon RDS Custom, we choose Amazon RDS Custom and choose in edition choose Oracle Standard Edition Two. The next thing is to build a custom engine version of the latest Oracle release (We use version Oracle 19.19). We exactly followed the steps provided in the below link:
We chose dev/test as template as the system are going to be used for non-production purpose.
Provide the name for the DB instance and also name for the admin user to login to the database. The credential has to be self managed as RDS Custom does not support credentials management.
The next step is to choose a instance configuration that is needed . For this I have chosen a db.m6i.large (2vCPU and 8GB RAM). This is a standard class machine.
once the instance type is chosen, the next is to ensure that sufficient storage is added to the instance. The IOPS and storage throughput can also be configured, but we left it to default.
The next step is to choose a VPC or create one and below screenshot explains the details of the VPC.
This is an important step to ensure that a public IPAddress is assigned so that any other resources outside can connect to the instance. Also ensure that the security group has only the necessary traffic that is needed for this instance. For example, we have configured ports 1521 for Oracle database connection.
The below is an important step. Ensure that the automation is paused for any scheduled maintenance . This step is important when restarting database and also ensuring paused automation before running graceful switchover. Below is an example script to pause automation for some time.
./pause-automation-rds-oracle-custom.sh -n <instance name> -t <minutes>
Example:
$./pause-automation-rds-oracle-custom.sh -n test02 -t 840#!/bin/sh
helpFunction()
{
echo ""
echo "Usage: $0 -n instanceName"
echo "\t-n Name of the db-istance"
echo "\t-t Pause time in minutes"
# exit 1 # Exit script after printing help
}
while getopts "n:t:" opt
do
case "$opt" in
n ) instanceName="$OPTARG" ;;
t ) pauseTime="$OPTARG" ;;
? ) helpFunction; exit 0 ;; # Print helpFunction in case parameter is non-existent
esac
done
# Print helpFunction in case parameters are empty
if [ -z "$instanceName" ]
then
echo "-n is a mandatory parameter";
helpFunction
exit 1
fi
if [ -z "$pauseTime" ]
then
pauseTime="30"
fi
commandOutput=" "
aws rds modify-db-instance \
--db-instance-identifier $instanceName \
--automation-mode all-paused \
--resume-full-automation-mode-minutes $pauseTime >$commandOutput
echo $commandOutput
After the instance is created below is the instance connected directly from aws console using session manager from the AWS EC2 page.
I also found that some of the parameters on the database were Enterprise edition parameters so had to reset them.
db_block_checking
dg_broker_config_file1
dg_broker_config_file2Also, changed the archivelog destination from log_archive_dest_1 to db_recovery_file_dest .