Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Once this is completed and added. Click on “Launch Instance” to start the instance. There are also options to have reserved public IP to ensure that the IPAddresses do not change after every server restart. These can be used for machines that are created for permanent production use. For this use case we have not enabled them as these machines are used only for temporary purposes. The machine name has also been set to desired one using the tags.

...

Once the server has been launched. Repeat the same to do for the second server with a different name but use the same VPC, security group and also IAM profile. Now we have two servers. Below is the details of one of them.

...

Login to the servers using SSH.

...

3. Installation and Configuration (Oracle and Standby MP)

We now have two servers that can ping each other and connect to them using ssh and also security groups configured to establish connection using the ports 7890,5533 and 4433.

The next steps that were completed are,

a. Installing Oracle on both primary and standby. Create a new database on the primary server.

Code Block
ec2-user@localhost[/home/ec2-user]: sudo su - oracle
Last login: Fri Apr 26 14:40:39 NZST 2024 on pts/0
The Oracle base has been set to /u01/app/oracle
oracle@localhost[/home/oracle]: cat /etc/oratab
SRC:/u01/app/oracle/product/19.3/dbhome_1:N
oracle@localhost[/home/oracle]: ps -ef |grep pmon
oracle    7667     1  0 14:42 ?        00:00:00 ora_pmon_SRC
oracle    8936  8860  0 14:58 pts/0    00:00:00 grep --color=auto pmon
SQL> select name,open_mode from v$database;

NAME      OPEN_MODE
--------- --------------------
SRC       READ WRITE

b. Create dbvisit directory on both primary and standby server for installing Dbvisit under /usr directory.

Code Block
root@localhost[/root]: cd /usr
root@localhost[/usr]: mkdir dbvisit
root@localhost[/usr]: chown oracle:oinstall dbvisit/