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 dbvcontrol dashboard.

1. Removing DDC file From GUI

You can skip this step if the DDC you’re trying to import is not in your GUI dashboard.

Before any import can happen, old DDC file must be removed first. Removal of configuration from dashboard can be done by “Remove Configuration” from the ACTIONS pane:

Open

The DDC file on primary and standby server will be automatically backed up before deletion if dbvagentmanager is reachable.

2. 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 isn’t relevant for import).

Default location of Dbvisit StandbyMP version 12 DDC files is on Linux:

On Windows:

It is possible that this directory contains DDC file backups, which are done automatically during various actions (for example removal of DDC file in GUI will automatically create a backup file):

Before running import, make sure to have the file you want to import on primary server with expected name. If you want to import any older backup version of DDC file, rename it back to format dbv_<DDC>.env (no further extension after .env) For example:

Once done, you’re ready for GUI import. Start with creating new Oracle configuration:

Open

Choose primary server:

If DDC file is correctly recognized, you will see an option to import DDC file:

Successful import is recognized by Primary Database having ONLINE status and standby database having RECOVERING status.

3. Importing pre-version 12 DDC file

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.

Default location of DDC file is following in version 11:

In versions 9 and 10:

3.1 Pre-checks

In order to successfully import DDC file following conditions must be fulfilled:

• 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

Server Roles Check

We need to find out hostnames used by the DDC file. This can be checked by running following command:

SOURCE=primary server, DESTINATION=standby server

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 the DDC file to force the match.

If server roles are correct, proceed further.

Dbvagentmanager configuration check

Hostnames in the DDC file must match the installed dbvagenmanager configuration on primary and standby:

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.

Old associated files check

• Directory /usr/dbvisit/standbymp/oracle/conf must not contain old DDC file:

• Directory /usr/dbvisit/standbymp/oracle/conf must not contain old DDC sqlite repository either. The filename or repository is <lowercase db_name>.db:

• Directory /usr/dbvisit/standbymp/oracle must not contain old hosts file. Name of hosts file can be read from DDC file:

3.2 Import DDC file into dashboard

After prechecks are successfully completed, we can import the DDC file into controlcenter. Copy the DDC file into DDC directory:

And use the GUI to import:

Choose primary server:

If DDC file is correctly recognized, you will see an option to import DDC file:

Successful import is recognized by Primary Database having ONLINE status and standby database having RECOVERING status.

3.3 License update

If you imported pre-version 12 DDC file, license will be unusable. This is indicated by a warning, like seen here:

The license needs to be updated as per:

4 Post-Import Checks

You should be able to directly enable / continue synchronization with automated standby update as described here:

Post Tasks - Automatic Standby Update (ASU)

5. Recreating DDC repository

The DDC is always accompanied by sqlite repository file which has format <db_name>.db, so for example:

this DDC sqlite repository is automatically created an maintained by dbvisit. Single DDC sqlite repository can be shared with more DDC files, if they share same primary database db_name parameter.

DDC sqlite repository is only relevant on primary server, on standbyserver its existence is unimportant.

In some cases it may be needed to manually recreate this file. For example due to corruption when disk gets full. In such case, do following:

A. Delete manually existing sqlite repository file on primary and standby server

B. Run following command on primary:

The command will automatically detect DDC file and provide you with possibility to install the repository from the scratch.

Check below example output and note that we selected “2” to create sqlite repository for existing DDC file.