This section will provide you with an overview of the new release updates of Dbvisit Standby version 10.
To check your current Dbvisit Standby Version and Release from the command line.
Dbvisit Standby as of version 10 caters for the following operating systems:
- Oracle Linux 6 and 7 (64 bit)
- Red Hat 6 and 7 (64 Bit)
- SLES 11 and 12 (64bit)
- Windows (See known issues below)
- Windows Server 2008 and above (64bit)
Dbvisit Standby Version 10 is supported only on Windows and Linux platforms
Dbvisit Standby version 10 supports the following Oracle Database versions:
- Oracle Database 10gR2 (10.2.0.5 recommended) - If using ASM 11gR2 version required for Graceful Switchover
- Oracle Database 11gR2
- Oracle Database 12cR1 and R2
- Oracle Database 18c (Supported exclude Oracle 18c RAC)
- Oracle Database 19c - Linux
- Oracle Multi-tenant for Oracle SE2 is supported
- New pluggable databases can be added to an existing primary database, which will be propagated to standby database when you send and apply archivelogs.
- Max of 3 pluggable databases is allowed in the primary databases. If you are adding more than 3 pluggable databases, please contact Dbvisit support.
2. Known Issues
It is possible that release updates will include known issues. This section should be reviewed for any new release.
- Dbvisit Standby currently only supports ipv4, not ipv6.
- It was noted that on Windows ipv6 may be favoured, and if the hostname resolution is not ipv4, Dbvnet, Dbvserver and Dbvagent may listen on ipv6 when started.
- If Dbvnet, Dbvserver and Dbvagent are not able to listen on ipv4 due to name resolution favouring ipv6, you will have to make use of ipv4 IP addresses in the Dbvnet, Dbvagent, Dbvserver configuration files as well as your Dbvisit Standby DDC file (for the SOURCE and DESTINATION)
- Using the following commands after starting Dbvnet, Dbvagent and Dbvserver, you will be able to identify whether it is listening on ipv4 or ipv6:
- Dbvnet: netstat -an|findstr 7890
- Dbvagent: netstat -an|findstr 7891
- Dbvserver: netstat -an|findstr 4433
- Dbvisit Standby includes Oracle 12.2 Instant Client libraries by default. If your system has a different version of Oracle installed, it is possible under some rare circumstances for a library version conflict to occur. If you experience any errors similar to "PRKN-1008: Unable to load the shared library orasrvmhas12.dll", you can usually resolve them easily by renaming this library in the dbvisit/standby folder to "orasrvmhas12.dll.12.2" or by using replacing the Instant Client libraries in dbvisit/standby or dbvisit/standby/lib (depending on your operating system).
From Dbvisit Standby v10 onwards, there is an option provided to you for choosing the Oracle instant client libraries. By default, the libraries are Oracle 12.2, otherwise you can choose to use Oracle 12.1 libraries.
3. Change Log
10.0.0 (1 January 2021)
New Feature: Oracle Multitenant support - Seamlessly handle creating and deleting up to 3 Pluggable Databases, always ensuring your standby database is correctly kept up to date.
New Feature: Reporting Replicas & Test/Dev Snapshots - Save costs and improve performance by fully utilizing both your production and standby environments. Reporting Replicas enable offloading performance-intensive tasks from your primary database onto your standby database, while ensuring that you always have fresh data to work with. Test/dev Snapshots allow for very quick creation of test/dev environments, often within seconds.
This feature replaces the optional Dbvisit Snapshots feature in Dbvisit Standby version 9+.
New Feature: New & Improved Network Management Utility - A new and upgraded Dbvnet, with all-new logging capabilities, better handling of unstable networks and automatic resolution of remote execution errors. Improve the reliability and resilience of your DR solution by getting the most out of your network.
New Feature: Upgraded Central Console - An updated, more streamlined central console (GUI) with full multi-language support.
STDBY-481: Dbvisit Standby v10 now comes with Oracle Instant Client libraries 12.1 and 12.2 (default 12.2). Selection of which one to use is possible during the installation process.
STDBY-783: Graceful Switchover is now possible on Windows environments with both Oracle Unified Auditing and Oracle versions 12.1 and lower
STDBY-763: Improved interaction of Snapshot creation and Parallel Recovery
STDBY-802: Improvements and fixes for DDC parameter handling during Graceful Switchover on RAC environments
STDBY-525: Host status indicators on the Manage Databases page are now real-time
STDBY-613: Added new options for setting custom DB_DOMAINS on Snapshots
STDBY-788: Added handling for historical Tasks with missing timestamps
STDBY-785: Observer will no longer send emails for all monitored DDCs when only one is updated
STDBY-775: Improved Mail function logging
STDBY-744: Dbvisit Reporting Replica Snapshot creation time interval is now in minutes instead of seconds
STDBY-756: Dbvisit Observer now automatically updates itself with any changes to Host configurations (e.g. passphrase)
STDBY-752: Dbvisit Observer now correctly handles Host passphases containing rare special characters
STDBY-760: New warnings and user notifications implemented for possible interactions of Reporting Replicas and DR Test functionality
STDBY-738: Updated description of update_dbenv_file function in help text
STDBY-481: Dbvisit Standby v10 now comes with Oracle Instant Client libraries 12.1 and 12.2 (default 12.2).
I have already installed Oracle Client 19.5.
Will dbvisit use this client, or should I remove it?