| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Create Virtual Cloud Network
...
Review the information provided and confirm the VCN creation.
...
Create Database Systems
To create the database machines, press Top left menu, then Oracle Database and click on the Oracle Base Database Service.
...
There is nothing special in installing Dbvisit Multiplatform in OCI environment.
Install Control Center on the compute instance machine
Install Dbvisit Agent on both database machines
Use following document how to install Dbvisit Multiplatform: https://dbvisit.atlassian.net/wiki/spaces/DSMP/pages/3242000447/Installing+Standby+Multiplatform#Installing-Standby-Multiplatform-on-Unix
Create Standby Database using Dbvisit Multiplatform
You can follow this guide, how to create Standby database on Oracle OCI to OCI: https://dbvisit.atlassian.net/wiki/x/JQAJ2w First we need to create the DBVISIT_BASE directory on both machines:
| Code Block |
|---|
[root@machine1 ~]# mkdir /usr/dbvisit
[root@machine1 ~]# chown oracle:oinstall /usr/dbvisit |
Then download the latest release of Dbvisit Multiplatform and start the installation of the agents on both machines. As machine names, provide the service names defined in custom DNS setup (machineX.oci2oci.lab):
| Code Block |
|---|
[oracle@machine1 dbvisit]$ cd /usr/dbvisit/
[oracle@machine1 dbvisit]$ tar xzf standby-v11.7.1.tar.gz
[oracle@machine1 dbvisit]$ ./install-agent-v11.7.1
+----------------------------------------------------------------------+
| ____ _ _ _ __ __ ____ |
| / ___|| |_ __ _ _ __ __| | |__ _ _| \/ | _ \ |
| \___ \| __/ _' | '_ \ / _' | '_ \| | | | |\/| | |_) | |
| ___) | || (_| | | | | (_| | |_) | |_| | | | | __/ |
| |____/ \__\__,_|_| |_|\__,_|_.__/ \__, |_| |_|_| |
| Copyright 2024 |___/ By Dbvisit |
+----------------------------------------------------------------------+
Welcome to Dbvisit StandbyMP setup version v11.7.1.
? Please carefully read the end-user license agreement at https://dbvisit.com/eula. Do you agree to the terms of this agreement? Yes
? Which directory should the software be installed into? /usr/dbvisit
- - - You are now configuring the Dbvisit StandbyMP Agent - - -
The Agent will listen on the following discovered addresses:
- 127.0.0.1
- 10.0.0.202
- 192.168.16.18
? Agent File Transfer Port: 7890
? Fully Qualified Domain Name for this host: machine1.oci2oci.lab
? Fully Qualified Domain Name for the Control Center: machine2.oci2oci.lab
? Agent Communications Port: 5533
Each Dbvisit StandbyMP Agent and the Dbvisit StandbyMP Control Center must
be configured with the same passphrase. This is how we know that they are all
intended to be part of the same system. Please specify a strong passphrase - we
suggest at least 12 characters, containing at least 2 numbers and 2 symbols.
? Passphrase: *****
? Confirm Passphrase: *****
- - - Dbvisit StandbyMP Agent configuration finished - - -
- - - Ready to perform installation - - -
? Do you wish to proceed with the setup using the supplied configuration options? Proceed with setup
- - - Performing installation - - -
Copying software files to '/usr/dbvisit'...
Writing Agent configuration file '/usr/dbvisit/standbymp/conf/dbvagentmanager.ini'...
- - - File creation complete - - -
- - - Configuration Summary - - -
Install Directory: /usr/dbvisit
Fully Qualified Domain Name for this host: machine1.oci2oci.lab
Fully Qualified Domain Name for the Control Center: machine2.oci2oci.lab
Agent Communications Port: 5533
Agent File Transfer Port: 7890
- - - Installation Summary - - -
The following actions have been performed:
- Installed Dbvisit StandbyMP Agent software into: /usr/dbvisit/standbymp
- Agent settings are available in the configuration file: /usr/dbvisit/standbymp/conf/dbvagentmanager.ini
- Generated new security certificates in: /usr/dbvisit/standbymp/certificates
- - - INSTALLATION SUCCESSFUL - - -
To enable the installed Dbvisit StandbyMP components to run as system services, you will need to execute some commands as the "root" user in order to complete the setup.
To install the system service(s), you can run, substituting the name of the user to run as if it is different from the current user:
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service install --user oracle
To start the system service(s), you can run:
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service start
[oracle@machine1 dbvisit]$ sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service install --user oracle
[oracle@machine1 dbvisit]$ sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service start
[oracle@machine1 dbvisit]$ |
The dbvagentmanager needs to be installed on the standby machine too.
Next we need to install Dbvcontrol (GUI) on the standby machine:
| Code Block |
|---|
[oracle@machine2 ~]$ ./install-control-v11.7.1
+----------------------------------------------------------------------+
| ____ _ _ _ __ __ ____ |
| / ___|| |_ __ _ _ __ __| | |__ _ _| \/ | _ \ |
| \___ \| __/ _' | '_ \ / _' | '_ \| | | | |\/| | |_) | |
| ___) | || (_| | | | | (_| | |_) | |_| | | | | __/ |
| |____/ \__\__,_|_| |_|\__,_|_.__/ \__, |_| |_|_| |
| Copyright 2024 |___/ By Dbvisit |
+----------------------------------------------------------------------+
Welcome to Dbvisit StandbyMP setup version v11.7.1.
? Please carefully read the end-user license agreement at https://dbvisit.com/eula. Do you agree to the terms of this agreement? Yes
? Which directory should the software be installed into? /usr/dbvisit
- - - You are now configuring the Dbvisit StandbyMP Control Center - - -
The Control Center will listen on the following discovered addresses:
- 127.0.0.1
- 10.0.0.123
- 192.168.16.18
? Control Center Web Server Port: 4433
? Agent Communications Port: 5533
Each Dbvisit StandbyMP Agent and the Dbvisit StandbyMP Control Center must
be configured with the same passphrase. This is how we know that they are all
intended to be part of the same system. Please specify a strong passphrase - we
suggest at least 12 characters, containing at least 2 numbers and 2 symbols.
? Passphrase: *****
? Confirm Passphrase: *****
- - - Dbvisit StandbyMP Control Center configuration finished - - -
- - - Ready to perform installation - - -
? Do you wish to proceed with the setup using the supplied configuration options? Proceed with setup
- - - Performing installation - - -
Copying software files to '/usr/dbvisit'...
Writing Control Center configuration file '/usr/dbvisit/standbymp/conf/dbvcontrol.ini'...
- - - File creation complete - - -
- - - Configuration Summary - - -
Install Directory: /usr/dbvisit
Control Center Web Server Port: 4433
Agent Communications Port: 5533
- - - Installation Summary - - -
The following actions have been performed:
- Installed Dbvisit StandbyMP Control Center software into: /usr/dbvisit/standbymp
- Control Center settings are available in the configuration file: /usr/dbvisit/standbymp/conf/dbvcontrol.ini
- Generated new security certificates in: /usr/dbvisit/standbymp/certificates
- - - INSTALLATION SUCCESSFUL - - -
To enable the installed Dbvisit StandbyMP components to run as system services, you will need to execute some commands as the "root" user in order to complete the setup.
To install the system service(s), you can run, substituting the name of the user to run as if it is different from the current user:
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service install --user oracle
To start the system service(s), you can run:
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service start
[oracle@machine2 ~]$ sudo /usr/dbvisit/standbymp/bin/dbvcontrol service install --user oracle
[oracle@machine2 ~]$ sudo /usr/dbvisit/standbymp/bin/dbvcontrol service start
[oracle@machine2 ~]$ |
The password specified must match the password specified during the dbvagentmanager installation.
At this moment you should be able to access the GUI on port 4433. You need to open security list port to access the port directly or you can tunnel the port using ssh to connect to it:
Initial login and password are admin/admin. It is recommended to change it immediately once you log in.
...
Create Standby Database using Dbvisit Multiplatform
Dbvisit needs a /etc/oratab entry for ASM instance in order to correctly detect the ASM instance running on the machines. Add similar entry to this one, with correct grid ORACLE_HOME to /etc/oratab:
| Code Block |
|---|
# This file is used by ORACLE utilities. It is created by root.sh
# and updated by either Database Configuration Assistant while creating
# a database or ASM Configuration Assistant while creating ASM instance.
# A colon, ':', is used as the field terminator. A new line terminates
# the entry. Lines beginning with a pound sign, '#', are comments.
#
# Entries are of the form:
# $ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are the system identifier and home
# directory of the database respectively. The third field indicates
# to the dbstart utility that the database should , "Y", or should not,
# "N", be brought up at system boot time.
#
# Multiple entries with the same $ORACLE_SID are not allowed.
#
#
TEST01:/u01/app/oracle/product/19.0.0.0/dbhome_1:N
+ASM1:/u01/app/19.0.0.0/grid:N |
To create the standby Database, press New Configuration menu on the left and Start with Oracle:
As a primary host choose your primary machine (machine1.oci2oci.lab)
From the list of databases on the primary machine, choose the one, that is going to be the source database for standby:
Choose your standby machine as a target of the replication:
Then fill in following values:
Staging directory, where the archived logs will be stored before sending to standby side
Unique database name: It is the unique database name from the OCI GUI, of the standby database system:
Choose a Staging directory, where the archived logs will be stored on standby side
Check the switch, that the standby database will use ASM
Insert the name of the ASM instance on the standby side: +ASM1
Choose a Configuration name. Usually name of the database is a good choice: Eg. TEST01
Enter the Dbvisit license key
Press Create Configuration button
...
At this moment you have a configuration, that puts together information about machines and database involved in the standby database installation.
Before you can continue with standby database creation, you need to create directories, that will be used by Dbvisit to create and backup of the primary database. On both machines run following commands:
| Code Block |
|---|
[opc@machine1 u01]$ sudo mkdir /u01/dbvisit_backup
[opc@machine1 u01]$ sudo chown oracle:oinstall /u01/dbvisit_backup |
Now you need to Create Standby Database. Click on the Setup Now link:
...
After some short time of gathering system information you need to fill in following fields:
make sure, that the checkbox to register standby database as clusterware resource is set to No. See chapter: Register Standby Database with Clusterware for more information.
make sure, that the checkbox to send newly created archived logs from the beginning of the primary database backup are sent to standby side
make sure, that the checkbox that you want to send and apply backups one by one in “parallel”
Fill in /u01/dbvisit_backup to both Source and Target Temp location. This will be the location, where the backups will be stored
Press the Manage Oracle Parameters Button
Update all standby database spfile parameters, that differ from between both databases. Mainly “audit_file_dest” and “wallet_root”, that do not match the correct db_unique_name parameter
Make sure, that the checkbox Automated Standby Update is set to Yes
Disable observer for now, you can always enable it later after the Standby database is created
Press Create Standby Database button
...
After some time, the standby database gets created:
...
Register Standby Database to Oracle Clusterware
It is advised to create database clusterware resource to let it to start the database automatically.
| Code Block |
|---|
srvctl add database -db TEST01_492_IAD -dbname TEST01 -instance TEST01 -dbtype "SINGLE" -diskgroup "DATA,RECO" -domain "oci2oci.lab" -node "machine2" -oraclehome "/u01/app/oracle/product/19.0.0.0/dbhome_1" -pwfile "+DATA/TEST01_492_IAD/password/pwdtest01_492_iad.277.1172143349" -spfile "+DATA/TEST01_492_IAD/parameterfile/spfileTEST01.ora" -startoption "MOUNT" -stopoption "ABORT" |
| Info |
|---|
Dbvisit creates Clusterware resource withouth parameter -instance with the srvctl command. If it is not specified, Oracle by default fills the instance name by db_unique_name parameter without underscore, which leads to missmatch of instance name and Dbvisit database name parameters. |