1. Introduction
This page will provide you with more detail on the system requirements for Running Dbvisit Standby MultiPlatform.
This includes Operating System (OS) support as well as the Oracle Database version support matrix.
2. Supported Operating Systems
This section will cover the supported Operating Systems for Dbvisit Standby MultiPlatform.
2.2. Linux
Dbvisit Standby MultiPlatform will only support 64bit Linux Installations.
The following Linux Distributions are supported (x86_64 / 64bit):
Supported Linux Distributions |
|---|
|
2.3. Microsoft Windows
Dbvisit Standby MultiPlatform will only support Microsoft Windows 64bit Installations.
Note that Dbvisit Standby MultiPlatform uses IPv4 and not IPv6. By default, during installation, the dbvagentmanager and dbvcontrol will list the IP addresses that it will listen on and also will also display the resolvable hostname for the control center.
For Microsoft Windows Platforms the following is recommended:
User Access Control (UAC) should be turned off when running Dbvisit Standby.
The Windows Account running Standby Multiplatform should be a Local or Domain account with the following group membership:
ORA_DBA
Local Administrators
Oracle Home DBA group - (if using 12c make sure the user is in the new Oracle Home DBA group)
Please make sure you test Standby Multiplatform in your Development or Test environment prior to implementation into production to ensure Virus Software, Firewall, UAC and Group policies do not affect the normal operation of Dbvisit Standby.
The following Microsoft Windows versions (64bit) are supported (Base release including Service Packs are supported):
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
Windows Server 2019
Windows Server 2022
When using Windows-based systems, it is recommended not to make use of the Uniform Naming Convention (UNC) paths - example: \\server\share_name
But to make use of local filesystem naming example: c:\folder_name\
3. Oracle Database Support
3.1. Supported Oracle Database Editions
Standby MultiPlatform supports the following Oracle Editions:
Oracle Database Standard Edition (SE)
Oracle Database Standard Edition One (SE1)
Oracle Database Standard Edition 2 (SE2)
Oracle Database Enterprise Edition (EE)
Oracle Database Express Edition (XE)
Please note that the primary and standby database server Oracle Editions must match!
Having mixed Oracle Database Editions are not supported.
3.2. Supported Oracle Database Versions
The following Oracle Database versions are supported with Standby MultiPlatform:
Oracle Database 10g (10.2.0.5)
Oracle Database 11g
11.1.0.7
11.2.0.1 is the base version supported
Oracle 11.2.0.4 and above patch level recommended
11.2.0.1 was released Sep 2009
11.2.0.4 was released Aug 2013
Oracle Database 12c
Oracle SE/SE1 up to 12.1.0.1
Oracle SE2 and EE 12.1.0.2 and above
12.1.0.1 was released June 2013
12.1.0.2 EE was released July 2014
12.1.0.2 SE2 was released Sep 2015
Oracle SE2 and EE 12.2 is supported from Dbvisit Standby 8.0.12
12.2.0.1 was released May 2017
Oracle Database 18c
Oracle SE2 (including Oracle RAC configurations starting from v9.0.04+)
Oracle EE - excluding Oracle RAC configuration as well as any specific Enterprise Edition features
Oracle Database 19c
Oracle SE2
Oracle EE - excluding Oracle RAC configuration as well as any specific Enterprise Edition features
Oracle Database 21c
Oracle SE2
Oracle EE - excluding Oracle RAC configuration as well as any specific Enterprise Edition features
The Oracle Database software version between primary and standby servers must match.
Having different versions such as patch levels are not supported and can cause unexpected results if Graceful Switchover (GS) or Activation/Failover is attempted.
The following features are not supported:
Flex ASM in Oracle version 12.1 and above
ASM mirroring syntax for standby init parameters (e.g.
db_create_file_dest=+DATA(FG$FILEGROUP_TEMPLATE_MIRROR))
3.3. Oracle Automatic Storage Management (ASM) Support:
When installing Standby Multiplatform on an environment using ASM for database storage, Oracle Grid Infrastructure version 11.2 and higher is recommended.
Recommended 11g version to use 11.2.0.4 including the latest patch updates.
Recommended 12c version 12.1.0.2 and above, including latest patch updates.
3.4. Support for Advanced Configurations - Oracle RAC
The following advanced configurations are supported:
Oracle Real Application Cluster (RAC) 11g
Oracle Real Application Cluster (RAC) 12c
Oracle Fail-Safe
If using Oracle RAC configurations, using the latest patch sets are highly recommended.
3.5. General Support Notes
In addition to the above mentioned, Standby MultiPlatform supports the following options:
Oracle Managed Files (OMF)
The use of a Fast/Flash Recovery Area (FRA)
Oracle Database 12c Multitenant Architecture is supported
3.6. Unsupported Configurations
Standby Multiplatform does not support the following configurations/options:
Cross-Platform Standby Database configurations
4. Microsoft SQL Server Supported versions.
Standby MultiPlatform supports SQLServer from version SQL Server 2012 to the latest version SQL Server 2019. Below are the editions supported by Standby MultiPlatform.
Enterprise Edition
Standard Edition
Web Edition
Personal Edition
Express Edition
5. 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 Standby MultiPlatform installation:
5GB space for the Dbvisit Standby software installation on the file system - however, 15GB is recommended especially for multiple configurations and because of tracefiles.
Standby Multiplatform is using Archive Logs to update the standby database. There should be sufficient space on the Standby Database server to store the archive logs from the primary database server. It is recommended you have sufficient space to keep at least 1 to 2 days worth of archive logs on disk. Please make sure you cater for peak load periods during which more redo can be generated.
IMPORTANT: The standby database server will require the same amount of storage capacity as the primary database server.
Standby Multiplatform makes use of a Dbvisit Archive Destination referred to as ARCHDEST (on the standby server) and ARCSOURCE (on the primary server)
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 to 2 day's worth of archive logs, but the 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 as an absolute minimum free space on the standby in the folder specified as the ARCHDEST.
If you are using ODA machines, It is required that you create the dbstorages before creating the standby databases using Dbvisit. Please refer to v10 documentation for the example of creating dbstorage:
On Linux, if you have dedicated mount for /tmp, make sure it is NOT mounted with “noexec” option. This can be verified with for example “mount -l” command.
6. Network Requirements
Dbvisit Standby Version 11 uses following ports:
DbvagentManager File transfer Port | Listens on 7890 TCP - Archivelog transfer to Standby database |
ControlCenter Ports | Listens on 4433 TCP - Webserver for user access via browser Listens on 5533 TCP - communication from dbvagentmanger |
The firewall rules need to be allowed as per this picture:
Host | Port to whitelist | Source |
|---|---|---|
ControlCenter host | 5533 | All primary and standby servers |
ControlCenter host | 4433 | All administrator workstations |
Primary host | 7890 | Standby host, ControlCenter host |
Standby host | 7890 | Primary host, ControlCenter host |
7. Browser Requirements
For ControlCenter access, Dbvisit version 11 supports Chrome, Firefox and Edge browsers.
Comments