New Features
PROJECT-1554: Configurations where either the primary or standby database is hosted in Oracle Base Database Service are now fully supported.
PROJECT-1154: It is now possible to disable the application of archived logs on the standby database while still shipping them from the primary.
PROJECT-1835: When using our DR Testing functionality, it is possible to use Intelligent Activation to choose how many archived logs to apply to the standby database prior to activation.
PROJECT-1837: General Reminder notifications are now sent if you have a license key that will expire soon.
PROJECT-1959: Oracle Intelligent Activation is now an option when activating the standby database whenever there are unapplied archived logs present on the standby host. Previously, this was only available when Standby Update Delay has been configured.
Improvements
General:
PROJECT-1822: The code that cleans up processes left over from previous executions of the dbvagentmanager service could kill unintended processes in rare situations. The logic has been tightened up so that only the appropriate processes are killed.
PROJECT-1823: The process for identifying the relevant trace files when creating an Oracle support package has been changed to be based on a time period rather than a PID or tracefile name. This should make it easier for users to provide the information needed by Dbvisit support.
PROJECT-1844: Support packages now include information about the license keys in use. This will allow the support team to identify issues related to licensing more quickly.
PROJECT-1911: Files included in support packages now preserve their modification times. This will allow the support team to provide better support in some cases.
PROJECT-1912: When upgrading the agent from a previous v11 or v12 version, the existing host name configuration was not pre-populated as the default value for the new installation, as was done for other fields. This has been fixed for both Windows and Linux installers.
PROJECT-1961: The time zone shown when configuring the Observer heartbeat time was incorrect when the product was switched to a Chinese language. This has been fixed and the correct time zone is now displayed for all languages.
PROJECT-1966: The list of new features shown on the login page has been updated.
PROJECT-1967: Perpetual license keys were shown as having an expiry date in the year 2099. The display has been changed to indicate that these are perpetual licenses.
PROJECT-1972: The timestamp shown when clicking on an event in the GUI was incorrect. This has been corrected.
PROJECT-1990: The documentation link shown on the Create Configuration page has been updated to the latest documentation.
PROJECT-1997: If the dbvagentmanager service was started from an interactive shell using nohup as an OS user that does not have password-less sudo access, a sub-process could hang when performing pre-checks for Graceful Switchover, causing the Graceful Switchover task to fail. The hang has been fixed.
Oracle:
PROJECT-1898: A check performed during Graceful Switchover that could cause the switchover to fail in some circumstances has been removed. The check related to the temporary tablespace of the XS$NULL user and was found to be unnecessary.
PROJECT-957: The COMPRESS and UNCOMPRESS DDC parameters need to be changed together so that we can verify that they match. The GUI for editing them now allows them both to be changed in one operation. Also, the value “Y” is now accepted, with the same meaning as “dbvisit”, which is to use our default compression method.
PROJECT-1001: Warnings in the dbvagentmanager.log file relating to the Snapshots functionality could appear even if Snapshots are not in use. These spurious warnings have been removed.
PROJECT-1050: The “Archived Source sequence #” field on the Detailed Log Gap Report was unpopulated when the source database was RAC. This field is now shown correctly.
PROJECT-1435: When using archive log compression (via the COMPRESS and UNCOMPRESS DDC parameters), the Intelligent Activation feature didn’t offer unapplied compressed archive logs as possible activation points. Compressed archive logs are now recognized as possible activation points.
PROJECT-1456: When there is more than one Oracle configuration with Automated Standby Update enabled on a host, and that host is restarted, one or more of the configurations could fail to start the Automated Standby Update daemon process after the restart. This was caused by the presence of a stale PID file. These stale files are now cleaned up when the dbvagentmanager service is started, fixing this problem.
PROJECT-1652: In some cases when many configurations exist on one host, defunct processes could be left after starting the dbvagentmanager service. These processes didn’t cause problems other than consuming a small amount of system resources, but we have fixed the code to clean these processes up immediately.
PROJECT-1845: If the license key for a configuration was updated while the standby database was activated for DR testing, the DR Test status could be lost, leading to the need to manually restore the standby database. This rare problem has been fixed.
PROJECT-1887: When upgrading from Dbvisit Standby v10, some bookkeeping information could be lost, leading to a warning in the history log file. This has been corrected.
PROJECT-1893: Detailed information about Oracle versions from 18c is now properly extracted. This only affects some internal processing.
PROJECT-1894: While a DR Test is in progress, including the backup of the standby database, the time period during which the standby database is activated, and the restore of the standby database, archived logs now continue to be shipped from the primary to the standby. This reduces the potential for data loss if the primary database becomes unavailable during a DR Test.
PROJECT-1895: Some fields on the “Archive Log Management” settings page were enabled for editing even if the current user didn’t have permission to change these settings. It was not possible to save the changes made in these fields. These fields are now properly disabled for users in the “Monitor” role.
SQL Server:
PROJECT-2013: A cosmetic issue with the form for editing detail of an existing SQL Server instance has been fixed.
CLI and API:
PROJECT-1823: Changed parameters for dbvcli and API
PROJECT-1967: Change to API response for perpetual licenses
PROJECT-1154: New parameter for dbvcli create-standby and dbvcli auto-update edit
PROJECT-1554: New parameter --tde-wallet-password for dbvcli create-standby and API
PROJECT-1835: dr-test start and dr-test/start/oracle: The --activate-point/activate_point flag is now required when Standby Update Delay is enabled
dr-test resume and dr-test/resume/oracle: The --activate-point/activate_point flag is now required when Standby Update Delay is enabled
PROJECT-1959: dbvcli activate and activate/oracle: The --activate-point flag is now required when Standby Update Delay is enabled
PROJECT-1710: Several dbvcli commands, when run on the same host as the database being operated on, could fail to display details of the operation. The affected commands include activate, send-logs, apply-logs, start, stop, restart. This has been fixed.
PROJECT-1803: The dbvcli command doesn’t work on Windows Server 2012R2 (and earlier) due to missing virtual console support. It now exits with an informative error message instead of an obscure error message.
Comments