This section will cover the supported Database versions and features for Dbvisit StandbyMP product for each platform: Oracle, SQL Server and postgres.
1. Oracle Database Support
a. Oracle Database Editions Support
Dbvisit StandbyMP product supports following editions of Oracle database:
Oracle Database Standard Edition 2 (Including “Standard Edition” and “Standard Edition 1”)
Oracle Database Enterprise Edition
Oracle Database Express Edition
It is not supported to create Oracle Standby database with different edition than primary database.
Only in very specific case when absolutely no EE features are used in primary database, it is possible to create SE2 standby database.
b. Oracle Database Versions Support
Following table contains list of supported database versions by Dbvisit StandbyMP:
Oracle Database Version |
---|
|
Support of Oracle Database version isn’t limited by specific release (for example 11.2.0.4), but we always recommend to be on the terminal patchset, otherwise there could be bugs resulting in issues with deployment or synchronziation.
c. Oracle Database Features and Advanced Deployment Configurations Support
In following table you can find list of features supported by Dbvisit StandbyMP:
Feature | Supported | Support Notes |
---|---|---|
ASM | Yes |
|
SEHA (Standard Edition High Availability) | Yes |
|
RAC (Real Application Cluster) | Yes |
|
Failsafe | Partially |
|
PDB (Pluggable database) | Yes |
|
Non-Oracle OS Clustering Software (Pacemaker) | Partially |
|
ODA KVM DB | Yes |
|
d. Oracle Database Deployment Support for configuration-heterogenous environments
Dbvisit StandbyMP supports configuration-heterogenous deployment for following cases:
Standby SI FS | Standby SI ASM | Standby RAC ASM | Standby SEHA ASM | |
---|---|---|---|---|
Primary SI FS | Yes | Yes | No | No |
Primary SI ASM | Yes | Yes | No | No |
Primary RAC ASM | Yes | Yes | Yes | N/A |
Primary SEHA ASM | Yes | Yes | N/A | Yes |
SI=Single Instance Deployment
FS=Filesystem
We Strongly recommend that standby server does have sufficient hardware configuration so as it will be able to sustain live production traffic without any issues in case of Disaster Recovery scenario.