Dbvisit Standby Version 8.0.x - New Features

Owned by Anton Els (Deactivated)
Last updated: Sept 20, 2018 by Vijayganesh Sivaprakasam
6 min read

1. Introduction

This section will provide you with an overview of the new Dbvisit Standby version 8 Features.

Dbvisit Standby version 8 consist out of 4 key components:

  1. Dbvserver
  2. Dbvagent
  3. Standby Core
  4. Dbvnet


On this page:

These 4 components work together to provide a full solution that can help you manage your Oracle Standard Edition (SE1, SE and SE2) standby database environment.

In summary, these components perform the following tasks:

ComponentIconDescription


Dbvserver



  • Dbvserver was introduced in Dbvisit Standby version 7 and has been completely rewritten in version 8.
  • The new Central Console - Web-based user interface
  • One Central Console to manage multiple Dbvisit Standby version 8 configurations
  • Small footprint webserver
  • Recommended to install on its own small server (Physical, Virtual Machine or Docker Image - persistent storage required)
  • Provides secure encrypted communication - HTTPS protocol on port 4433
  • Communicates to Primary and Standby Database servers via the Dbvisit Agent (dbvagent)
  • All communication with the Dbvisit Agent is encrypted and secure
  • Hosts managed by the Central Console can be Windows or UNIX (see the system requirements for more detail)
  • The Central Console does have a small repository where information about tasks being executed are stored
  • Multiple users can be created and tasks are tracked per user
  • Using the Central Console is not required - All functions of Dbvisit Standby version 8 can be run from the Command Line Interface (Standby Core)



Dbvagent


  • The Dbvisit Agent (dbvagent) is introduced in Dbvisit Standby version 8
  • This agent is the link between the Central Console and the Dbvisit Standby Core which must be installed on each database server (primary and standby)
  • The Dbvisit Agent has a small footprint and is listening for secure connections on port 7891 from the Central Console
  • All communication with the Central Console is secure and encrypted
  • The Dbvisit Agent and Central console do not have to be used - some users might only want to use the Command Line Interface (Standby Core) which does not require the Central Console or the Dbvisit Agent. In this case, the Dbvisit Agent does not have to be installed or can be left shutdown.
  • The Dbvisit Agent is compulsory to run on a host to be managed by the Dbvisit Standby Central Console
  • A small repository is used to keep track of tasks being executed from the Central Console



Standby Core



  • The Dbvisit Standby Core is also known as the Command Line Interface
  • This is where the core functions of Dbvisit Standby is performed, this include but is not limited to the following functions:
    • Creating a Standby Database (CSD)
    • Sending and Applying Archived Redo
    • Performing Graceful Switchover (Role Reversal)
    • Re-synchronize a Standby Database due to unrecoverable archive log gaps or fixing logical corruption on the standby database due to nologging operations that were performed on the primary
    • Activate / Failover of a Standby Database when disaster strikes
    • More than 80 command line API options
  • The Dbvisit Standby Core is making use of the Oracle Instant Client for connecting to the Oracle Database or ASM Instance
  • End users might perform minimal installations where only the Dbvisit Standby core is used together with SSH for network communication. In this scenario, no other component needs to be installed and this is considered a Minimal installation and is available as an option if required.
  • In Dbvisit Standby version 8, the previous multiple executables have been combined into one single easy to use command line utility called the Dbvisit Standby Control Utility - "dbvctl"
  • For detail help on using the "dbvctl" command use the "-h" option or for full detail on functions use "-h,-f"
  • Dbvisit Standby version 8 may still be scheduled, using either the Windows Scheduler or the CRON schedule. The schedule that used to be part of the Dbvserver component has been removed and is no longer available.
  • Many of the operations that can be performed by the "dbvctl" utility now allow batch operations - this will help to streamline tasks without interactive questions being asked.



Dbvnet


  • Dbvnet was introduced in Dbvisit Standby version 7 and has been completely rewritten in version 8.
  • Dbvnet is responsible for the network communication between the Oracle Database servers (Primary and Standby).
  • All communication between the systems are secure and encrypted (Encryption is on by default and cannot be disabled).
  • Dbvnet may be configured to allow compression.
  • Dbvnet has two core functions - to allow for the copy of files between servers and to allow for remote execution of commands.
  • On Windows-based systems, Dbvnet is the default and only option, whereas Unix based systems have Dbvnet as the default option, but if required, SSH may be used instead of Dbvnet.


The diagram below provides a brief overview of how the above four components work together.  The DBA (Administrator) will have the option to either run commands via the Command Line Interface (Standby Core) using the dbvctl utility - or - They can make use of the new Central Console which can be used to manage multiple installations.


Note: The above diagram is just a high-level representation of how Dbvisit Standby v8 components communicate.


2.  New Features

Dbvisit Standby version 8 new features are listed below in no particular order:

  • The command line interface is now consolidated into one single easy to use executable - "dbvctl"
  • The Dbvisit Standby Core repository is no longer stored in the Oracle Database
    • The repository has now been moved outside the Oracle database and is located in DBVISIT_BASE/standby/conf directory 
    • The repository name is DB_NAME.db
  • The directory structure of version 8 is similar to version 7 with the addition of the new Dbvisit Agent subdirectory
  • Dbvserver has been totally rewritten and now have a smaller footprint and is hosting a brand new web-based user interface - referred to as the "Central Console" 
  • The new Central Console: 
    • Can manage multiple Dbvisit Standby v8 installations
    • The new web interface has a new easy to use modern look and feel
    • A small repository is used on the web server to keep track of task information
    • Can handle multiple users (each DBA in the team can have their own login)
    • All core functions can be performed via the Central Console
      • Dbvisit Standby agent must be installed and running on all database servers
  • Dbvnet has been totally rewritten with improved performance, stability and footprint
  • Improved Batch Operations:
    • Installation
    • Create Standby Database (CSD)
    • Synchronize Standby Database (SYNC)
    • Creation of Standby Database Templates 
  • Graceful Switchover (GS) Improvements:
    • Execute / Start GS now from only one node 
    • No additional keys or execution of commands on the remote server required
    • Improved output 
    • Various performance improvements - especially in environments with large redo logs and slow networks
    • The GS process will now keep track of all trace files generated
    • Auto rollback has been implemented (if possible)
  • Improved Archivelog Management Module (AMM)
  • Various improvements for Windows-based installations
  • Improved handling of Oracle Database 12c SE/SE1 and SE2 installations
  • Support for Oracle Database 12c SE/SE1 and SE2 Multitenant (Single PDB)
  • New Improved and Exposed Command Line API
  • New Dbvisit Agent (dbvagent) is introduced.  
    • This new component will allow for communication between the Central Console and the Standby Core.  
    • All communication between the Central Console and Dbvisit Agent is encrypted
    • Tasks from the Central Console are executed on the Standby Core and task updates are pushed to the Central Console
  • New Support Package option is introduced
    • To allow for faster and easier support we have introduced a new "Support Package" option.  
    • If an error is received the Process ID will be displayed, the user can then create a support package
    • This support package will include all required information for the Dbvisit Support team to allow for quick and easy investigation of errors
    • The support package can be created from the command line as well as via the Central Console - from where it can even download the support package
  • Basic support for cascading standby databases have been introduced in Dbvisit Standby version 8
  • Oracle RAC Support Improvements:
    • Dbvisit Standby version 8 includes a large number of improvements with regards to managing Oracle RAC standby configurations
    • Dbvisit Standby version 8 is now more Oracle RAC aware.
    • If you have an Oracle RAC capable standby environment (Clusterware and storage configured with the database software installed), you can now create a full Oracle RAC enabled standby database using the Dbvisit Standby CSD process
    • Dbvisit Standby is now executed (running) on only one of the RAC nodes
    • Shared Storage is required for the Dbvisit Standby Installation as well as a Virtual IP for the cluster to be used by Dbvisit Standby only
  • Improved SQL and RMAN connections to the Database
    • Shared connections are used by default
    • Improved error handling 


  • SSH Support for network communication is still supported on UNIX systems. SSH passwordless authentication is required.