Always willing to help and assist, superb services
Jose Cleto, President— Ninphas
Presales (click question for answer)
What is the difference between Dbvisit Standby and Dbvisit Replicate?
The key difference between the two products relates to the solution space that they are targeted to address, and the characteristics of the replication technology they use.
- Designed as a DR Solution
- Performs Physical Database Replication - the Secondary (standby) is exactly the same as the Primary, in terms of both data and structure. It comes with tools for DR functions such as Graceful Switchover, Failover, Creation the Standby database etc
- Designed as a Replication, Data Migration, Reporting and ETL extract solution
- Performs Logical Database Replication - the target can be a subset of data, and the structure can be different. The target database can even be non Oracle (SQL Server or MySql)
=> A detailed comparison of the two applications can be found here.
Is automatic failover supported with Dbvisit Standby? What is the failover process?
We prefer not to automate the failover process as it is difficult for software to determine if it is a real disaster or just a temporary glitch. The failover process cannot be reversed so it is crucial that this only happens in case of a real disaster.
With Dbvisit Standby the standby database is ready to take over instantly at any time. It only requires one Dbvisit Standby command to activate the standby database and this can be scripted to run automatically if automatic failover is required.
Does Dbvisit Standby support multiple standby databases?
Yes, Dbvisit Standby supports multiple standby databases from the same primary database. There is no limit to the number of standby databases supported for one primary database. Setting up an additional standby database takes about 2 minutes!
Can I do a Graceful Switchover (role reversal) with Dbvisit Standby?
Yes this is fully automated in Dbvisit Standby. Please see our Graceful Switchover page.
Can Dbvisit Standby be used with Oracle Fail Safe?
Yes, Dbvisit Standby can be used in a Microsoft clustering environment with Oracle Fail Safe. Please see our Pricing Plans page for Dbvisit Standby licensing requirements for Oracle Fail Safe (non-RAC) clusters.
Does Dbvisit Standby create a standby database automatically?
Yes this is available from Dbvisit Standby version 5.2.
Alternatively please see our documentation on how to manually create a standby database:
Can Dbvisit Standby be used in a UNIX cluster environment?
Yes, Dbvisit Standby can be used in a UNIX or Linux clustering environment. Please see our Pricing Plans page for details on cluster licensing for Dbvisit Standby in a RAC or non-RAC clustered environment.
Does Dbvisit Standby impact database processing?
Dbvisit Standby runs outside the database and therefore has very limited impact on database processing. Dbvisit Standby does not use PL/SQL packages or database triggers. When Dbvisit Standby runs, a log switch occurs by default (although this can be turned off) and this may have an impact on database processing (Data Guard has a similar impact on database processing). The more frequently Dbvisit Standby is scheduled the more this impact will be. If compression is enabled, which again it is by default, then this will also require some resource. If your network connection is large enough to accommodate the log file volume then you could also consider turning the compression off.
Can Dbvisit Standby be used in an Oracle RAC environment?
Yes, Dbvisit Standby can be used in an Oracle RAC environment. Please see the Dbvisit Standby product page for more information.
When I purchase a Dbvisit Standby license, how long does this last?
The Dbvisit Standby license is a perpetual license. It lasts forever, and the license for the standby server is also included with that purchased for the primary server. See the Pricing Plans page for more information.
Is there a Windows version for Dbvisit Standby?
Yes, to download please go to the downloads section on our website.
Can Dbvisit Standby run in a virtual server? What is your licensing model for virtual servers?
Yes, Dbvisit Standby is fully supported to run in a virtual environment. The Dbvisit Standby licensing model is that we license per virtual server, according to the number of physical CPU's that are allocated to the virtual server.
What sort of reporting can we get out of Dbvisit Standby?
The Dbvisit Standby repository installed in the Oracle database provides a lot of useful information and can be accessed using standard SQL. Some examples are: How long it takes for each log to transfer to the standby server, archive log gap analysis etc. This information can be obtained using any SQL reporting tool (TOAD or PL/SQL Developer) that connects to the database. Please see the Dbvisit Standby Installation Guide and User Manual on our documentation page for more information.
Do you provide support and updates to Dbvisit Standby?
Yes, Dbvisit Standby is a fully supported product, and this service and updates are provided through a DbvisitProtect subscription. Please see the DbvisitProtect page to find out more about this service.
Additonally Dbvisit Standby creates comprehensive trace files which can be emailed to our support team to be analyzed so that issues can be quickly resolved.
System Requirements (click question for answer)
How is Dbvisit Standby installed?
Dbvisit Standby is installed through a menu (dbvisit_setup) that guides you through the installation process. Dbvisit Standby will recommend most of the settings. Typically the installation takes about 15-30 minutes. The database does not need to be restarted and there are no init.ora parameters that need to be altered. See our documentation page for a complete overview of the installation. In addition to this we also offer quick and normal installation guides on our Resources page.
Technical (click question for answer)
Can the TM (transportable media) option of the CSD (create standby db) process utilize a tape drive?
Yes if the tape drive can be mounted onto a filesystem (like a USB drive).
With Dbvisit Standby do the tablespaces need the same directories/sizes as the primary?
The database files (and tablespaces) for the standby database do not have to be in the same directories as the primary database, but this is highly recommended as it will make administration of the standby database much easier. It will also make creation of the standby database much easier. The automatic standby datafile creation feature of Dbvisit Standby also assumes the standby database files are in the same directories as on the primary database. Please see the Dbvisit Standby forum for help if your standby server configuration is not the same as the primary server.
The tablespace size will automatically be the same size as the primary database. This cannot be changed.
Can we install Dbvisit Standby in any location: /u01/oracle/dbvisit/ or d:\program files\dbvisit?
Dbvisit Standby can be installed in any location. Dbvisit Standby can be installed in different locations on the primary and the standby servers.
How to start/stop the database synchronization process with Dbvisit Standby?
Dbvisit Standby is started on both the primary and standby servers with the same command:
Where <database> is your database name.
This will synchronize the databases at the time that the Dbvisit Standby process is run.
To continuously synchronize the databases, the Dbvisit Standby command has to be scheduled on both the primary and standby servers (say every 10 minutes).
By stopping the Dbvisit Standby scheduling, the synchronization process will also stop. See the full list of Dbvisit Standby commands.
Is it easy to change the configuration of Dbvisit Standby?
Yes, it is very easy to change the configuration of Dbvisit Standby for a particular database. Each database has a separate configuration file which is a plain text ASCII file and can be easily edited using any text editor. We call this configuration file the DDC file (Dbvisit Standby database configuration file).
The DDC file can also be updated through the Dbvisit Standby setup utility:
An overview of all the Dbvisit Standby configuration settings can be found in the user guide.
Does memory configuration of the standby database matter with Dbvisit Standby?
The memory configuration of the standby database is independent to the primary database. In most cases the standby server has less capacity than the primary server, so the memory settings for the standby database is usually less than the primary database.
The memory configuration of the standby database has no impact on Dbvisit Standby processing.
What kind of error reporting does Dbvisit Standby generate if failures occur?
There will be an email sent, and there will be an entry in the Dbvisit Standby "alert" log. The location of the Dbvisit Standby alert log will be specified by the LOGDIR variable in the Dbvisit Standby database configuration (DDC) file. The name of this alert log is specified by the JOBHIST variable but is dbvisit.hist by default. Just as the Oracle alert log can be monitored by a monitoring tool, so the Dbvisit Standby alert log can also be monitored by a monitoring tool. The Dbvisit Standby alert log is a very condensed log which makes monitoring easy.
Dbvisit Standby will also produce a trace file. The email will contain the name and location of the trace file. The trace file can be sent to Dbvisit Standby support for analysis.
Other (click question for answer)
Your question is not answered?
if your question has not been answered here then please check our forums or blog site, or alternatively get in contact with us.
Businesses in over 110 countries worldwide with Oracle® Database Standard Edition trust Dbvisit to protect and share their data.
Join a growing community of Oracle experts using Dbvisit software as the key to unlocking untapped revenue from customers and prospects.
Dbvisit provides Oracle® Database Standard Edition users with affordable disaster recovery and data replication solutions.