| Table of Contents |
|---|
1. Introduction
In this This section , we will cover how to deploy deploying Dbvisit Standby on an Oracle Standard Edition High Availability (SEHA) Windows cluster. SEHA is a feature replacing RAC, which is no longer available on in Standard Edition, starting with the 19c version.
| Note |
|---|
SEHA feature is available only on version 19.7 and onwards. Note that shared ACFS volume is required for Dbvisit installation. ACFS on Windows is deprecated for 19c and de-supported for all further releases by Oracle. In other words the only supported Oracle version from Dbvisit for SEHA configuration is 19c. |
...
Dbvisit Standby MP handles Oracle SEHA deployment similar similarly to Oracle RAC Cluster, with a few differences. There are two types of possible SEHA cluster configurations:
A. One or more Oracle database instances are running on one of the SEHA cluster nodes while the other node hosts 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.
...
This includes configurations where, for example, Oracle database instance instances A and B run on SEHA node 1 and database instance C runs on node 2. Such deployment is Dbvisit Standby currently NOT supported by Dbvisit Standbydoes NOT support such Deployments. Dbvisit Standby can be active only on one of the SEHA cluster nodes, not on both.
...
For deployment to Oracle RAC clusters, follow the same steps as mentioned below. There is only a cosmetic difference when creating a DDC configuration in the GUI at the end of the process.
Make sure that you’re running the supported RAC version as per:
From 19c onwards, RAC is an Enterprise Edition (EE) option only and is not certified with Dbvisit Standby, please contact . Don't hesitate to get in touch with Dbvisit Support if you wish to deploy Dbvisit to such an RAC environment.
1.3 Prerequisites
To deploy Dbvisit Standby on the SEHA cluster, the following prerequisites are needed:
New A new dedicated IP address and hostname for the new cluster VIP address are needed. This VIP address will be different from existing cluster VIP addresses. Our suggestion is to use hostname such as dbvisit-vip1 for example.
Shared storage between both primary cluster nodes with minimum 15GB free space. Such shared storage can be only provided by ACFS (no support for other methods)
...
| Code Block |
|---|
C:\Users\Administrator>acfsutil info storage
Diskgroup Consumer Space Size With Mirroring Usable Free %Free Path
ACFS 19.65 19.65 0.54 2%
DBVISIT 19.00 19.00 18.22 95% C:\dbvisit
CRS 4.99 4.99 4.64 92%
DATA 39.29 39.29 39.18 99%
FRA 19.65 19.65 17.88 91%
----
unit of measurement: GB |
Make sure the Oracle Grid Infrastructure is deployed as per Oracle documentation. The group membership for oracle and grid users needs to be correct. Dbvisit supports cluster role separation (oracle and grid user) as well as simple configuration (oracle user only)
Verify that the primary oracle database is SEHA enabled:
| Code Block |
|---|
C:\Users\Administrator>srvctl config database -d TEST01 Database unique name: TEST01 Database name: Oracle home: C:\app\oracle\product\19.0.0.0\dbhome_1 Oracle user: dbvisit\oracle ... Configured nodes: w19ora19seha3,w19ora19seha4 |
In srvctl config output, "Configured nodes" needs to contain TWO nodes. If you see only one node, the database does not have SEHA feature enabled
On both SEHA nodes, check that the Windows Registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\KEY_OraDB*Home*has a string value forORACLE_SID.
...
Before starting with Dbvisit Installation, we need to create a dedicated VIP address mentioned in the "1.3 Prerequisites". In our example, the pre-allocated VIP for our SEHA cluster is "172.16.17.253," and we decided to assign the DNS name "dbvisit-vip34". To create a new VIP address, you need to execute:
| Code Block |
|---|
C:\Users\Administrator>appvipcfg create -network=1 -ip=192.168.18.253 -vipname=dbvisit-vip34 -user=dbvisit\oracle Using configuration parameter file: C:\app\grid\product\19.0.0.0\gridhome_1\crs\install\crsconfig_params The log of current session can be found at: C:\app\orabase\crsdata\w19ora19seha3\scripts\appvipcfg.log |
...
| Note |
|---|
Before starting installation make sure to provision shared ACFS volume to your SEHA cluster. The size needs to be at least 15GB. In this example our shared volume is created as C:\dbvisit |
In this This section we will highlight only the most important and SEHA-related aspects of Dbvisit Installation. For a complete guide please refer to:
Installing Standby Multiplatform
We’ll be aiming for the Dbvisit configuration as follows:
Nodes | Associated VIP (active only on one SEHA node) | Installed Dbvisit component |
|---|---|---|
w19ora19seha3, w19ora19seha4 | dbvisit-vip34 | Dbvagentmanager |
w22ora19seha1, w22ora19seha2 | dbvisit-vip12 | Dbvagentmanager, Dbvcontrol |
We will first start on the primary SEHA cluster. We need first to create directory which will contain Dbvisit installation DBVISIT_BASE:
...
Continue by starting the dbvagentmanager installer and specifying this directory as DBVISIT_BASE (installation file agent-v11.6.0.msi was downloadded downloaded to C:\dbvisit\sw):
| Code Block |
|---|
C:\Users\Administrator>msiexec /i C:\dbvisit\sw\agent-v11.6.0.msi |
...
go Go for next to set passphrase:
...
Once installation is completed, edit the dbvagentmanager configruation configuration file and set FileTransferListenAddress to DBVISIT-VIP34.DBVISIT.CZ and save the file
...
To enable SEHA failover for dbvagentmanager, we recommend to integrate integrating them into Oracle Grid by using an action script. Here is a single action script for dbvagentmanager and for dbvcontrol:
| View file | ||
|---|---|---|
|
Dbvcontrol will not be installed on the primary cluster, but the same action script will be used for dbvagentmanager and dbvcontrol on the standby cluster.
Upload the script to directory C:\dbvisit\app\bin
...
You need to check that the script is working properly. For checking, run on 1st SEHA node:
| Code Block |
|---|
cd C:\dbvisit\app\bin
C:\dbvisit\app\bin>dbvcrs.bat stop dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat check dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat start dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat check dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat clean dbvagentmanager
C:\dbvisit\app\bin>dbvcrs start dbvagentmanager
Starting service dbvagentmanager
The Dbvisit StandbyMP Agent service is starting.
The Dbvisit StandbyMP Agent service was started successfully.
Checking service dbvagentmanager
SERVICE_NAME: dbvagentmanager
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0 |
You need to receive the correct output for each command (service is stopped, started, etc ..)
2.4 Creating dbvagentmanager service on the 2nd SEHA node
On the 2nd SEHA node, we need to manually create the Windows service manually, set it’s its startup mode to manual, and change the password (use an actual password):
...
2.5 Creating dbvagentmanager Cluster Resource
Make sure the dbvagentmanager service is stopped on both SEHA nodes. Now we can finally create the dbvagentmanager action script and test VIP + dbvagentmanager relocation:
| Code Block |
|---|
crsctl add resource dbvagentmanager -type generic_application -attr "START_PROGRAM='/dbvisit/app/bin/dbvcrs.bat start dbvagentmanager',STOP_PROGRAM='/dbvisit/app/bin/dbvcrs.bat stop dbvagentmanager',CHECK_PROGRAMS='/dbvisit/app/bin/dbvcrs.bat check dbvagentmanager',CLEAN_PROGRAM='/dbvisit/app/bin/dbvcrs.bat clean dbvagentmanager',CHECK_INTERVAL=10,START_DEPENDENCIES='hard(dbvisit-vip34) pullup(dbvisit-vip34) attraction(dbvisit-vip34)',STOP_DEPENDENCIES='hard(dbvisit-vip34)',PLACEMENT='favored',HOSTING_MEMBERS='w19ora19seha3 w19ora19seha4',ACL='owner:dbvisit\oracle:rwx,pgrp::r-x,other::r--'" |
try Try to startup start dbvagentmanager via crsctl and check the service status afterwards afterward (must be RUNNING):
| Code Block |
|---|
C:\dbvisit\app\bin>crsctl start res dbvagentmanager
CRS-2672: Attempting to start 'dbvagentmanager' on 'w19ora19seha3'
CRS-2676: Start of 'dbvagentmanager' on 'w19ora19seha4' succeeded
C:\dbvisit\app\bin>sc query dbvagentmanager
SERVICE_NAME: dbvagentmanager
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0 |
...
| Code Block |
|---|
C:\dbvisit\app\bin>crsctl relocate resource dbvisit-vip34 -f CRS-2673: Attempting to stop 'dbvagentmanager' on 'w19ora19seha3' CRS-2677: Stop of 'dbvagentmanager' on 'w19ora19seha3' succeeded CRS-2673: Attempting to stop 'dbvisit-vip34' on 'w19ora19seha3' CRS-2677: Stop of 'dbvisit-vip34' on 'w19ora19seha3' succeeded CRS-2672: Attempting to start 'dbvisit-vip34' on 'w19ora19seha4' CRS-2676: Start of 'dbvisit-vip34' on 'w19ora19seha4' succeeded CRS-2672: Attempting to start 'dbvagentmanager' on 'w19ora19seha4' CRS-2676: Start of 'dbvagentmanager' on 'w19ora19seha4' succeeded C:\dbvisit\app\bin>crsctl relocate resource dbvisit-vip34 -f CRS-2673: Attempting to stop 'dbvagentmanager' on 'w19ora19seha4' CRS-2677: Stop of 'dbvagentmanager' on 'w19ora19seha4' succeeded CRS-2673: Attempting to stop 'dbvisit-vip34' on 'w19ora19seha4' CRS-2677: Stop of 'dbvisit-vip34' on 'w19ora19seha4' succeeded CRS-2672: Attempting to start 'dbvisit-vip34' on 'w19ora19seha3' CRS-2676: Start of 'dbvisit-vip34' on 'w19ora19seha3' succeeded CRS-2672: Attempting to start 'dbvagentmanager' on 'w19ora19seha3' CRS-2676: Start of 'dbvagentmanager' on 'w19ora19seha3' succeeded |
After each relocation of the VIP address, check that the dbvagentmanager service is running on that respective node and node and that it’s stopped on the other node.
This step concludes the installation and setup of Dbvisit on the primary SEHA cluster
3. Dbvisit Software Setup on Standby Cluster
3.1 Creating Dbvisit Dedicated VIP Address
Same as on the primary SEHA cluster, Before starting with Dbvisit Installation, we need to create a dedicated VIP address mentioned in the "1.3 Prerequisites". Our pre-allocated VIP for our standby SEHA cluster is "172.16.17.254" and we decided to assign DNS name "dbvisit-vip12". To create a new VIP address, you need to execute:
| Code Block | ||
|---|---|---|
| ||
C:\Users\Administrator>appvipcfg create -network=1 -ip=192.168.18.254 -vipname=dbvisit-vip12 -user=dbvisit\oracle Using configuration parameter file: C:\app\grid\product\19.3.0.0\gridhome_1\crs\install\crsconfig_params The log of current session can be found at: C:\app\orabase\crsdata\w22ora19seha1\scripts\appvipcfg.log |
...
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 dbvamanagerdbvagentmanager. We need first to create the directory which will contain Dbvisit installation DBVISIT_BASE:
...
go for next to set passphrase:
...
Use the same passphrase as on the primary cluster, then on the next page make sure to install in C:\dbvisit\app:
...
| Code Block |
|---|
C:\Users\Administrator>net stop dbvagentmanager && net start dbvagentmanager The Dbvisit StandbyMP Agent service is stopping. The Dbvisit StandbyMP Agent service was stopped successfully. The Dbvisit StandbyMP Agent service is starting. The Dbvisit StandbyMP Agent service was started successfully. |
set Set it to manual start mode:
| Code Block |
|---|
C:\Users\Administrator>sc config dbvagentmanager start=demand [SC] ChangeServiceConfig SUCCESS |
...
3.3 Installing Dbvcontrol on Standby Cluster
You can skip this chapter section if you will deploy the controlcenter elsewhere.
Start dbvcontrol installation:
...
There’s nothing to change throughout the whole installer except the passphrase - use the same passphrase as before:
...
And make sure to install it in C:\dbvisit\app:
...
Once installation is completed, edit the dbvagentmanager configruation file and set FileTransferListenAddress to DBVISIT-VIP12.DBVISIT.CZ and save the file
...
3.4 Creating Cluster Action Script for dbvagentmanager and dbvcontrol
We will use the exactly the same action script as on the primary cluster. Download from sectio 2.3 Creating Cluster Action script for dbvagentmanager and copy it into C:\dbvisit\app\bin on standby cluster.
...
You need to check that the script is working properly. For checking, run on 1st SEHA node:
| Code Block |
|---|
cd C:\dbvisit\app\bin
C:\dbvisit\app\bin>dbvcrs.bat stop dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat check dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat start dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat check dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat clean dbvagentmanager
C:\dbvisit\app\bin>dbvcrs start dbvagentmanager
Starting service dbvagentmanager
The Dbvisit StandbyMP Agent service is starting.
The Dbvisit StandbyMP Agent service was started successfully.
Checking service dbvagentmanager
SERVICE_NAME: dbvagentmanager
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0 |
You need to receive the correct output for each command (service is stopped, started, etc ..) - do the same for dbvcontrol
...
On 2nd SEHA node, we need to manually create the Windows service manually, set it’s its startup mode to manual, and change the password (use an actual password):
...
If you installed dbvcontrol as well, continue to perform the same steps for dbvcontrol:
...
3.6 Creating dbvagentmanager and dbvcontrol Cluster Resources
Skip the dbvcontrol part is if dbvcontrol isn’t installed. Make sure the dbvagentmanager service is stopped on both SEHA nodes. Now we can finally create the dbvagentmanager action script and test VIP + dbvagentmanager relocation:
| Code Block |
|---|
crsctl add resource dbvagentmanager -type generic_application -attr "START_PROGRAM='/dbvisit/app/bin/dbvcrs.bat start dbvagentmanager',STOP_PROGRAM='/dbvisit/app/bin/dbvcrs.bat stop dbvagentmanager',CHECK_PROGRAMS='/dbvisit/app/bin/dbvcrs.bat check dbvagentmanager',CLEAN_PROGRAM='/dbvisit/app/bin/dbvcrs.bat clean dbvagentmanager',CHECK_INTERVAL=10,START_DEPENDENCIES='hard(dbvisit-vip12) pullup(dbvisit-vip12) attraction(dbvisit-vip12)',STOP_DEPENDENCIES='hard(dbvisit-vip12)',PLACEMENT='favored',HOSTING_MEMBERS='w22ora19seha1 w22ora19seha2',ACL='owner:dbvisit\oracle:rwx,pgrp::r-x,other::r--'" |
try Try to startup dbvagentmanager via crsctl and verify the service status (must be RUNNING):
...
| Code Block |
|---|
crsctl add resource dbvcontrol -type generic_application -attr "START_PROGRAM='/dbvisit/app/bin/dbvcrs.bat start dbvcontrol',STOP_PROGRAM='/dbvisit/app/bin/dbvcrs.bat stop dbvcontrol',CHECK_PROGRAMS='/dbvisit/app/bin/dbvcrs.bat check dbvcontrol',CLEAN_PROGRAM='/dbvisit/app/bin/dbvcrs.bat clean dbvcontrol',CHECK_INTERVAL=10,START_DEPENDENCIES='hard(dbvisit-vip12) pullup(dbvisit-vip12) attraction(dbvisit-vip12)',STOP_DEPENDENCIES='hard(dbvisit-vip12)',PLACEMENT='favored',HOSTING_MEMBERS='w22ora19seha1 w22ora19seha2',ACL='owner:dbvisit\oracle:rwx,pgrp::r-x,other::r--'" |
try Try to startup dbvcontrol via crsctl and verify the service status (must be RUNNING):
...
| Code Block |
|---|
C:\dbvisit\app\bin>crsctl relocate resource dbvisit-vip12 -f CRS-2673: Attempting to stop 'dbvagentmanager' on 'w22ora19seha1' CRS-2673: Attempting to stop 'dbvcontrol' on 'w22ora19seha1' CRS-2677: Stop of 'dbvcontrol' on 'w22ora19seha1' succeeded CRS-2677: Stop of 'dbvagentmanager' on 'w22ora19seha1' succeeded CRS-2673: Attempting to stop 'dbvisit-vip12' on 'w22ora19seha1' CRS-2677: Stop of 'dbvisit-vip12' on 'w22ora19seha1' succeeded CRS-2672: Attempting to start 'dbvisit-vip12' on 'w22ora19seha2' CRS-2676: Start of 'dbvisit-vip12' on 'w22ora19seha2' succeeded CRS-2672: Attempting to start 'dbvagentmanager' on 'w22ora19seha2' CRS-2676: Start of 'dbvagentmanager' on 'w22ora19seha2' succeeded CRS-2672: Attempting to start 'dbvcontrol' on 'w22ora19seha2' CRS-2676: Start of 'dbvcontrol' on 'w22ora19seha2' succeeded C:\dbvisit\app\bin>crsctl relocate resource dbvisit-vip12 -f CRS-2673: Attempting to stop 'dbvagentmanager' on 'w22ora19seha2' CRS-2673: Attempting to stop 'dbvcontrol' on 'w22ora19seha2' CRS-2677: Stop of 'dbvagentmanager' on 'w22ora19seha2' succeeded CRS-2677: Stop of 'dbvcontrol' on 'w22ora19seha2' succeeded CRS-2673: Attempting to stop 'dbvisit-vip12' on 'w22ora19seha2' CRS-2677: Stop of 'dbvisit-vip12' on 'w22ora19seha2' succeeded CRS-2672: Attempting to start 'dbvisit-vip12' on 'w22ora19seha1' CRS-2676: Start of 'dbvisit-vip12' on 'w22ora19seha1' succeeded CRS-2672: Attempting to start 'dbvagentmanager' on 'w22ora19seha1' CRS-2676: Start of 'dbvagentmanager' on 'w22ora19seha1' succeeded CRS-2672: Attempting to start 'dbvcontrol' on 'w22ora19seha1' CRS-2676: Start of 'dbvcontrol' on 'w22ora19seha1' succeeded |
After each relocation of the VIP address, check that dbvagentmanager and dbvcontrol service is running on that respective node and that it’s stopped on the other node.
...
In our case, dbvagentmanager is run by domain account dbvisit\oracle, so we need to add him it to two Registry Keys: “Oracle” (HKEY_LOCAL_MACHINE\SOFTWARE\Oracle) and “KEY_OraDB19Home1” (HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\KEY_OraDB19Home1). The privileges needed are “Full Control”
Make sure the key “KEY_OraDB19Home1” contains value “ORACLE_SID”
...
Once done, proceed with standby database creationthe next steps.
To start, logon to the GUI. Below are the screenshots showing you how you can use them to create the New Oracle database configuration
...
Step 1: Open Main Screen, navigate to New Configuration, click (1)
...
Step 2: Choose (1) the Primary host dbvisit-vip34 from the discovered host list:
...
Step 4: Next step is to select the Standby Host, ; in this example DBVISIT-VIP12
...
Once the Primary and Standby hosts are selected, you will be presented with the SEHA cluster(s) details. make sure Ensure to correctly enter all SEHA cluster details (nodenames and ASM instances).
...
Continue to fill in the required details. Make sure to correctly set ARCHSOURCE (1) and ARCHDEST (2) - they should ideally be ideally the same directory and exist on primary & standby.
...
Continue changing the rest of the details if needed. In our example, we left everything to the suggested values:
Standby Oracle SID
Oracle Database Home on the Standby server
DB Unique Name (db_unique_name) of the standby if required
Dbvisit Base location on the Standby server if different
Finalize by setting the DDC name, and license key and click on “Create Configuration”:
...
Once the configuration is created, you can create the SEHA standby database.
| Info |
|---|
To create standby database, Dbvisit uses RMAN compressed backup by default. On Windows this can mean significant time consumption. If you have enough disk space we recommend to disable the RMAN compression before proceeding as displayed on following picture: |
...
Standby Server dbvisit-vip23
Please refer to the below link for the pre-requisites requisite steps to be performed before switchover.
...
Standby cluster now hosts SEHA standby database, which is also registered within OCR. you You can check by executing the command below on the primary and standby cluster:
| Code Block |
|---|
C:\Users\Administrator>srvctl config database -d TEST01 Database unique name: TEST01 Database name: Oracle home: C:\app\oracle\product\19.0.0.0\dbhome_1 Oracle user: dbvisit\oracle Spfile: +DATA/TEST01/parameterfile/spfiletest01.ora Password file: +DATA/TEST01/password/PWDTEST01.ORA Domain: Start options: open Stop options: immediate Database role: PRIMARY Management policy: AUTOMATIC Server pools: Disk Groups: DATA,FRA Mount point paths: Services: Type: SINGLE Database instance: TEST01 Configured nodes: w19ora19seha3,w19ora19seha4 CSS critical: no CPU count: 0 Memory target: 0 Maximum memory: 0 Default network number for database services: Database is administrator managed |
“Configured nodes” The “Configured nodes” attribute needs to contain two cluster nodes otehrwise otherwise, the database isn’t SEHA enabled. “Start options” and “Stop options” are always different for primary and standby database. “Database role” databases. “Database role” is always PRIMARY for both primary and standby databasedatabases.
You’re able to failover primary or standby SEHA database by running srvctl relocate database -d TEST01 -node <nodename>
There’s no dependency between Dbvisit VIP and the SEHA database, so if you manually relocate SEHA database, you also have to manually relocate Dbvisit VIP: crsctl relocate resource dbvisit-vip12 -f
In case when the node where the SEHA database and Dbvisit VIP run wil will fail, gets rebooted, the SEHA database as well as Dbvisit VIP will get failed fail over to the second node automatically
...