...
This example will only show using the Central Console. It is possible to create the standby database either via the Command Line Interface (CLI) using the command: ./dbvctl -d <DDC> --csd in this example: "./dbvctl -d SOLO --csd"
To use the Central Console, navigate to the Central Console page and follow the steps as outlined below:
6.1 Start CSD process
Step 1: Navigate to the Create Standby Database (CSD) Menu
...
Step 2.1: Select the DDC, Create New Database option and update the Database SPFILE parameters to match the Standby server configuration. Make sure you review the locations of the datafiles, redo logs and spfile.
In this example, the primary and standby systems match exactly from a storage point of view (same disk groups etc) so we do not have to change any parameters.
...
Step 2.23: Review Temporary Backup Locations - Make sure that this location has sufficient space for a full RMAN compressed backup of the database. In this example /usr/tmp has sufficient space on both the primary and standby.
...
...
A job will appear in the taskbar, wait until it completes:
...
6.1 Send logs from Primary to Standby
Once CSD process is completed, verify archivelogs can be successfully sent and applied. Navigate to Database actions, click on send log button
...
Apply Archive logs to Standby database
...
7. Summary
Standby cluster now hosts SEHA standby database
...
which is also registered within OCR. you can check by executing the command below:
| Code Block |
|---|
$ srvctl config database -d SOLO
Database unique name: SOLO
Database name:
Oracle home: /u02/app/oracle/product/21.0.0/dbhome_1
Oracle user: oracle
Spfile: +DATA/SOLO/parameterfile/spfilesolo.ora
Password file: +DATA/SOLO/password/orapwSOLO
Domain:
Start options: mount
Stop options: abort
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Disk Groups: DATA,RECO
Mount point paths: /u02
Services:
Type: SINGLE
OSDBA group: dba
OSOPER group: oper
Database instance: SOLO
Configured nodes: czrlin0222,czrlin0223
CSS critical: no
CPU count: 0
Memory target: 0
Maximum memory: 0
Default network number for database services:
Database is administrator managed |
“Configured nodes” attribute needs to contain two cluster nodes otehrwise the database isn’t SEHA enabled. “Start options” and “Stop options” are always different for primary and standby database. “Database role” is always PRIMARY for primary and standby database.
You’re able to failover primary or standby SEHA database by running srvctl relocate database -d SOLO -node <nodename>
There’s no dependency between Dbvisit VIP and SEHA database, so if you manually relocate SEHA database, you also have to manually relocate Dbvisit VIP: crsctl relocate resource dbvisit-vip2223
In case when node where SEHA database and Dbvisit VIP run wil fail, gets rebooted, SEHA database as well as Dbvisit VIP will get failed over to the second node automatically
This guide doesn’t include integrating dbvctl daemon process for automatic log shipping and automatic log apply as cluster resource. If you wish, you can create action script for dbvctl daemon. In case you create dbvctl daemon as cluster resource you must not use Dbvisit CLI or GUI to control the daemon.