7. Managing Configuration (DDC) Files
Please see also this section for additional information: Creating the DDC File
Dbvisit Standby allows you to create a DDC (Dbvisit Standby configuration file) for the following scenarios:
- Oracle single instance database as primary with a single instance database as a standby
- The primary and standby databases can use Filesystem based storage or ASM
- If ASM is to be used on the standby it must already be configured with the required disk groups
- Primary and Standby database systems should match - especially the Oracle Database software (Including patch levels)
- Mixing Database Editions are not supported. Both primary and standby must use the same Oracle Software version and Edition.
- Oracle Real Application Cluster (RAC) database as primary to a single instance standby database (with multiple threads but only one is used)
- Oracle Real Application Cluster (RAC) database as primary with an Oracle RAC database as a standby
- Important If using Oracle RAC configurations:
- The primary and standby configuration should match (Operating System, Clusterware - GI, and Database software)
- If the primary is a two-node cluster the standby Oracle RAC must also, be a two-node cluster
- All RAC nodes must be running at the time of running the Dbvisit Standby - Create Standby Database option
- Shared storage is recommended on each cluster to install and run Dbvisit Standby from
- A Virtual IP address and name is recommended for each cluster
- If the Standby Database is to be an Oracle RAC enabled cluster, the Oracle RAC cluster must already be configured with the required disk groups and storage available.
- If using Oracle RAC, it is recommended to have a shared storage location for the Dbvisit Standby installation as well as for the Dbvisit ARCSOURCE and ARCHDEST locations. These locations are used by Dbvisit and are not the same as the database archive destinations and should not be located inside the database archive log destination or fast/flash recovery area.
7.1. Creating a New DDC File - Single Instance to Single Instance
This section will describe the steps to create a new DDC file for a single instance primary and standby database.
Following these steps will create the DDC file after which you can edit and add additional parameters if required (Example adding email notification configuration).
Step 1: Select "Manage Configurations"
From the main screen, select the Manage Configurations option.
Step 2: Adding a new DDC by selecting the "+" or "New" green button as highlighted.
In this example, there is no DDCs configured. To start the creation of a new DDC select the "+" new option to start the process.
Step 3: Select the Source Host - the host that is running the database we want to create a standby database from.
As shown in the screen below, we select from the dropdown option  the host "dbv1" which in this case have already been added as a new host.
This host must already have the Dbvisit Standby Agent (dbvagent) installed and running. See the "Managed Hosts" section for more detail.
The License will be displayed, review the license as shown in  below and if in agreement, select "ACCEPT" to continue.
Step 4: Select the Database for which you want to create a standby database.
Databases running on the host selected in step 3 above will be listed in the drop-down option.
If the database is not listed in the /etc/oratab file - if using Linux, or if it is not listed in the Windows registry (entry created by DBCA) - it will not be listed.
You will need to add the database manually - select the Manual entry option and specify the database SID and Oracle Home when prompted.
If the database you want to create a standby database for is listed, select it and continue to the next step.
Step 5: Specify ARCHSOURCE location and Network communication.
The next step is to confirm the ARCHSOURCE location - marked as  in the image below.
- On the primary database server, this location will only be used as a temporary area to which archive logs are extracted - if using ASM before they are sent to the standby database.
- This location is not the same as the database archive log destination and should not be located in the database archive log location or fast/flash recovery area.
- Do not share this location with other databases, it must be unique to a specific DDC
- If a Graceful Switchover (GS) is performed, the ARCHSOURCE and ARCHDEST locations in the DDC files are reversed - meaning the ARCSOURCE location will become the ARCHDEST and the ARCHDEST location will become the ARCSOURCE location.
The next option to review is the use of DBVNET or SSH. The default is DBVNET which is recommended. The default port will also be displayed and can be changed.
- The default DBVNET port used is 7890 and for SSH 22.
- SSH is still a supported option on UNIX based systems but is not available if you are using Windows-based systems.
- If you do select SSH you must make sure that SSH is already configured on both primary and standby database servers with passwordless authentication.
Step 6: Select the Destination Host marked with  in the above image - this is the host that will run the standby database to be created
- It is important that the Oracle Database software (matching the primary database software in version and edition) is already installed on this host.
- From the drop-down menu select the standby database server host.
- Hosts will only be listed here if they have already been configured in the Central Console.
You will now be presented the following options as marked by  and  below.
The following fields need to be reviewed and updated where needed:
1. Oracle SID
- This is the Oracle SID to be used for the standby database.
- This is also the value that will be used for the INSTANCE_NAME of the standby database
- If you are creating two standby databases for the exact same primary on the same standby database server, the Oracle SID must be different.
- If the primary and standby database servers are an exact match, leaving the Oracle SID here at the default - which is the same as the primary (source) is recommended.
2. Select if ASM to be used?
- If the Standby database is to use ASM, change the selector to YES and specify the ASM instance name, example +ASM (see image below)
- If the Standby database is not using ASM, leave it at the default which is NO.
3. ARCHDEST location
- This is the location on the standby database server where Dbvisit Standby will copy archive logs into. This location must have sufficient disk space to keep at least two days worth of archive logs, 4 or more recommended.
- This location should not be located inside the database archive log destination or fast/flash recovery area
- Do not share this location with other databases, it must be unique to a specific DDC
4. Dbvisit Standby base directory on the destination (standby) server
- This is the location where Dbvisit Standby is installed on the standby database server.
- A default value will be provided, please make sure you have already installed Dbvisit Standby into this location and that the version match the same version used on the primary database server.
5. Oracle Home directory on the destination (standby) servers
- Dbvisit Standby will provide the same location for the Destination as what was provided for the source server. Please review the location and make sure the correct Oracle Home is used for the standby database.
6. The standby database unique name (DB_UNIQUE_NAME)
- Dbvisit Standby is making use of the Database Unique Name which is the database parameter DB_UNIQUE_NAME.
- In most cases, this value (which is the same as what was detected on the source/primary) should be sufficient without any changes required.
- If you are running more than one standby database on the standby database server for the same primary database, you must specify a different DB_UNIQUE_NAME for the standby databases.
7. The new configuration (DDC) name to be used
- The last option to be provided is the Dbvisit Configuration File (DDC) name.
- We recommend you provide a short name - in most cases the default value provided should be sufficient
- Do not use special characters in the name - example underscore "_" or a dash "-" or any others such as $,%# etc.
8. Adding a valid License Key
- The final step is to add a license key. Remember that you cannot use a v7 or v8 or v9 key for version 10.
- The license key is only added during DDC creation and it will be applied on the primary node
Step 7: Submit - The DDC file is created
Once you submit, the DDC file will be validated and created in the DBVISIT_BASE/standby/conf directory on the primary and standby database servers.
At this stage, a new repository will also be created, which is located in the same directory with the name <DB_NAME>.db.
This repository will be updated on the primary database and is not used on the standby database until a Graceful Switchover or Activation is performed.
Once the DDC file is created, you will see the configuration is listed in the Central Console - see image below.
The following options are highlighted in the image above.
- Delete DDC
- Update (refresh) DDC (use this if you have manually altered the DDC file through Command Line to synchronise your changes with the GUI)
- Edit DDC
- Upgrade DDC (The green status tick will be changed to an upgrade button if it is detected that the DDC file needs to be upgraded).
- This option will have information on how the DDC is monitored by Dbvisit observer if configured.
7.2. Create a new DDC File - Oracle RAC to Single Instance
Please see this section for more detail: Creating the DDC File#2.5.CreateaDDCFile-OracleRACprimarytoSingleInstanceStandby
7.3. Create a new DDC file - Oracle RAC to Oracle RAC
Please see this section for a detailed example: Oracle RAC Configurations#OracleRACConfigurations-5.CreatetheDbvisitStandbyDDCFile
7.4. Edit a DDC File
The GUI allows you to directly edit Configuration/DDC parameters. To do this, click the blue Edit Configuration button for the relevant Configuration on the Configurations page.
You can edit any parameter in a DDC by double-clicking on the row or clicking the blue Edit button . To set the parameter, either click the green Accept button or press Enter.
You can remove any parameter from a DDC by clicking the red Delete button .
NOTE: You CANNOT edit OR remove special system parameters - these are highlighted in blue background rows and have no action buttons available .
You can add new parameters by clicking the green New button  and selecting from the list of available parameters. Only one parameter can only be added ONCE, i.e. each parameter can only have a single value.
After making changes, click Submit to save the DDC . Until you do this, no change is made to the DDC.