In this section, we will show you how to import or re-import existing Oracle DDC file into dbvcontrol dashboard. DDC file contains complete configuration for a pair of Primary and Standby Oracle database synchronization.
...
Note |
---|
DDC file contains all settings needed for Oracle Synchronization. When doing import, you must ensure that all settings stored inside the DDC file are correct (for example primary and standby server roles). Do not perform import if you’re not sure that all DDC file variables are correct. Instead, create DDC file from scratch instead. |
Table of Contents | ||
---|---|---|
|
...
If the server roles are NOT correct, we recommend to abort the import process and create new DDC from the scratch. Roles not being correct indicate mismatch between DDC and your environment and you can potentially introduce many errors or even endanger your production database. Do NOT manually edit SOURCE and DESTINATION in the DDC file to force the match.
If you’re confident that the DDC is correct and you only need to swap the roles (switch SOURCE and DESTINATION parameters) run following procedure command on primary server:
Code Block |
---|
/usr/dbvisit/standbymp/oracle/dbvctl -d SLASH -o update_ddc_file ============================================================= Dbvisit Standby Database Technology (12.1.0RC) (pid 2823091) dbvctl started on czlin0231: Mon Feb 24 14:20:01 2025 ============================================================= >>> Dbvisit Database configuration (DDC) file /usr/dbvisit/standbymp/oracle/conf/dbv_SLASH.env has been updated and variables have been reversed between primary and standby server SOURCE=czlin0232 DESTINATION=czlin0231 |
You will see and output with swapped hosts. This command can be run repeatedly.
Once server roles are correct, proceed further.
...
The license needs to be updated as per: <<TBD>>
4 Post-Import Checks
You should be able to directly enable / continue synchronization with automated standby update as described here:
...