Supported Oracle Database Version
Dbvisit Standby version 7 supports the following Oracle Editions:
Oracle Database Standard Edition (SE)
Oracle Database Standard Edition One (SE1)
Oracle Database Enterprise Edition (EE)
Oracle Database Express Edition (XE)
The following Oracle Database versions are supported with Dbvisit Standby Release 7:
Oracle Database 10g
Oracle Database 11g
Oracle Database 12c (excluding Multitenant – pluggable database environments)
The following advanced configurations are supported:
Oracle Real Application Cluster (RAC) 10g
Oracle Real Application Cluster (RAC) 11g
Oracle Real Application Cluster (RAC) 12c
Oracle Fail-Safe
Dbvisit Standby version 7 supports the use of:
Automatic Storage Management (ASM)
Oracle Managed Files (OMF)
The use of a Fast/Flash Recovery Area (FRA)
Dbvisit Standby version 7 does not support Oracle versions prior to 10g. If Oracle 8i or 9i 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.
Supported Operating Systems
The following Linux Distributions are supported (x86 and x86_64):
Oracle Linux 4
Oracle Linux 5
Oracle Linux 6
Red Hat Enterprise Linux 3
Red Hat Enterprise Linux 4
Red Hat Enterprise Linux 5
Red Hat Enterprise Linux 6
Suse Linux Enterprise Server 8
Suse Linux Enterprise Server 9
Suse Linux Enterprise Server 10
Suse Linux Enterprise Server 11
Storage Requirements
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:
200Mb 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 (ARCHDEST) to store the archive logs shipped from the primary server to the standby server. 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. For example, if you generate 2GB worth of redo (archive logs) on the primary in one day, you should have at least 2GB minimum free space on the standby in the folder specified as the ARCHDEST.