Improvements
Oracle
PROJECT-2103: If an Oracle configuration had the CASCADE parameter in the DDC file set to Y when the source database was not a standby database, an erroneous configuration, then not only would a CSD fail, but the source database would be restarted first. Now, the CSD will still fail, but the source database will not be restarted.
PROJECT-2018: A change made in StandbyMP version 12.1.0 to allow srvctl to be used in non-English locales had the side effect of filling trace logs with large amount of unnecessary information. This has been fixed.
PROJECT-2187: Graceful Switchover now requires that both primary and standby instances are at the exact same version. A new DDC parameter, _GS_IGNORE_VERSIONS, can be set to allow the versions to be different, for example during upgrades. Even with the new parameter set, only compatible versions are allowed.
General
PROJECT-2185: An error in non-English translations introduced in StandbyMP version 12.3.0 caused a misleading error message to be displayed when saving Automated Standby Update settings. The settings were saved successfully despite the error message. The translations have been corrected.
PROJECT-2223: Visiting the login page now logs out all browser tabs in the same browser instance, for additional security.
SQL Server
PROJECT-2207: A change made in StandbyMP version 12.3.0 caused the Activate Standby action to be hidden in the GUI if the primary SQL Server instance or Dbvisit StandbyMP Agent Manager was unavailable. The activate action could still be initiated using dbvcli. This has been fixed and the GUI can now initiate Activate Standby even when the primary instance is not available.
Comments