When installing Dbvisit Standby on an environment using ASM for database storage, Oracle Grid Infrastructure version 11.1 and higher is recommended.
The minimum version of ASM supported by Dbvisit Standby is 10.2 with the following exceptions:
Using version 10.2 for ASM storage is supported, but with one advanced functionality of Dbvisit Standby which is not supported - Graceful Switchover (GS).
All other functionality such as Activation and Synchronization of the standby database is still supported with 10.2 ASM, but it is recommended to run the latest patch set (10.2.0.5)
Oracle ASM 10.1 is not supported.
The following advanced configurations are supported:
Oracle Real Application Cluster (RAC) 10g
Oracle Real Application Cluster (RAC) 11g
Oracle Real Application Cluster (RAC) 12c
Dbvisit Standby version 7 supports the use of:
Automatic Storage Management (ASM) - 11g and above recommended to use all features provided by Dbvisit Standby.
Oracle Managed Files (OMF)
The use of a Fast/Flash Recovery Area (FRA)
Dbvisit Standby version 7 does not support Oracle versions prior to 9i. If Oracle 8i are used it is recommended to make use of the most recent Dbvisit Standby version 6.
When using Oracle 10g ASM, the Graceful Switchover feature will not be available.
If using ASM, it is recommended to make use of Oracle 11g Release 2 and higher (including latest patches).
Oracle Database 12c Multitenant Architecture (Pluggable Database option) is not currently supported, but this is planned for future release updates.
If 10g Oracle RAC environments are used, it is recommended that they are patched to the latest patch set, 10.2.0.5. Oracle Grid Infrastructure (11g and above) is recommended, but Dbvisit Standby will work with 10gR2 ASM, with the exception that the Graceful Switchover functionality will not be available.
It is good practice to ensure the latest patches are applied to both the Grid Infrastructure and Database Homes.
Important: The primary and standby server Oracle Software Edition and version should be identical. When using 64bit it is strongly recommended that you use 64bit for both primary and standby and that you do not mix binaries, example having 64bit primary with 32bit standby.
Ignoring the above note and running mixed editions or mixed binaries can lead to unexpected results when performing database activation or graceful switchover.
Supported Operating Systems
Dbvisit Standby version 7 is supported on the following Operating Systems:
For Microsoft Windows Platforms it is recommended that the User Access Control (UAC) should be turned off when running Dbvisit Standby.
The following Microsoft Windows versions (32bit and 64bit) are supported (Base release including Service Packs are supported):
Please make sure you test Dbvisit Standby in your Development or Test environment prior to implementation into production to ensure Virus Software, Firewall, UAC and Group policies does not affect the normal operation of Dbvisit Standby.
Important: The primary and standby server Operating System also should be identical.
The following Linux Distributions are supported (x86 and x86_64):
Oracle Linux 4
Oracle Linux 5
Oracle Linux 6
Oracle Linux 7 (64 bit)
Red Hat Enterprise Linux 4
Red Hat Enterprise Linux 5
Red Hat Enterprise Linux 6
Red Hat Enterprise Linux 7
In addition our current release 7.0.60 (19 June 2016) supports
- Linux x86 32bit and 64bit (OEL (4,5,6,7), RHEL (4,5,6,7) and SLES (10,11))
- MS Windows 32bit and 64bit
- Solaris (SPARC) and x86 for Intel and AMD (Solaris 10 and 11)
Make sure glibc.i686 package is installed when using Oracle Linux 6 or Red Hat Enterprise Linux 6
Dbvisit Standby is installed on all servers forming part of the Standby Database configuration. The following system requirements are the minimum required for Dbvisit Standby installation:
300Mb space for the Dbvisit Standby software installation on the file system. The software installation takes approx. 70Mb of space, and it is recommended to have sufficient space for trace file generation. Dbvisit Standby generates a trace file each time it executes, containing information about Dbvisit processing and its environment. When an alert or error notification is sent by Dbvisit, the trace file will be attached to the email so that this can be forwarded to Dbvisit support if needed, allowing them to quickly diagnose issues. A minimum of 200Mb space is recommended.
10Mb space for the Dbvisit Standby Database Repository inside the Oracle Database. The repository stores information used for reporting as well as Create Standby Database (CSD) template information which can be used to easily re-create standby databases if required.
The standby database server will require the same amount of storage capacity as the primary database server.
Dbvisit Standby makes use of a Dbvisit Archive Destination referred to as ARCHDEST. This is used to store the archive logs shipped from the primary server to the standby server. This location is NOT the same as the database archivelog destination.
This location should be big enough to keep at least 1 day's worth of archive logs, but capacity to store three days or more is recommended.
Example, if you generate 2GB worth of redo (archive logs) on the primary in one day, you should have at least 2GB as an absolute minimum free space on the standby in the folder specified as the ARCHDEST.
The following browsers are recommended when using the Dbvisit Standby Web Based interface:
Having an up to date version of Flash installed and enabled in the browser is required for the reporting pages.