| Table of Contents | ||||
|---|---|---|---|---|
|
1. Introduction
In this section, we will cover how to deploy Dbvisit Standby on an Oracle Standard Edition High Availability (SEHA) cluster. SEHA is a feature replacing RAC which is no longer available on Standard Edition starting with 19c version.
...
Volume /dbvisit is not shared between both clusters, it's shared between two nodes on local cluster only (Volume is not shared between primary and standby).
1.1 Different types of Oracle SEHA configurations
Dbvisit Standby MP handles Oracle SEHA deployment similar to Oracle RAC Cluster with few differences. There are two types of possible SEHA cluster configurations:
A. One or more Oracle database instances running on one of the SEHA cluster node nodes while the other node hosts no are not running any database instances.
Such deployment is supported by Dbvisit Standby MP 11.1 and onwards. In this type of deployment Dbvisit uses cluster resources and shared storage to be able to failover to the other SEHA node.
B. Two or more Oracle database instances running on both SEHA cluster nodes.
This includes configurations where for example Oracle database instance A and B run on SEHA node 1 and database instance C runs on node 2.
...
Such deployment is
...
currently NOT supported by Dbvisit Standby. Dbvisit Standby can be active only on one of the SEHA cluster nodes, not on both.
| Info |
|---|
Currently, SEHA is supported only for Linux environments. |
1.2 Oracle RAC
For deployment to Oracle RAC clusters, follow the same steps as mentioned below. There is only cosmetic difference when creating DDC configuration in the GUI at the end of the process.
...
from From 19c onwards, RAC is Enterprise Edition (EE) option only and is not certified with Dbvisit Standby, please contact Dbvisit Support if you wish to deploy Dbvisit to such RAC environment.
1.3 Prerequisites
To deploy Dbvisit Standby on SEHA cluster following prerequisites are needed:
...
And on 2nd node, you need to have entry for +ASM2.
2. Dbvisit Software Setup on Primary Cluster
2.1 Creating Dbvisit Dedicated VIP Address
Before starting with Dbvisit Installation we need to create dedicated VIP address mentioned in the "1.2 Prerequisites". In our example the pre-allocated VIP for our SEHA cluster is "192.168.8.12" and we decided to assign DNS name "dbvisit-vip2178". To create new VIP address you need to execute as root user:
...
You should get connected to both nodes. Finish this preparation step by relocating the new VIP to the 1st SEHA cluster node.
2.2 Installing Dbvisit Software
| Note |
|---|
Before starting installation make sure to provision shared volume to your SEHA cluster (for example ACFS shared volume or NFS volume). The size needs to be at least 15GB. In this example our shared volume is provided by ACFS and is mounted on /dbvisit |
...
Do not create systemctl service. There’s no dbvcontrol component on this SEHA cluster - installation of the product on primary cluster is hence finished.
2.3 Creating Cluster Action script for dbvagentmanager
To enable easy SEHA failover for dbvagentmanager we recommend to integrate them into Oracle Grid by using action script. Here is single action script for dbvagentmanager and for dbvcontrol:
...
This step concludes the installation and setup of Dbvisit on primary SEHA cluster
3. Dbvisit Software Setup on Standby Cluster
3.1 Creating Dbvisit Dedicated VIP Address
Same as on primary SEHA cluster, before starting with Dbvisit Installation we need to create dedicated VIP address mentioned in the "1.2 Prerequisites". Our pre-allocated VIP for our styandby SEHA cluster is "192.168.8.13" and we decided to assign DNS name "dbvisit-vip2223". To create new VIP address you need to execute as root user:
...
You should get connected to both nodes. Finish this preparation step by relocating the new VIP to the 1st SEHA cluster node.
3.2 Installing Dbvisit Software
Installation of Dbvisit software on standby cluster is completely the same as on primary - the only difference is that we’ll install dbvcontrol component in addition to dbvamanager. First install dbvagentmanager:
...
Do not create systemctl service. We have installed both components on standby cluster, installation of the product is hence finished.
3.3 Creating Cluster Action scripts for dbvagentmanager and dbvcontrol
Upload the action script from primary cluster from to directory /dbvisit/app/standbymp/bin and set correct privileges:
...
This step concludes the installation and setup of Dbvisit on standby SEHA cluster
4. Creating Dbvisit Database Configuration (DDC) with CLI
Here is and example on how to create DDC file for SEHA configuration. In our sample test environment, we have primary database SOLO running on primary SEHA cluster czrlin0217 and czrlin0218 with database home /u02/app/oracle/product/21.0.0/dbhome_1.
...
| Info |
|---|
DDC file create on CLI must be imported in Control Center first before proceding with Standby Database Creation |
5. Creating Dbvisit Database Configuration (DDC) with GUI
| Info |
|---|
In our example we use Dbvcontrol Center on standby SEHA cluster czrlin0222 and czrlin0223. You can install Dbvcontrol Center there or on any other machine separated from SEHA clusters. |
...
| Info |
|---|
If wish to create standby database on ACFS storage, don’t fill in any ASM details, simply leave empty |
| Note |
|---|
Similar to Archsource: Archdest is Dbvisit archivelog directory which must be never set to any database-related directory (like FRA etc ..). This directory also must not contain any subdirectories, not even lost+found. On standby server this directory will contain all archivelogs. After database role change Archdest directory will become Archsource and vice versa. |
6. Setup Disaster Recovery Database
This example will only show using the Central Console. To use the Central Console, navigate to the Central Console page and follow the steps as outlined below:
6.1 Create SEHA DR database
Step 1: Navigate to the DASHBOARD and click on Set up now
...
Step 3: A job will appear in the taskbar, wait until it completes:
...
6. Perform Graceful Switchover
Primary Server: dbvisit-vip2178
...
3. Primary and Standby server roles are swapped
...
4. Switchback
...
7. Summary
Standby cluster now hosts SEHA standby database which is also registered within OCR. you can check by executing the command below:
...