/
Release Notes

Release Notes

Owned by Vijayganesh Sivaprakasam
Last updated: Apr 01, 2025
4 min read

New Features

  • CLI: A powerful new command line syntax, unified across Oracle, SQL Server and PostgreSQL configurations, allows for simple, standardized and automated management of our DR product.

  • API: Featuring the ability to control StandbyMP fully remotely from any third-party tool or software suite, our new API allows for streamlined integrations into complex workflows never previously possible.

  • New license key format: from v12.1 onwards, StandbyMP is switching to a new format license key. Please see the detailed notes linked below.

Deprecations

  • postgresql The WAL File Shipping replication mode for PostgreSQL is deprecated. Existing configurations using the WAL File Shipping replication mode will continue to function, but no new configurations using this mode can be created. All support for the WAL File Shipping replication mode will be removed in a future release, at which point all configurations using the WAL File Shipping replication mode will need to be recreated using the WAL Archiving or WAL Streaming replication modes.

Improvements

General


PROJECT-854: The “maximum number of failed checks” Observer setting now also applies to checks of the standby database, allowing you to limit the number of notifications received when the standby database is not in the expected state.

PROJECT-1442: It is now possible to configure the domain name used in the HELO/EHLO message sent while talking to the SMTP server when sending email. This is necessary in some situations to prevent email sent by StandbyMP from being rejected as spam.

PROJECT-1760: The “Dismiss Task” button on task details displays has been renamed to “Hide Task” to better reflect its purpose. It is only available for tasks that have finished running.

PROJECT-1818:A new license key format has been introduced. This will allow you to have more confidence that your software is correctly licensed.

PROJECT-1145:Dismissing a task whose configuration has since been deleted could result in an error. This has been fixed so that tasks for deleted configurations can be dismissed from the timeline without error.

PROJECT-1307:Some of the data files that StandbyMP uses to store information about its operations could grow large over time, potentially leading to disk space exhaustion and performance degradation. These data files are now automatically cleaned of data that is no longer needed.

PROJECT-1428:The Windows installer now always creates a log file, in the %TEMP% directory, to assist support to debug problems with installation.

PROJECT-1642:The command to reset tasks and events did not include events created by the Observer. This command should only be used at the request of the support team, and will now include Observer events.

PROJECT-1830:The Observer check interval now has a minimum value of 10 seconds, enforced consistently in the Control Center, API and CLI.

PROJECT-1833:When testing email notification sending, if the debug output is large, the Control Center could fail to show the close button. This has been fixed.

PROJECT-1836:The OpenAPI document describing our public API is now installed under the docs directory.

PROJECT-1896:A non-functional “add new” link has been removed from the settings page for product users. This link didn’t do anything except cause confusion.

Oracle

PROJECT-1772:The Standby Activation Test could fail when a Standby Update Delay is configured, leaving the standby database requiring manual intervention to recover. The Standby Activation Test is now not available if a Standby Update Delay is configured. The feature will be re-enabled in a future version.

PROJECT-689:Incorrect validation of input parameters when creating a standby database on SEHA meant that it was not possible to specify the use of ACFS. This validation has been removed.

PROJECT-777:Creating a standby database where the log_archive_dest_* database parameters contain commas (such as occur in attributes like VALID_FOR=(ALL_LOGFILES,ALL_ROLES)) could result in an error. These parameters now have special handling so that values containing commas can be used.

PROJECT-1000:When validation failed for some standby database parameters, the validation was not re-run, leading to the validation error persisting even if the error was resolved. This has been fixed so that parameters are always re-validated each time.

PROJECT-1142:When restarting a RAC database, only one instance was restarted. This has been fixed so that the entire database is restarted, making it consistent with the start and stop database actions.

PROJECT-1299:In some cases, actions involving more than one database on the same host could interfere with each other, leading to, for example, a failure to activate all databases at once. This has been fixed so that simultaneous actions on different databases on the same host do not interfere with each other.

PROJECT-1301:An error could occur when create an Oracle standby database on Windows using the dbvctl command line. This error has been fixed.

PROJECT-1310:Some email notifications included a broken image link. The broken image link has been removed from these email notifications.

PROJECT-1339:Setting up a configuration using SEHA could fail if a non-English locale was used. A fix has been made to force the output from srvctl into English when automated by StandbyMP.

PROJECT-1502:After importing an existing DDC, problems could occur if hostname scripts were required but were not present. This affects systems where the host name of the database host doesn’t match the SOURCE or DESTINATION parameter in the DDC, for example when using RAC. To fix this, hostname scripts are created during the import process using the configured SOURCE and DESTINATION parameters.

PROJECT-1545:Configurations using Reporting Replicas required manual intervention following a StandbyMP upgrade in order to upgrade the “dbvsnap” configuration file. This upgrade is now performed automatically.

PROJECT-1559:When activating a standby database using the dbvctl command line, a confusing prompt relating to custom scripts was shown. This prompt has been removed. To use custom scripts during activation, please use the Control Center or the new dbvcli command line tool.

PROJECT-1701:In some cases, upgrading from Standby v10 on Windows could fail to copy existing DDC files. The upgrade process has been made more robust.

PROJECT-1702:Upgrading from Standby v10 on Windows while the v10 dbvserver service is running could fail. The installer will now stop the dbvserver service and continue.

SQL Server

PROJECT-1821:The user interface for creating many SQL Server configurations at once has been streamlined.

PROJECT-1709:Events were not created for failures of Automated Standby Update for SQL Server configurations. This has been fixed, and events will now appear in the Control Center if log backup or restore fails.

Related content