3.2. Creating the DDC (Non-RAC)
This section will guide you through the steps to create a Dbvisit Standby Configuration (DDC) file using the version 8 Central Console (Web-Based User Interface)
The steps to create the DDC files are:
3.2.1. Step 1: Select Manage Configurations
From the Main menu screen seen below, select "Manage Configurations"
3.2.2. Step 2: The Default Configuration Screen
During the Initial Configuration, there will not be any DDC files known to the Central Console.
If you already have Dbvisit Standby version 8 DDC files on the primary and standby hosts (you might have created them via the command line and want to inform the Central Console of its existence), you can Import them into the Central Console by clicking the Import button , selecting the Host you want to import from, and then selecting the DDC. Once imported, you will be able to see these existing DDC files on the main "Manage Configurations" screen.
The example here is for a cleanly installed system where no DDC files exist yet. The next steps will guide you through the process of creating the new DDC file.
From the screen below click on the "NEW"  button to start the process.
3.2.3. Step 3: Select the Source Host
The Source host can be seen as the Primary Database Server.
3.2.4. Step 4: Accept License
The Next step is to accept or decline the license agreement. The process can only continue if you accept the license agreement.
3.2.5. Step 5: Select The Source Database
Dbvisit Standby version 8 will look at the /etc/oratab file for any known databases on the source server. If you are not using this file it is recommended you do add the databases to this file.
For more details on the use of the /etc/oratab file please consult the Oracle Documentation. The normal format of an entry in this file is: <SID>:<ORACLE_HOME>:<AutoStart-Yes-or-No>, example:
If you are using a Windows-based system, the details will be extracted from the Windows Registry Entries - which is created by the DBCA on creation.
If the Database you have running on the system is not listed in the dropdown list, you may add it by selecting the "Manual Entry" option.
3.2.6. Step 6: Specify Source Options and Destination (Standby) Server
This section allows you to specify 2 specific options - as highlighted in the image below with the number 4.
- The ARCHSOURCE location
- The network communication option to be used, Dbvnet (default) or SSH
The ARCSOURCE Location:
- The ARCHSOURCE location is the location on the Primary server where Dbvisit Standby will copy archive logs to.
- It is recommended that this locations directory structure matches the ARCHDEST from the destination (Standby server).
- In previous versions, the ARCDEST parameter was used to cater for both the Primary and the Standby and had to match. In version 8 the new ARCHSOURCE parameter was introduced to allow the Primary and Standby servers to have a different location.
- During Graceful Switchover (Role Reversal) the ARCHSOURCE and ARCHDEST parameter values will automatically be exchanged (swapped/reversed).
- The default location will be: ORACLE_BASE/dbvisit_arch/<DDC> - which in this example is: /u01/app/oracle/dbvisit_arch/DEV
- It is important to make sure this location used have sufficient storage to keep at least one day's worth of archive logs (2 days recommended)
- This location will only be actively used when the database is converted to a standby database.
- IMPORTANT - The ARCSOURCE location is not the same as the Oracle Database Archive Log Destinations and must never be located inside the Fast Recovery Area (FRA) or be the same as the default Oracle Database Archive Destination
The Network Communication Option:
- Dbvisit Standby version 8 supports two key communication options (with the exception of Windows-based systems)
- The options are:
- Dbvnet (Default and recommended option)
- When using Dbvnet the default port for communication is 7890 it may be adjusted
- Before adjusting the port, you need to make sure the DBVNET on both primary and standby database servers are configured and using the required port.
- If you want to use SSH, it is required that SSH user equivalence be configured and that passwordless authentication is working between the primary and standby servers.
- The Default SSH port is 22 and may be changed.
As pointed out by the red marked number 5 in the above image, you now need to select the destination also known as the "Standby Host"
In this example, the standby server is "dbv2" which is selected. Once selected, the Standby Database Options are enabled - see Step 7 below.
3.2.7. Step 7: Standby Database Options
The Standby Database Options are highlighted with the number 6 (and arrows) in the image below. These include:
- The Standby Database Oracle SID (Instance Name)
- This may be different than the Primary Database Instance Name
- Selecting if ASM is to be used on the Standby Database Server
- Note that if you select yes for this option you must already have ASM configured on the standby database server.
- Once you select Yes a new input box will be enabled asking for the ASM instance name, example "+ASM"
- The ARCHDEST location
- This is where Dbvisit Standby will copy archive logs to on the standby database server.
- By default, compression will be enabled and archive logs will be stored in compressed format on the standby server.
- This may be changed following the DDC file creation.
- The ARCHDEST location is not the same as the Oracle Database Archivelog destination and should never be located in the Fast Recovery Area (FRA) or be the same location as the Database Archivelog Destination.
- The ORACLE HOME location of on the Standby Server
- It is recommended that you add an entry into the /etc/oratab file on the standby server for the standby database
- The Unique Database Name
- This will be the DB_UNIQUE_NAME value for the standby database
- It may be different than the Primary database one - by default, it will be set to the same value which should be fine for most configurations
- You must set this to a different value if you are running two standby databases on the same standby database server - where both of them are for the exact same primary database.
- The Configuration Name
- This is the Dbvisit Standby Configuration (DDC) name
- It is recommended to use the default value provided, but you may adjust this if required
Once you have entered all the details - click on "SUBMIT" and the DDC file creation will start. This process only takes a few seconds.
Once complete you will see the DDC file listed under the Configurations menu option.
The following are highlighted in the image above for the DDC that was created named DEV:
- Configuration/DDC name
- Known source host
- Known destination host
- The current version of the Configuration/DDC
- Current status of the Configuration/DDC. The possible statuses are: Up-to-date (operational), Obsolete (must be upgraded), Disabled (one or both Hosts cannot be contacted)
- Edit option - select this if you want to edit the DDC, see step 8 below (optional)
- Refresh option - this might be required if a Graceful Switchover was performed using the Command Line Interface instead of the Console - selecting the refresh option will confirm the Source and Destination hosts and update the information in the Console if required
- Remove the DDC - this will only remove the DDC from the Central Console as well as from the systems - use with caution
3.2.8. Step 8: Editing The DDC
It might be required to Edit the DDC to enable additional options - such as enabling Email Notifications or making changes to the default Archivelog Management Module (AMM) parameters.
The two Figures below provide you with a summary of the options available:
- Select NEW to add new parameters
- Click on the pencil to edit parameter values (or select the value with the mouse - click)
- Lines marked with light blue are non-editable parameters
- Once editing is complete, click on SUBMIT to confirm and submit the changes