...
| Info |
|---|
Now you have a chance to edit the standby database init parameters from in pfile stored in /u02/app/oracle/dbvisit_backup/initMEGA.ora - for example memory allocation, etc ... |
...
| Code Block |
|---|
... ... Starting recover at 29-AUG-23 using channel ORA_DISK_1 starting media recovery media recovery complete, elapsed time: 00:00:00 Finished recover at 29-AUG-23 RMAN> |
3. Standby database creation is now complete
RMAN has started the standby database in mount standby mode which is correct for Dbvisit Standby to continue.
...
3. Create corresponding configuration in dbvcontrol GUI
Now you can create the DDC file in the dbvcontrol GUI (in detail described in: Create Oracle Configuration ):
...
Once created, DDC in the dashboard will look like so:
...
4. Backup & send archivelog to verify that standby database can be correctly recovered.
We need to perform this via command line. On primary run:
...
| Code Block |
|---|
[oracle@czlin0212 oracle]$ /usr/dbvisit/standbymp/oracle/dbvctl -d MEGA ============================================================= Dbvisit Standby Database Technology (11.4.0) (pid 928715) dbvctl started on czlin0212: Tue Aug 29 13:09:45 2023 ============================================================= >>> Applying Log file(s) from czlin0211 to MEGA on czlin0212: thread 1 sequence 116 (1_116_1145654994.arc)... done thread 1 sequence 117 (1_117_1145654994.arc)... done Last applied log(s): thread 1 sequence 117 Next SCN required for recovery 135844738 generated at 2023-08-29:12:26:30 +02:00. Next required log thread 1 sequence 118 ============================================================= dbvctl ended on czlin0212: Tue Aug 29 13:09:48 2023 ============================================================= |
...
5. Final step is to enable the automated standby update.
On primary run:
| Code Block |
|---|
[oracle@czlin0211 oracle]$ /usr/dbvisit/standbymp/bin/dbvagentmanager auto-update modify --enable --set-interval-seconds 300 --noconfirm |
...