...
| Code Block |
|---|
[oracle@dbvel81 oracle]$ ./dbvctl -d TEST01 -o switchover
=============================================================
Dbvisit Standby Database Technology (11.3.0) (pid 50249)
dbvctl started on dbvel81: Wed Apr 12 19:03:53 2023
=============================================================
>>> Starting Switchover between dbvel81 and dbvel82
Running pre-checks ... done
=>Enter Custom User Script to run after Switchover is complete on dbvel81
(leave blank for no script): []: /home/oracle/scripts/switchover.sh
=>Enter Custom User Script to run after Switchover is complete on dbvel82
(leave blank for no script): []: /home/oracle/scripts/switchover.sh
=>Do you want to proceed with Graceful Switchover? [no]: yes
Your input: 1
Is this correct? <Yes/No> [Yes]:
Pre processing ... done
Processing primary ... done
Processing standby ... done
Converting standby ... done
Converting primary ... done
Completing ... done
Synchronizing ... done
Post processing ... done
>>> Graceful switchover completed.
Primary Database Server: dbvel82
Standby Database Server: dbvel81
>>> Dbvisit Standby can be run as per normal:
dbvctl -d TEST01
As part of the Switchover process, the primary and standby controlfiles have been exchanged.Unless you are using RMAN catalog database, you may need to cross-check all backups and review RMAN settings using the SHOW ALL command on the new Primary/Standby databases. Confirm the path set for the SNAPSHOT CONTROLFILE NAME TO setting is valid on both sides.
PID:50249
TRACE:50249_dbvctl_switchover_TEST01_202304121903.trc
=============================================================
dbvctl ended on dbvel81: Wed Apr 12 19:07:09 2023
============================================================= |
ASM → ASM
| Code Block |
|---|
[oracle@kiwi701 oracle]$ ./dbvctl -d TEST01 -o switchover
=============================================================
Dbvisit Standby Database Technology (11.3.0) (pid 83016)
dbvctl started on kiwi701: Fri Apr 28 00:21:28 2023
=============================================================
>>> Starting Switchover between kiwi701 and kiwi702
Running pre-checks ... done
=>Enter Custom User Script to run after Switchover is complete on kiwi701
(leave blank for no script): []:
=>Enter Custom User Script to run after Switchover is complete on kiwi702
(leave blank for no script): []:
=>Do you want to proceed with Graceful Switchover? [no]: yes
Your input: 1
Is this correct? <Yes/No> [Yes]:
Pre processing ... done
Processing primary ... done
Processing standby ... done
Converting standby ... done
Converting primary ... done
Completing ... done
Synchronizing ... done
Post processing ... done
>>> Graceful switchover completed.
Primary Database Server: kiwi702
Standby Database Server: kiwi701
>>> Dbvisit Standby can be run as per normal:
dbvctl -d TEST01
As part of the Switchover process, the primary and standby controlfiles have been exchanged.Unless you are using RMAN catalog database, you may need to cross-check all backups and review RMAN settings using the SHOW ALL command on the new Primary/Standby databases. Confirm the path set for the SNAPSHOT CONTROLFILE NAME TO setting is valid on both sides.
PID:83016
TRACE:83016_dbvctl_switchover_TEST01_202304280021.trc
=============================================================
dbvctl ended on kiwi701: Fri Apr 28 00:28:30 2023
============================================================= |
5. DR Testing
| Code Block |
|---|
[oracle@dbvel82 oracle]$ ./dbvctl -d TEST01 -o dr_test
=============================================================
Dbvisit Standby Database Technology (11.3.0) (pid 41621)
dbvctl started on dbvel82: Wed Apr 12 19:30:37 2023
=============================================================
>>> Running pre-checks please wait... done
-------------------------------------------------------------------------------
=>Do you want to backup the standby database prior to activation? [yes]:
Your input: 1
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
=>Specify backup type: 1 for image copy, 2 for backupset [1]: 2
Your input: 2
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
=>Specify backup location: []: /ust/tmp
Your input: /ust/tmp
Is this correct? <Yes/No> [Yes]:
Directory /ust/tmp does not exist and cannot be created
Enter valid location
-------------------------------------------------------------------------------
=>Specify backup location: []: /usr/tmp
Your input: /usr/tmp
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
=>Specify backup format: [%U.bkp]:
Your input: %U.bkp
Is this correct? <Yes/No> [Yes]:
-------------------------------------------------------------------------------
=>Do you want to be prompted to confirm activation on successful completion of
the backup? [yes]:
Your input: 1
Is this correct? <Yes/No> [Yes]:
>>> Standby database size is 3.59GB. Backing up database might take some time.
>>> Backing up standby database... done
>>> Validating backup of the standby database... done
-------------------------------------------------------------------------------
Standby Backup summary
-------------------------------------------------------------------------------
tag DBV_TEST01_41621
location /usr/tmp
type backupset
db_unique_name TEST01
server dbvel82
resetlogs_id 1090236030
resetlogs_time 2021-12-02:11:20:30
created_on 2023-04-12 19:34:26
created_on_utc 2023-04-12 23:34:26
status VALID
Files:
DBV_TEST01_41621_0v1pee68_31_1_1.bkp
DBV_TEST01_41621_101pee7v_32_1_1.bkp
DBV_TEST01_41621_111pee8o_33_1_1.bkp
DBV_TEST01_41621_CONTROL.CTL
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
=>Do you want to proceed with activating the standby database? [no]: yes
Your input: 1
Is this correct? <Yes/No> [Yes]:
>>> Activating now...
>>> Activation complete. Please ensure a backup of this Database is made
>>> Old archives from before the activation should be removed to avoid mix-up between new
and old archive logs
>>> Process complete
=============================================================
dbvctl ended on dbvel82: Wed Apr 12 19:35:34 2023
============================================================= |
...
| Code Block |
|---|
[oracle@dbvel82 oracle]$ ./dbvctl -d TEST01 -o reinstate ============================================================= Dbvisit Standby Database Technology (11.3.0) (pid 42544) dbvctl started on dbvel82: Wed Apr 12 19:39:15 2023 ============================================================= >>> Running pre-checks please wait... >>> Validating backup of the standby database... done done ------------------------------------------------------------------------------- Standby Backup summary ------------------------------------------------------------------------------- tag DBV_TEST01_41621 location /usr/tmp type backupset db_unique_name TEST01 server dbvel82 resetlogs_id 1090236030 resetlogs_time 2021-12-02:11:20:30 created_on 2023-04-12 19:34:26 created_on_utc 2023-04-12 23:34:26 status VALID Files: DBV_TEST01_41621_0v1pee68_31_1_1.bkp DBV_TEST01_41621_101pee7v_32_1_1.bkp DBV_TEST01_41621_111pee8o_33_1_1.bkp DBV_TEST01_41621_CONTROL.CTL ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- >>> Reinstating standby will result in permanent removal of all current database files. =>Proceed with reinstating? [no]: yes Your input: 1 Is this correct? <Yes/No> [Yes]: >>> Shutting down the database... done >>> Removing database files... done >>> Restoring standby control file... done >>> Starting standby database... done >>> Restoring standby database... done Standby database reinstated. ============================================================= dbvctl ended on dbvel82: Wed Apr 12 19:42:01 2023 ============================================================= |
...