Page Comparison

...

Configuring Dbvisit StandbyMP for Oracle SE on AWS Custom

Step 1: Creating your Oracle database.

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

...

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 and also ports 7890,5533 and 4433 for Dbvisit standby configuration.

...

The below is an important step. Ensure that the automation is paused for any scheduled maintenance Important: Implement Script for Pausing Automation for Scheduled Maintenance and Switchovers . 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.

...

After the instance is created below is the instance connected directly from aws console using session manager from the AWS EC2 page.

...

...

Installing the Dbvisit StandbyMP Agent Manager and Control Center

1. Pause the automation on the second server. Drop the database.

2. Install the agentmanager on the primary and also agentmanager and control center on the standby. For detailed installation documentation click here.

Primary:

bash-4.2$ ps -ef |grep dbv
rdsdb     6017 23277  0 Aug09 ?        00:00:16 /rdsdbdata/dbvisit/standbymp/bin/dbvhelper -agentManagerId 3oychmd4s3l5 -directorId 3rxxfok6zctlm -hostAddress ip-10-0-10-76.ap-southeast-2.compute.internal -natsAddress ip-10-0-9-20.ap-southeast-2.compute.internal -natsPort 5533 -configurationType Oracle -helperProcessKey oracle:3oychmd4s3l5
rdsdb     8683  6017  0 Aug10 ?        00:02:26 /rdsdbdata/dbvisit/standbymp/oracle/dbvctl                                -d RDSCDB -D run --mode GUI
rdsdb    23277     1  0 Aug09 ?        00:00:20 /rdsdbdata/dbvisit/standbymp/bin/dbvagentmanager service run
rdsdb    28903 20764  0 05:44 pts/0    00:00:00 grep --color=auto dbv
rdsdb    32391  6017  0 04:53 ?        00:00:01 /rdsdbdata/dbvisit/standbymp/oracle/dbvctl                                -d RDSCDB --listener start --mode GUI

...

[ssm-user@ip-10-0-9-20 bin]$ ps -ef |grep dbv
rdsdb      825     1  0 Aug09 ?        00:00:38 /rdsdbdata/dbvisit/standbymp/bin/dbvagentmanager service run
rdsdb     1154     1  0 Aug09 ?        00:01:03 /rdsdbdata/dbvisit/standbymp/bin/dbvcontrol service run
rdsdb     8604   825  0 Aug09 ?        00:00:17 /rdsdbdata/dbvisit/standbymp/bin/dbvhelper -agentManagerId nm6clvbv4psa -directorId 3rxxfok6zctlm -hostAddress ip-10-0-9-20.ap-southeast-2.compute.internal -natsAddress ip-10-0-9-20.ap-southeast-2.compute.internal -natsPort 5533 -configurationType Oracle -helperProcessKey oracle:nm6clvbv4psa
ssm-user 10471  8101  0 05:45 pts/0    00:00:00 grep --color=auto dbv
rdsdb    27450  8604  0 05:32 ?        00:00:01 /rdsdbdata/dbvisit/standbymp/oracle/dbvctl                                -d RDSCDB --listener start --mode GUI
[ssm-user@ip-10-0-9-20 bin]$

1. Access the GUI directly from the public IPAddress of the standby server.

2. Before creating the standby below init parameters were reset as these parameters belong to Enterprise edition and not standard edition. I also removed these parameters on the primary as well.

db_block_checking
dg_broker_config_file1
dg_broker_config_file2

Also, for primary change the archivelog destination from log_archive_dest_1 to db_recovery_file_dest .

The DR database creation completed successfully.

Image Removed

3. Create the standby database from the StandbyMP control center. For detailed create standby database documentation click here

...

Performing a Test Graceful Switchover.

Before running graceful switchover, the automation has to be paused on both primary and standby for required time. The automation must be paused to ensure that the databases are not restarted automatically by AWS when performing switchover. Ensure automations are paused before performing any database activity that involves restarting of the databases.

...