Dbvisit TechnicalOverview

Dbvisit
Oracle Disaster Recovery and Standby Database

made simple and cost-effective
Technical Whitepaper
Avisit Solutions Limited
www.dbvisit.com
Contents
Contents ............................................................................................................................................................ 2
Copyright Notice ................................................................................................................................................ 2
Audience............................................................................................................................................................ 2
Introduction ........................................................................................................................................................ 3
Highlight technical features ............................................................................................................................... 4
Complete technical specifications ..................................................................................................................... 5
Installation.......................................................................................................................................................... 7
Dbvisit System Requirements ........................................................................................................................... 8
Platform ............................................................................................................................................................. 8
What is included in the Dbvisit software for Windows ....................................................................................... 8
Dbvisit versus Data Guard................................................................................................................................. 9
Graceful switchover (role reversal).................................................................................................................. 10
Oracle RAC...................................................................................................................................................... 11
Reporting database ......................................................................................................................................... 12
Dbvisit architecture .......................................................................................................................................... 13
Scheduling ....................................................................................................................................................... 14
Log files ........................................................................................................................................................... 14
Trace files ........................................................................................................................................................ 14
Dbvisit help ...................................................................................................................................................... 15
Interactive mode .............................................................................................................................................. 15
Dbvisit commands overview ............................................................................................................................ 15
Dbvisit Archive Log Management Module....................................................................................................... 17
AvisitProtect..................................................................................................................................................... 18
Contact ............................................................................................................................................................ 18
Copyright Notice
Copyright  Avisit Solutions Limited
All rights reserved. Price and specification are subject to change without notification.
This document is the property of Avisit Solutions Limited. Dbvisit is a product of Avisit Solutions Limited.
Dbvisit is a registered trademark of Avisit Solutions Limited.
Oracle is a registered trademark of Oracle Corporation.
Audience
This document is intended for a technical audience. Experience with the Oracle database and standby
database is necessary to understand the concepts behind Dbvisit.
Dbvisit Technical Overview © Avisit Solutions Limited page 2 of 18

Introduction
What is Dbvisit:
Dbvisit automates the synchronisation of a hot standby database at a remote or local location. A standby
database is like having an online hot backup of your database instantly available 24x7. There is no need to
restore in the event of a disaster (which is very time consuming), as there is instant data recovery and
database recovery. It is possible to switch over to the standby database in a matter of minutes to allow
business continuity in an emergency. No other software is required to replicate the primary database onto a
separate standby server.
An overview of Dbvisit is represented in figure 1.
Figure 1 – Overview of Dbvisit processing.
Why Dbvisit:
Unlike other generic Disaster Recovery products, we focus solely on Oracle and do not compromise on
features and functionality to ensure that your Oracle databases are protected. We support all Oracle features
such as RAC, ASM, OMF and Flash Recovery, maximising the benefits of using Oracle.
Dbvisit can implement automated Oracle standby database without Data Guard. Dbvisit can be used with the
Standard Edition (SE) of Oracle, Standard Edition One and with Oracle XE. This makes Dbvisit a very cost
effective solution compared with upgrading to Oracle Enterprise Edition to enable utilisation of Oracle Data
Guard.
Dbvisit supports multiple Oracle options:
Dbvisit works in a multi Oracle version environment, in a mixture of Oracle 32bit and 64bit, in a mixture of
editions (Enterprise, Standard, Standard Edition One and XE) and in a mixture of versions (8, 9i, 10g and
11g).
Future proof your investment as Dbvisit will work with all versions and features of Oracle (from 8i onwards
both 32bit and 64bit).

What is special about Dbvisit:
Dbvisit runs outside the database therefore causing minimal interruption of the database. It runs as
an executable allowing it to capture precise snapshot images of the database for rollback purposes.
Dbvisit eliminates the need of external monitoring as it does not run on agent or daemons (unlike
Data Guard), it thus remains active without supervision.
Greater bandwidth is not required because it automatically compresses archive logs before
replicating to the Oracle Standby database.
Dbvisit does not use complex SQL*Net configurations, reducing the number of open firewall ports;
thus making the data more secure and less vulnerable.
Highlight technical features

Automatic Graceful switchover to reduce downtime during maintenance outages using its role reversal
capabilities. The primary database transitions to a standby database and the standby database
transitions to a primary database with no data loss. It can also be used for the failback process after
disaster or failure. Graceful switchover works for Oracle 8i, 9i, 10g and 11g.
Automatic creation of the standby database from normal, RAC or ASM databases.
Time-delayed standby database updating enabling data loss due to human error or software error to be
recovered.
Compression used to ensure distance independency and minimum bandwidth requirement between
production and standby systems.
Complete protection from all types of failures, including software and human errors, faulty batch jobs,
sabotage as well as natural or man made disasters.
Supports all Oracle features such as RAC, ASM, OMF and Flash recovery area.
Secure encrypted transport mechanism.
Easy to use with no training required. Simple failover process.

Complete technical specifications
 Time-delayed standby database updating enabling data loss due to human error or software error to
be recovered.
 Automatic creation of the Standby Database from normal, RAC or ASM database.
 Automatic gap identification with conflict resolution.
 Failover to backup or standby database in case of disaster or severe outage.
 Supports Oracle versions 8i to 11g, both 32 bit and 64 bit (may support Oracle 7.3 and 8.0 in some
cases).
 Supports all Oracle editions from Enterprise Edition (EE), Standard Edition (SE), Standard One to
Oracle Express Edition (XE).
 Dbvisit works with Microsoft Windows, Unix, Linux and Itanium Linux.
 Simple to install and configure. Dbvisit on Windows comes with a modern Windows installer. With
Dbvisit, any Oracle DBA can have a fully automated process to keep the standby database up to
date in less than 30 minutes.
 Database does not need to be shutdown or restarted to install Dbvisit. Database init.ora parameters
do not need to be modified.
 Multiple Standby Databases from the same primary database. Each standby database has its own
schedule, parameters and thresholds.
 Switch back to the "old" primary database after a disaster with automatic graceful switchover. This is
a seamless automated operation done in a matter of minutes with no dataloss. This works with
Oracle 8i, 9i, 10g and 11g.
 Provides automatic graceful switchover which may be used for planned outages. This is a reversible
role transition between the primary database and a standby database with no data lost during the
switchover operation. Automatic switchover works with Oracle 8i, 9i, 10g and 11g.
 Supports Oracle RAC (Real Application Cluster) on SE (Standard Edition).
 Supports Oracle flash recovery area and ASM file systems.
 Dbvisit automatically resends the logs incase of network issues.
 Logs are compressed before being transferred to the Oracle standby database. This means that the
link between the production database and the standby database does not need to be a high speed
link.
 Very secure. Secure shell (with encryption) is standard (even on Windows). SQL*Net is not used. No
extra ports need to be opened on the firewall.
 Dbvisit can also stop, start and open normal and open standby databases in read only mode with
simple commands which can be scheduled.
 Automatic notification included. Notification thresholds can be set.
 Fully automated management and monitoring of the Oracle archive logs on both the primary and
standby server. If space becomes an issue, automatic notifications will be sent, and archive logs can
be automatically removed if required.
 Resends specific log files, and resynch with standby database if the standby database is rebuilt.
 Dbvisit is external to the database and cannot conflict with normal Database operations, and
minimizes the impact on database performance. Dbvisit does not use Database triggers.
 Site specific pre and post commands are supported.
 Full reporting available about the replication process including timings of the compression and
transfers.
 Backup or standby database can be used for BI, dataware housing or reporting purposes.

 Provides full archive log gap and transfer log gap reporting.
 Dbvisit produces comprehensive trace files which can be analyzed by Dbvisit support for fast
turnaround time on any issue.
 Automatic continuation without intervention of the DBA when temporary network or database
problems occur.
 All database changes are replicated to the standby database. There are no exceptions.
 Superior to automated log shipping. See a comparison between Dbvisit and log shipping.
 Simple alternative to Data Guard. See a comparison between Dbvisit and Data Guard.
 Automatic space management. Dbvisit will automatically add datafiles and tablespaces to the Oracle
standby database which have been added to the primary database. Works for Oracle 8i and above.

Installation
Installation of Dbvisit is through a wizard driven menu system. Dbvisit will suggest default values for most
variables, making the installation routine very simple. These can either be accepted or changed at any
stage.
=========================================================
Dbvisit Standby Database Technology
http://www.dbvisit.com
Dbvisit Database setup

Default values will be shown in []
Options:
1) New Dbvisit Database setup (combines options 2,3,4)
1a) New Dbvisit RAC Instance setup (combines options 2,3,4)
2) New Dbvisit Database configuration (DDC) file setup

3) New Dbvisit Archive Management Module (AMM) setup
4) New Dbvisit Database repository (DDR) setup
5) Manage Dbvisit Database repository (DDR)

6) Update Dbvisit Database configuration (DDC) file
7) Create Standby Database
9) Uninstall Dbvisit Database repository (DDR)

E) Exit
=========================================================
Please enter choice :1
Once installed on the primary server, the installation is replicated automatically to the standby server. Any
change to the configuration is only done on the primary server, and are replicated to the standby server
automatically. The database does not need to be shutdown or restarted to install Dbvisit. Database init.ora
parameters do not need to be modified.
Dbvisit on Windows uses a Windows installation wizard and includes SSH software to ensure a secure
encrypted transport mechanism to the standby server:
Online quick installation guides and video tutorials are available to demonstrate how to install and configure
Dbvisit. Please see http://www.dbvisit.com.

Dbvisit System Requirements
- 40MB of space on the primary and standby servers for the Dbvisit software
- 10MB of space for the Dbvisit database repository in the Oracle database.
- Identical database management system and operating system versions on production and standby
system.
- Similar storage capacity on production and standby system.
Platform
Dbvisit runs on Microsoft Windows (NT4, 2000, 2003, 2008, XP, Vista), Unix platforms (Solaris, HP-UX, AIX)
and Linux.
Oracle versions from Oracle 8i, 9i, 10g and 11g. Dbvisit works with Standard Edition (SE), Oracle Enterprise
Edition (EE), Workgroup Server, Edition One and Oracle XE.
Dbvisit works with Oracle RAC, Microsoft Cluster Server, Oracle fail safe, ASM, OMF and flash recovery
area.
What is included in the Dbvisit software for Windows

The following external software is included in the Dbvisit for Windows software. This software is fully licensed
and is included as part of the Dbvisit license.
1. Bitvise WinSSHD. WinSSHD is a SSH Secure Shell 2 server for Windows NT4, 2000, XP, 2003 and
Vista. It provides the mechanism to securely accept the Dbvisit database update transfers. For more
information please see http://www.bitvise.com/winsshd.
2. Bitvise Tunnelier. Tunnelier is a SSH and SFTP client for Windows. It provides the mechanism to
securely transfer the Dbvisit database update. For more information please see
http://www.bitvise.com/tunnelier.

Dbvisit versus Data Guard
Dbvisit is a real alternative for Oracle Data Guard without the cost and complexity.
Data Guard is the disaster recovery product offered by Oracle to keep the standby database up to date. Data
Guard only comes with Oracle Enterprise Edition (EE).
Dbvisit has similar features to Data Guard, but is much more cost-effective than upgrading to Oracle
Enterprise Edition to be protected in case of internal and external disasters.
Dbvisit works with all editions of Oracle (including Oracle Standard One, XE and Standard Edition) and all
versions of Oracle (from 8i onwards).
* Dbvisit offers minimum of 60 seconds data loss. Maximum protection mode in Data Guard which offers 0% data loss comes with a
high price and high performance costs which are unacceptable for most companies.
** We believe the decision to failover to the standby database should not be automatic, as it could just be a temporary glitch. However
the failover is a simple command in Dbvisit and can be automated if this feature is required.
Dbvisit does not use SQL*Net, it uses secure shell (ssh) mechanism even on Windows. Dbvisit for Windows
includes ssh software from Bitvise to securely transfer the updates to the standby server. This makes Dbvisit
very secure on all platforms and servers are not compromised by using non secure ports and non encrypted
transport mechanisms.

Graceful switchover (role reversal)
Graceful switchover is also referred to as role reversal.
Graceful Switchover is used to switch back to the original primary database after a disaster in which the
standby database has been activated.
Graceful Switchover may also be used for planned outages to perform an upgrade on the primary site by
switching over the database users to the standby site as hardware or software is upgraded on the primary
site. It may also be used to test the Disaster Recovery scenario.
During a switchover, the primary database transitions to a standby role, and the standby database
transitions to the primary role. There is no loss of data during the transition and the standby database does
not have to be rebuilt.
After the planned outage is completed, Graceful Switchover can reverse back to the original state.
Figure 2 - Graceful switchover
How the Dbvisit Graceful Switchover process works

1. Users are temporarily disconnected from the main primary database.
2. Dbvisit Graceful Switchover is initiated.
3. Main primary database is shutdown during transition.
4. Standby database is shutdown during transition.
5. Main primary database transitions to standby database on primary server in matter of minutes*.
6. Standby database transitions to primary database on standby server in matter of minutes*.
7. Users can re-connect to primary database on standby server and continue working, with no data loss.
8. Maintenance can proceed on primary server.
9. Optionally Dbvisit can keep the standby database on the primary server up to date during the scheduled
maintenance outage.
10. At the end of the scheduled maintenance the databases are transitioned back to their original state in
matter of minutes*.
*Depending on speed of network and distance between primary and standby server.

Oracle RAC
Dbvisit can be used together with Oracle RAC (Real Application Cluster) to provide high availability and
disaster recovery. RAC can be used with Oracle Standard Edition.
RAC allows multiple instances on different nodes to access a shared database on a cluster system. RAC
allows scalability by plugging in extra hardware when needed.
Standby node setup with RAC
The Oracle standby database can configured as a single instance database or as a RAC database with
several instances on different standby nodes.
1. RAC primary and RAC standby database.
 All primary nodes need to send the archive logs to a shared location on the RAC standby cluster.
 Dbvisit only needs to be scheduled on one standby instance to apply the archives from all threads
to the standby database
2. RAC primary and single instance Oracle standby database.
 All primary nodes need to send the archive logs to the single standby node.
 Dbvisit will apply the archives from all threads to the single instance standby database.

Reporting database
To offset the load on the primary database and server when running large reports, these reports may be run
on a reporting database. This reporting database functions much like a standby database and is an exact
copy of the production database running on a separate server.
This reporting database feature can be used for:

1. Providing a reporting database to run large reports without impacting the primary database and
server. Having this functionality can help ease the load on the primary database by migrating large
reports to the reporting database.
2. Providing an up-to-date database for a remote office.
The difference between a standby database and a reporting database is that the reporting database is
available in READONLY mode while a standby database is not available for reading purposes. A standby
database is in recovery mode.
When a reporting database is in READONLY mode, it is not able to be kept up to date with the primary
database. Only when the reporting database is in recovery mode, can it be kept up to date with the primary
database.
The reporting solution can be totally automated
Dbvisit can automate the process so that the reporting database is available for reporting during the day and
at night is in recovery mode to automatically start applying all the updates that have arrived during the day
and subsequent night. Next morning, Dbvisit will automatically open the reporting database in READONLY
mode so that it is up to date with the primary database to run reports.
Cost effective
In order to safe cost, the function of the reporting database and the standby database can be combined into
one standby database with Dbvisit. This makes Dbvisit a very cost effective solution that provides both a
standby and a reporting database.
Continuous protection
With Dbvisit it is possible to open the standby database for reporting purposes during the day, while the
primary database is still sending updates to the standby/reporting server. This ensures you are continuously
protected as all the updates are available ready to be applied in case of disaster or failure.

Dbvisit architecture
The Dbvisit architecture has been kept as simple as possible to ensure ease of use, yet remain secure.
Dbvisit installs straight on to the database server. There is no need to install a java agent or client. Dbvisit is
not dependent upon SQL*Net or any database listeners being present.
The main features of the Dbvisit architecture are:
1. Server based.
2. Command line interface for ease of use and security
3. Dbvisit runs on both the primary and standby server independently from each other. No
communication is necessary between the Dbvisit process on the primary server and the Dbvisit
process on the standby server.
4. Dbvisit is scheduled separately on the primary server and standby server using any available
scheduling tool including cron or Windows scheduler.
5. Dbvisit is scalable as Dbvisit can be used with Oracle RAC and Oracle ASM filesystem.
6. Comprehensive error checking at every level. If any errors are detected then alerts are raised
depending on set thresholds. Dbvisit produces comprehensive trace files which can be analysed by
Dbvisit support for fast turnaround time on any issue.
7. Dbvisit runs external to the database to limit the impact on database performance.
8. Dbvisit is a completely hands-off operation and automatically recovers from temporary network
outages or glitches. No manual intervention is required.
9. Dbvisit repository can be used for reporting using standard SQL queries. Reports on duration of log
transfer, archive log gap, duration of compression step etc.
Dbvisit managers
Figure 4 - Dbvisit managers
Dbvisit consists of 6 Managers:

1. Dbvisit Oracle SQL manager: Manages the interface to the Oracle database using standard SQL
functionality. This allows Dbvisit to work against all versions of Oracle.
2. Dbvisit transfer log manager: Manages the transfer of the compressed archive logs to the standby
server. It records successful transfers in the Dbvisit repository. If there are any outages in the
network, then the Dbvisit transfer log manager will continue to attempt the transfer until successful.
3. Dbvisit apply log manager: Manages the applying of the Oracle archive log to the standby
database and intercepts any messages from the Oracle database. It will also add additional data
files to the standby database if these have been added to the primary database.
4. Dbvisit OS manager: Interfaces with the Operating System.

5. Dbvisit Error manager: Tests and verifies every step of the process and ensures that everything
completes successfully. This also traps any Oracle or OS errors that may occur.
6. Dbvisit logging manager: Logs all activity and records successful Oracle archive log files which
have been transferred. Creates comprehensive trace files for auditing and support purposes.
Scheduling
Dbvisit is scheduled using a scheduler. Dbvisit is scheduled separately on both the primary and the standby
server.
The most common way to schedule Dbvisit is to use cron on Linux/Unix and Windows scheduler on
Windows servers.
To schedule Dbvisit the following cron entry is made on both the primary server and the standby server:
# Dbvisit - Standby Database Technology from Avisit Solutions Limited
00,10,20,30,40,50 * * * * /usr/local/dbvisit/dbvisit dbvisitp
Where dbvisitp is the name of the Database.
This schedules Dbvisit every 10 minutes, 24 hours a day, 7 days a week.
Log files
Log files are an integral part of Dbvisit. Log files are created on both the primary server and the standby
server.
Normal logging is kept to a minimal to allow easy integration with monitoring tools. Once an error is detected,
logging is elaborate. An example of the Dbvisit log files:
200903132000 - 1 Log transfer(s) for dbvisitp completed. Last sequence was 82.
200903132030 - Problem with /usr/bin/rcp /oracle/oraarch/dbvisitp/arch84.log.gz
avisit02:/oracle/oraarch/dbvisitp/arch84.log.gz..
Program terminated.
200903132045 - Archived Redo Log transfer for dbvisitp terminated: Archive file
/oracle/oraarch/dbvisitp/arch*84.log not found.
Program terminated.
200903132100 - Log transfer for dbvisitp terminated: Archive file
Program terminated.
Program terminated.
Program terminated.
Dbvisit automatically manages the log files to ensure that they do not grow too big.
Trace files
Dbvisit produces comprehensive trace files. These trace files can be by sent to Dbvisit support to be
analysed to provide quick resolution on any issue.
When Dbvisit raises an alert or error, Dbvisit will specify the trace file to be sent to Dbvisit support for
analysis.
Dbvisit automatically manages the trace files to ensure that they are removed after a set number of days
when no longer needed.

Dbvisit help
Dbvisit help is available on the command line. Type dbvisit to display the help:
NAME
Dbvisit - Oracle Standby Database Technology.
Automated managed Standby Databases.
Automatic creation of Standby Databases.
Oracle Disaster Recovery.
VERSION
Version 5.2.14.2406
USAGE
dbvisit ORACLE_SID
dbvisit -r SEQUENCE_NUMBER ORACLE_SID
dbvisit -R ORACLE_SID
dbvisit -i ORACLE_SID
dbvisit -c ORACLE_SID [nocksum]
dbvisit -ReverseCopy ORACLE_SID
dbvisit -lic ORACLE_SID
dbvisit -lic ORACLE_SID LICENSED_USER LICENSE_KEY
dbvisit -?
dbv_oraStartStop start ORACLE_SID
dbv_oraStartStop stop ORACLE_SID
dbv_oraStartStop open ORACLE_SID
dbv_oraStartStop status ORACLE_SID
dbv_oraStartStop activate ORACLE_SID [Yes]
dbv_oraStartStop switchover ORACLE_SID [UNIQUE_KEY]
<more>
Interactive mode
Dbvisit can also be run manually on the command line. This is normally done during testing, or when the
database needs to be synchronised outside the normal schedule period.
An example of running Dbvisit interactively is:
[oracle@avisit02 dbvisit]$ dbvisit dbvisitp
======================================================
Dbvisit Standby Database technology
dbvisit started on avisit02:
======================================================
Archive file(s) for dbvisitp from avisit01 will be applied to avisit02...
200903152112 - Log seq 188 applied to standby database dbvisitp.
200903152112 – Log seq 189 applied to standby database dbvisitp.
200903152112 – Log seq 191 applied to standby database dbvisitp.
======================================================
dbvisit ended on avisit02:
======================================================
[oracle@avisit02 dbvisit]$
Dbvisit commands overview

The following list gives an overview of the Dbvisit commands available.
Where oracle_database is name of database (ORACLE_SID).
Everything in square brackets “[ ]” is optional.
dbvisit Dbvisit help. Displays the dbvisit help pages.
dbvisit oracle_database Normal Dbvisit operation. This command is run on primary and standby
servers.
Transfers log files from primary database if run on primary server.
Applies log files to standby database if run from standby server.
dbvisit –i oracle_database Reports on the log sequences of:
1. Latest archived log of primary database
2. Latest non archived log of primary database (redo log)

3. Latest log sequence of standby database
4. Latest log sequence sent by Dbvisit
It also reports on the:
Archive log gap which is difference between the last archived sequence
on the primary and the last applied sequence on the standby database.
The archive log gap should be near 0
Transfer log gap which is the difference between the last archived
sequence on the primary and the last sequence transferred to the
standby server. The transfer log gap should be near 0.
dbvisit –r sequence oracle_database
Specific log and all subsequent logs will be resend to the standby database.
sequence is the log sequence number from which Dbvisit will start transferring
logs until the current log.
dbvisit –R oracle_database Used when standby database has been rebuilt. Resynchronise primary
database with standby database.
Dbvisit will connect to the standby database and determine the next log which
needs to be applied. This log and all subsequent logs will be transferred from
the primary database until the current log.
dbvisit_setup Run the dbvisit setup and configure utility. This can do the following:
1. New database or RAC Instance setup
2. Create standby database
3. New Dbvisit Database Configuration (DDC) file setup
4. New Dbvisit Archive log Management Module (AMM) setup
5. New Dbvisit database repository (DDR) setup
6. Manage the database repository (DDR)
7. Update Dbvisit Database Configuration (DDC) file
8. Uninstall Dbvisit
Can only be run on the primary server.
dbv_oraStartStop start oracle_database
Starts the database. This may be either a regular (primary) database or a
standby database. Dbvisit will determine if the database is a primary or a
standby database and will start it accordingly.
dbv_oraStartStop stop oracle_database
Stops (shutdown) the database. This may be either a regular (primary)
database or a standby database. Dbvisit will determine if the database is a
primary or a standby database and will start it accordingly.
dbv_oraStartStop restart oracle_database
Stops (shutdown) and then starts the database. This may be either a regular
(primary) database or a standby database. Dbvisit will determine if the
database is a primary or a standby database and will stop and start it
accordingly.
dbv_oraStartStop status oracle_database
Displays the status of the database. This can be either a regular (primary)
database or a standby database.
dbv_oraStartStop open oracle_database
Opens the standby database in READONLY mode.
dbv_oraStartStop activate oracle_database [Yes]
In the event the primary database is no longer available. Activates the standby
database to become a primary database. Activation cannot be reversed. A
new standby database will have to be built.
To disable the prompt to confirm that the database can be activated specify
Yes on the command line.
dbv_oraStartStop switchover oracle_database [unique_key]
Initiates the Graceful Switchover process to transition the primary database to
a standby database and the standby database to a primary database. This
command must be given on both the primary and the standby servers.
There is no loss of data during the transition and the standby database does
not have to be rebuilt.
To run in batch mode, a unique key can be specified on the command line.
This unique key must be the same on both the primary and standby server
and can be any number not used before.
dbv_functions -h Brings up help for dbv_functions. This performs various Dbvisit functions like
compression, copying, repository reporting, creating control file, list %full
Diskspace, checksum etc. This utility may also be used on its own.

Examples
dbvisit dbvprod1 Run Dbvisit for database dbvprod1.
dbvisit_setup Setup and configure Dbvisit for a specific database.
Also:
- Creates Standby Databases.
- Configures the Dbvisit Archive Management Module.
- Manages the Dbvisit repository.
- Updates the Dbvisit database configuration file (DDC).
dbvisit -r 345 dbvprod1 Run Dbvisit starting at sequence 345 until the current sequence for database
dbvprod1.
Standby database does not need to be up and running.
dbvisit -R dbvprod1 Resynch. Contact the standby database to find the next sequence that it
requires. Resend starting from this sequence for database dbvprod1.
Standby database needs to be up and running.
dbvisit -i dbvprod1 Reports on the log sequences of database dbvprod1:
1. Latest archived log of primary database
2. Latest non archived log of primary database (redo log)
3. Latest log sequence of standby database
4. Latest log sequence sent by Dbvisit
5. Archive log gap
6. Transfer log gap
dbv_oraStartStop activate dbvprod1
Activates standby database dbvprod1 to become a primary database.
dbv_oraStartStop switchover dbvprod1
Initiate Graceful Switchover between the primary and the standby database.
The primary database transitions to a standby database and the standby
database transitions to a primary database. There is no loss of data during the
transition and the standby database does not have to be rebuilt.
Dbvisit Archive Log Management Module

The Dbvisit Archive Log Management Module is included in all versions of Dbvisit.
The Dbvisit Archive Log Management Module fully automates the management and monitoring of the Oracle
archive logs on both the primary and standby server.
Unlike Oracle database files, Oracle archive logs need to be monitored and managed constantly to ensure
the database continues its optimal operation. If the disk space available to Oracle archive logs is used up,
then the whole database will “freeze” and not allow any update or insert operation.
Dbvisit Archive Log Management module includes the following options:
1. Alerts through email when Oracle archive logs have reached a set threshold of available disk space.
2. Can delete Oracle archives logs after a set number of days.
3. Can delete Oracle archive logs after available disk space has been used up to ensure continual
database operation.
4. Can keep a certain number of Oracle archive logs on the server.
5. Ensures the Oracle archive logs have been transferred to standby database before removing any
logs.
6. Works on both primary and/or standby servers.
7. Can integrate with Backup software to ensure logs have been backed up before removing.
The Dbvisit Archive Log Management Module is easy to configure and provides peace of mind to ensure that
the database continues its optimal operation and will not suffer as a result of poorly managed Archive log
files or insufficient disk space. Note: Normal backup software should still be used to backup Oracle archive
log files to tape or other storage device.

Support - AvisitProtect
Oracle databases running with Dbvisit are fully supported by Oracle.
Avisit Solutions Limited provides full technical support and updates to Dbvisit.
Dbvisit provides free technical support during the evaluation period to ensure your standby databases are
managed effectively by Dbvisit.
AvisitProtect is a maintenance and support product which is able to be purchased on an annual basis and
which allows access to unlimited email, online, or telephone technical support along with access to all
product enhancements and fixes.
First, in the rare occasion you get an "error", they (Dbvisit) do not just give you an error message, but tell
you the exact steps to fix it in the message. Also I was so pleasantly surprised and grateful to experience
something completely different with this company. They are real people.
-Jill Salo - Oracle DBA | Westpeak Global Advisors | USA
Contact
For more information, a 30 day evaluation version or to purchase Dbvisit please contact us at:
Web: http://www.dbvisit.com
Email: info@dbvisit.com

Dbvisit TechnicalOverview

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dbvisit TechnicalOverview

Uploaded by

Copyright:

Available Formats

Dbvisit

Oracle Disaster Recovery and Standby Database

Avisit Solutions Limited

Dbvisit Technical Overview © Avisit Solutions Limited page 2 of 18

Figure 1 – Overview of Dbvisit processing.

Dbvisit Technical Overview © Avisit Solutions Limited page 3 of 18

Highlight technical features

Dbvisit Technical Overview © Avisit Solutions Limited page 4 of 18

Dbvisit Technical Overview © Avisit Solutions Limited page 5 of 18

Dbvisit Technical Overview © Avisit Solutions Limited page 6 of 18

Dbvisit Database setup

2) New Dbvisit Database configuration (DDC) file setup

5) Manage Dbvisit Database repository (DDR)

7) Create Standby Database

9) Uninstall Dbvisit Database repository (DDR)

Dbvisit Technical Overview © Avisit Solutions Limited page 7 of 18

What is included in the Dbvisit software for Windows

Dbvisit Technical Overview © Avisit Solutions Limited page 8 of 18

Dbvisit Technical Overview © Avisit Solutions Limited page 9 of 18

Figure 2 - Graceful switchover

How the Dbvisit Graceful Switchover process works

Dbvisit Technical Overview © Avisit Solutions Limited page 10 of 18

Dbvisit Technical Overview © Avisit Solutions Limited page 11 of 18

This reporting database feature can be used for:

Dbvisit Technical Overview © Avisit Solutions Limited page 12 of 18

Figure 4 - Dbvisit managers

Dbvisit consists of 6 Managers:

Dbvisit Technical Overview © Avisit Solutions Limited page 13 of 18

Where dbvisitp is the name of the Database.

This schedules Dbvisit every 10 minutes, 24 hours a day, 7 days a week.

Dbvisit Technical Overview © Avisit Solutions Limited page 14 of 18

Dbvisit commands overview

Dbvisit Technical Overview © Avisit Solutions Limited page 15 of 18

Dbvisit Technical Overview © Avisit Solutions Limited page 16 of 18

Dbvisit Archive Log Management Module

Dbvisit Technical Overview © Avisit Solutions Limited page 17 of 18

Dbvisit Technical Overview © Avisit Solutions Limited page 18 of 18

You might also like