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.
There are various situations when you can use this process such as when re-installing Dbvisit StandbyMP from the scratch or even manually importing older version DDC file after failed or incomplete upgrade. Oracle DDC file is standalone entity and can be used to quickly add existing standby database to you your dbvcontrol dashboard.
| Info |
|---|
There is no need to recreate standby database when importing DDC file (if the standby database is healthy). |
| 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 | ||
|---|---|---|
|
...
The DDC file on primary and standby server will be automatically backed up before deletion if dbvagentmanager is reachable. The backup is done by renaming the file it with date extension on primary and standby
| Info |
|---|
You will lose notification and observer configuration when you remove the configuration from the GUI |
2. Re-Importing version 12 DDC file
This is usually done when you want to restore older version of DDC file. It is also viable solution when encountering various issues: remove DDC file from dbvcontrol and import it back. The import always happens from primary server only (standby server or DDC file on standby isn’t relevant for import).
...
| Code Block |
|---|
/usr/dbvisit/standbymp/oracle/conf/dbv_SLASH.env |
...
| Info | ||
|---|---|---|
you need to be sure that the version of the DDC file you’re restoring doesn’t have significant differences - for example primary and standby server roles are the same in the DDC file as you would expect. You can easily swap the Primary and Standby server roles by running dbvctl command:
Note the last line tells you the actual server roles (SOURCE = primary server, DESTINATION = standby server) - this must be in line with what you expect. If not, run the command again |
Once you verify the primary and standby server roles are correct, you’re ready for GUI import. Start with creating new Oracle configuration:
...
| Info |
|---|
if you’re not successful with the import (or you see server roles incorrectly), try to perform all the steps in “3. Importing pre-version 12 DDC file” which include also precheck and cleanup |
...
steps in “3. Importing pre-version 12 DDC file” which include also precheck and cleanup |
3. Importing pre-version 12 DDC file or importing version 12 DDC file with detailed prechecks
We recommend to use this approach when:
you’re importing pre-v12 version DDC file
re-import of v12 DDC failed for any reason (prechecks specified here should help you to resolve the issue)
It is supported to import version 9,10 and 11 in Dbvisit StandbyMP version 12 GUI. The import of older version DDC file into version 12 GUI effectively means upgrading it. This is especially useful when upgrading from older Dbvisit versions by installing version 12 from the scratch.
...
The server roles must be correct
The hostnames specified in DDC file must match hostnames configured in primary and standby dbvagentmanager (case sensistive, domain sensitive)
There must be no old files accociated with the DDC file we intend to import inside Dbvisit base on primary and standby
A. Server Roles Check
| Info |
|---|
We assume that DDC file we want to import is for now placed in /tmp directory |
...
Once server roles are correct, proceed further.
B. Dbvagentmanager configuration check
...
The hostnames must be identical - FQDN matters and case matters as well. If you see any differences in letter case or domain, edit the DDC file to get the match. Don’t edit the dbvagentmanager.ini file.
C. Old associated files check
...
| Note |
|---|
If you’re in SEHA or RAC environment then it’s exactly the opposite: you MUST manually create the hosts file, if it’s not already existing. Create empty file as per HOSTNAME_CMD parameter and include following line: echo “hostname” Where hostname string is the value of SOURCE parameter found in your DDC file (typically dedicated Dbvisit VIP address). |
3.2 Import DDC file into dashboard
...